Hello,
Hello all,
I have different versions of CMSMS on different virtual hosts on the same server. All virtual hosts are configured the same.
However, CMSMS versions behave different. 0.12 FIJI works perfectly with PHP safe mode on. But 0.13 gives severe access problems in file manager and image manager - does not work at all.
a) What has been changed in 0.13 regarding safe mode? How can I change it so that it behaves like 0.12?
b) Does 1.0 HAWAII work under safe mode?
I have switched over to CMSMS as the only CMS that I support, so I am having a hard time right now as half of all installations do not work - unfortunately I did not check file/imagemanager of 0.13 before installing since I figured it would work the same way as 0.12 ... my bad.
Do I have to either go back to 0.12 or change to a digfferent CMS which supports safe mode?
I do NOT want to switch off safe mode.
Regards,
Alex
Urgent: safe mode problems with 0.13/1.0
Urgent: safe mode problems with 0.13/1.0
Last edited by faglork on Tue Sep 12, 2006 3:19 pm, edited 1 time in total.
Workaround found: Re: Urgent: safe mode problems with 0.13/1.0
I have found a workaround:
I have to manually create directories via FTP (thus setting correct ownership) and chmod them 777.
Also: Forget about 0.12 working in safe mode ... 0.12 has the same problems.
Which is - as I understand it - not a bug of CMSMS but simply the effect of safe mode restrictions.
If CMSMS could be set to
a) create directrories with a given ownership
b) chmod them 777
all would be well (I think). But AFAIK only ROOT can issue a CHOWN command, so this won't work.
Any ideas?
Cheers,
Alex
I have to manually create directories via FTP (thus setting correct ownership) and chmod them 777.
Also: Forget about 0.12 working in safe mode ... 0.12 has the same problems.
Which is - as I understand it - not a bug of CMSMS but simply the effect of safe mode restrictions.
If CMSMS could be set to
a) create directrories with a given ownership
b) chmod them 777
all would be well (I think). But AFAIK only ROOT can issue a CHOWN command, so this won't work.
Any ideas?
Cheers,
Alex