Answered Container page not loading - returning 404

Off the bat, this is "weird" - no, really!

MODx revo. Container page (/services/) has been working fine up to this point, its a container 'page', FURLS on everything else on the site work fine.
What I've tried :

• Turn FURL's off, it doesn't load.
• Change to a normal page (.html) not a container - it loads
• Set the template to blank, to make sure there is no conflict with scripts e.t.c doesn't load
• Change the name of the container page, it loads

As a temporary measure I've just renamed the container to "/our-services/" - but i really want it back to just '/services/'

Any help would be greatly received!

Many thanks

P.S The Modx error logs shows nothing regarding this either [ed. note: gelstudios last edited this post 13 years, 10 months ago.]

You pointed me in the correct direction, and now I'm happy to report it's all resolved!

Having a physical folder with the same name as a container in MOD'x with FURL's enabled is bad...

Well, the web server looks for physical folders/files first, and only does the rewrite thing if it doesn't find what it was asked for.

You should be able to add an exclusion to the parent directory of the directory in question in the .htaccess file such as the assets folder (although if this is using nginx, as the Cloud is, there's no .haccess to add an exclusion to).