register_globals issue

Hi,

I get a Configuration warning: ’register_globals is set to ON in your php.ini configuration file’ when I login to Modx

I have deleted the # in front of php_flag register_globals Off as I have read in previous threads on MoDx in both ht.access file and .htaccess file in the root folder of Modx

However I still get the message.

The site is on a shared server. Also I have two sites with the same host and both with the same version of Modx installed and deleting the # worked on one of the sites but not on the other?

Any clues appreciated

World

Not all servers allow using htaccess to control this. I had a similar situation recently and the solution was to migrate to a newer server which allowed customizing the php. I would contact the host and see if they have options.

Register_globals is quite dangerous to leave on by default its switched off on onesmarthost but customers can enable if they wish.

Some hosts allow you to upload a customer php.ini to your htdocs / wwwroot folder which sets this to off.

It could be that htaccess rules are not setup for your particular domain by the host or that server, your best bet would be to drop them an email to confirm how you can to register_globals off

Aaron.

Thanks dev-cw and Aaron for your suggestions.

Once I get Register_Globals set to OFF can I then set the permissions on the assets/cache and assets/images folders back to 777 so that they work in my MODx admin area? At the moment I have them set to 755 but this seems to make them inaccessible from within the MODx cms?

Thanks

W

Quote from: world at Nov 28, 2008, 09:52 AM

Once I get Register_Globals set to OFF can I then set the permissions on the assets/cache and assets/images folders back to 777 so that they work in my MODx admin area? At the moment I have them set to 755 but this seems to make them inaccessible from within the MODx cms?

These are completely separate issues and having nothing whatsoever to do with one another.

OpenGeek,

Ok. but the second part of the question is still remains i.e from what I understand permissions should not be left as 777 but if I change
assets/cache and assets images to anything else like 755 then do not seem to accessible from within my MODx

My understanding of all this is very limited so some clues would be appreciated.

Your answer just leave me hanging

W

Permissions for the file browser also depends on your server configuration and how PHP is running.

Ryan,


System info says:

PHP Version 5.2.5 what other information do you need to know?

w

Is it running as CGI or an Apache module. Is it running as Suexec or Suhosin. And several other potential things. The answer is going to determin if it should be 777/666, 775/664 or 755/644 for directories/files.