discuss.answer
-
☆ A M B ☆
- 24,524 Posts
Do you have the "web" resource (#1) set as the error page? Sounds like you are getting the not-found error.
What are you using for routing?
I prefer to use XRouting, it's very simple to use. All you need to do is set up some context settings.
https://modx.today/posts/2015/05/using-xrouting-for-multilingual-websites-in-modx
Thanks Susan, got it. I was missing some Context Settings.
XRouter is so wonderfully simple!
Todd
Susan,
If I'm running MODX in a sub-folder, how would this affect the Context Settings?
The routing works fine locally, but that site is at root level. The remote site is in a sub-folder and it's throwing a 404.
Todd
Id guess your base URL rewrite isnt looking at the subfolder, so its probably set to RewriteBase / not RewriteBase /moo/
The base URL is pointing to the correct directory.
Even for the default Website context previewing a Resource throws a 404.
I don't know if it's a sub-folder issue, or if I messed something up when I created the new Sandbox context.
UPDATE
As a test I created a new context on another remote site, one that's not installed in a sub-folder and it works perfectly.
Whatever the problem it would definitely seem to be related to the installation being in a sub-folder. Apart from all the Resources (both contexts) throwing a 404 the rest of the Manager functions normally.
[ed. note: todd.b last edited this post 10 years, 5 months ago.]
Todd
-
☆ A M B ☆
- 24,524 Posts
What about the RewriteBase directive in your .htaccess file?
First, make sure the base href tag in all your templates is called uncached (with the exclamation point):
<base href="[[++site_url]]" />
If that doesn't solve it, try using just a slash in your Rewrite Base line. The subdirectory name isn't usually necessary there.
