not working in subfolder

[roots]

not working in subfolder

[retlehs]

nice catch, i hadn't tested roots in a subfolder since we added rewrites from /wp-content/themes/roots/css/ (and js/ and img/) to /css/ etc.

looking into it now -- looks like it's in roots-cleanup.php starting at line 28 that must be fixed

[swartsr]

Thanks for looking into this! I'm having the same issue... I set up a child theme folder for my website so when you update I can pull down your latest stuff without breaking anything. It seems to be causing broken links for me too. Thank you!

[retlehs]

@swalkinshaw is working on a fix but not sure when he'll get it out (just left for a trip today)

in the meantime you could removes lines 1 through 45 on roots-cleanup.php to get it so you can at least work in a subfolder for now -- basically remove the roots_add_rewrites and roots_clean_assets/plugins functions

[swartsr]

Thanks! Appreciate it!

[misfist]

I also have WP installed in a sub-directory (called /wordpress) and am having the same problem. I commented out lines 8-45 (line 1 is <?php and 2-7 are already commented out), but it's looking for css, js and img directories in:

/wp-content/themes/roots/

It needs to be:

/wordpress/wp-content/themes/roots/

Any ideas?

Thanks!

[retlehs]

hmm the rewrite rules might need to be flushed after that -- try going to the permalinks page and clicking 'save' just to make that happen

if you still have the problem then you can take out the root relative filters in roots-cleanup.php

sorry about the troubles in subfolders! will get this fixed asap.

[retlehs]

i think scott got this working.. will try and push it out to the repo tonight

[swalkinshaw]

Updated relative path function to work with sub dirs - closed by 40485c7

[misfist]

I replaced the roots-cleanup.php file and it appears to be working correctly.

Thanks!

[swalkinshaw]

Yep, that's the only file that's been changed. Let me know how it goes. I tested it on a subfolder install but you never know...

[misfist]

I replaced the roots-cleanup.php file and it appears to be working correctly.

Thanks very much!

[bonny]

I just installed roots in a subfolder and it does not work. It will however work if I replace roots-cleanup.php with the version from april 04. So... something must have happened between now and april 04. Should I start a new issue about this?

[retlehs]

i have the latest roots and latest WP installed in a subdirectory

are you sure that maybe your .htaccess file just wasn't generated yet? need some more info besides 'does not work', what's broken.. file paths?

[bonny]

Ok, does this help:

WordPress is installed in /wordpress/

The link-tag for the stylesheet looks like this:
link rel="stylesheet" href="/wordpress/css/style.css"

/wordpress/css/style.css gives a file not found/404

If I manually go to
/css/style.css
it will show me the css-file, which makes me think that the htaccess does indeed work.

If i remove
add_filter('template_directory_uri', 'roots_clean_assets');
from roots-cleanup.php it will work (but output old ugly code, of course)

Oh, and I just realized I am using WP 3.2-bleeding and not the latest stable, so maybe that has something to do with it.

[retlehs]

i just installed wordpress 3.2 nightly and the latest roots into a subdirectory, all paths/redirects working properly

if you're getting 404 when trying to hit /wordpress/css/style.css then it sounds like your .htaccess isn't getting generated or isn't working like it should

[bonny]

The .htaccess do get generated. But I'll try it on another server and see if that helps. Hopefully there's something weird going on on this one. Thanks for your time!

[retlehs]

you mention that you're able to hit /css/style.css but not /wordpress/css/style.css, is it possible that your .htaccess file is in the root and not at /wordpress/.htaccess? also, can you provide us with the .htaccess file that's on your server?