Safe_Mode On
PermalinkI read on php.net that safe_mode is deprecated and will be removed in version 6 of php and is nothing to rely on (eh... on or off?), so it might be something that needs to be considered.
We can't guarantee that every function of concrete5 will work perfectly with safe mode enabled, which is why we throw a warning on install if it is disabled. Installation should still proceed, however - I was just able to install concrete5 with it enabled.
Finally - yes, you will have to make certain files writable in order to install/run concrete5. How else would the installation program write the resulting configuration file to a directory upon completion? The packages directory is made writable to allow easy installation of addons from concrete5.org, and the files directory is made writable to allow you to add files and images to your site, through the file manager.
Once installation is complete, these directories can be made non-writable again (although that will disable certain functionality.) It is advised that the config/ directory should be made non-writable, too.
Would simply CMOD'ing the entire C5 file structure to 777 suffice? ...and then changing them back afterwards - are the majority of the files permissions the same (ie all except the directories specified in the installation that need to be writeable), or is it a real mixed bag?
If you have wired uid/gid settings, you might have to disable the files structure which usually gets created automatically. See this threadhttp://www.concrete5.org/community/forums/installation/plesk_safe_m...
this must not be such a hard question for the developers overhere.
Can someone explain if concrete5 can be installed with safe_mode on?
Also curious about the why it is needed and with what words to convince the host that safe_mode should be turned off.
Anyone?