After moving a ModX site (Evolution 1.0.4 version) from on server to another, I’ve since ran into a number of permissions issues that I can’t seem to get around. Basically, the site loads normally straight from the cache, but with cache disabled and the cache files temporarily renamed so to force the site to load from the database, I get an unstyled page. Checking the source code and then clicking through on the stylesheet links, I get a 403 forbidden error.
I’ve made sure the permissions in the relevant access subfolders are set as the moving site guide in the documentation recommends, and tried various other things to try to get it to work, but to no avail. Must the server be configured in a specific way in order to avoid 777 permission settings, or just to get it to work, even with 777 permissions set in the necessary areas?
-
MODX Staff
- 730 Posts
Are your CSS files actual files, or MODX Resources?
Is it possible there’s a base_href in the head of your page that is pointing to the wrong server?
The CSS seems to be generated, as it is coming from .html files (since that is the suffix setting on database side), and there is a base tag in the template pointing to the right domain. On the last bit, the base tag is coming up properly. What isn’t appearing is the styling, because all I’m getting is 403 errors from the links, saying I "don’t have permission to access /index.php on this server".
-
MODX Staff
- 730 Posts
Is it possible to post the URL of the site publicly?
-
MODX Staff
- 730 Posts
Does your .htaccess file have the following?
RewriteBase /stjohnscollege.co.uk/
-
☆ A M B ☆
- 24,524 Posts
No, MODx runs as well on any type of PHP implementation. Some folders and files may need to have looser permissions if coming from a server that used suexec; for example the assets/cache folder and all of its files have to be writable.
Temporary URLs are always a problem with rewriting URLs. Different configurations require different solutions. Usually I find it easiest to simply not use friendly URLs until the domain’s final URL is available.
And yeah, the tweak to the .htaccess rewrite base rule was the issue.
Thanks for the info and it all should be working in the mean time. Cheers!