All the installs I’ve done with PHP4 have gone flawlessly, but now I’ve been trying to work in an all PHP5 environment and I’m getting writable errors in the following places;
assets/cache directory
assets/cache/siteCache.idx.php
assets/cache/sitePublishing.idx.php
assets/images directory
assets/export directory
manager/includes/config.inc.php
Also, the install pages wouldnt load in Firefox at all (they’d just be continuously loading and flash a PHP error for a split second and try to reload again. It does work in Opera though)
As to the permissions, should I just change them via FTP or would that be insecure? I’m looking for the best practices in terms of security when setting up MODx in a pure PHP5 environment.
Just a quick question : did you change from a shared server to a dedicated box ?
I am asking because when I switched I had to manage new things, and permission are among them (it was not switching from PHP4 -> PHP5 but from shared -> dedicated). You indeed have to CHMOD the files (as instructed by the installer BTW).
From a security standpoint, of course the config.inc.php should be set to 644 (read only) once the install is done (If you don’t, the manager warns you that you have to do so anyway).
The following files have to be writable for MODx to work :
assets/cache directory
assets/cache/siteCache.idx.php
assets/cache/sitePublishing.idx.php
assets/images directoryssets/export directory
As for the reloading in FF, never seen that... I’ll let someone jump in to answer that one...
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id
I’ve been testing out installations on 1&1 Shared hosting plans and Surpass Hosting shared plans. The reloading only occurred on the install page and I havent seen anything simlar since. It was a little strange though.
