roots / sage

WordPress starter theme with Laravel Blade components and templates, Tailwind CSS, and a modern development workflow
https://roots.io/sage/
MIT License
12.74k stars 3.06k forks source link

h5bp htaccess missing #357

Closed johnsolarz closed 12 years ago

johnsolarz commented 12 years ago

Apparently I'm not getting the h5bp htaccess rules to write upon standard activation in a subdirectory install. Roots rewrites work properly.

This is what my roots-generated htaccess looks like - Is this correct? Thanks in advance

# BEGIN HTML5 Boilerplate
# END HTML5 Boilerplate

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /demo/
RewriteRule ^index\.php$ - [L]
RewriteRule ^css/(.*) /demo/wp-content/themes/roots/css/$1 [QSA,L]
RewriteRule ^js/(.*) /demo/wp-content/themes/roots/js/$1 [QSA,L]
RewriteRule ^img/(.*) /demo/wp-content/themes/roots/img/$1 [QSA,L]
RewriteRule ^plugins/(.*) /demo/wp-content/plugins/$1 [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /demo/index.php [L]
</IfModule>

# END WordPress
retlehs commented 12 years ago

can you tell me what your setup is? (LAMP / MAMP / whatever)

can you try in a non-subdirectory install (move out of /demo/ and into the web root)?

johnsolarz commented 12 years ago

Yes, I'm on standard LAMP and I just tried a non-subdirectory install for a new site the other day. No luck. Something server side? FYI The previous version of roots which had a different method for writing the htaccess (pre "markers" i think) worked fine for me. Curious where the discrepancy is. Thanks for your attention.

retlehs commented 12 years ago

fixed