My host updated to PHP 5.3.8 - Evolution 1.0.5 breaks - Now what?

Try setting it manually in the root index.php file just after the opening php tag.



See php for more details and list of supported locations.

this is strange, after saving the configuration from a minor change I now get:

date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/London' for 'BST/1.0/DST' instead

I can access the manager fine, but trying to browse the site produces the above error. Maybe a snippet or chunk?

That seems to have worked. Thanks =)

Ugh, actually no. It appears even though the host claims that magic_quotes_gpc is set as off it is still showing as On my end. Surely they need to restart Apace for this to propagate?

Well, magic_quotes_gpc is now set to off. I've cleared browser cache. Logged out and back in again to confirm it is off, and it is. Tried editing a html chunk and still backslashes are being inserted before quotes.

I'm at a bit of a loss now really. ;/

Is it on all resources? Since they were turned on if you made any changes they will be stored in the database. Try editing that resource and manually removing the extra backslashes and save, then see what the results are.

No difference i'm afraid. I have to manually go in via phpmyadmin and edit the table directly.

I have kind of resolved it now. I found a snippet of code in some previous threads where others were addressing the issue and have inserted that into the root index.php, the ajax.php and manager index.php. For now this will have to do until i can get to the bottom of it with my host. Otherwise it looks like moving to a host that does support MODx Evolution properly.

Thanks for the help though, i do appreciate it greatly =)

Do you have php as an Apache module, or is it CGI or FastCGI? If it's an Apache module, yes, the Apache server has to be re-started for any changes in the default php.ini to take affect.

Are there any directives in your .htaccess file relating to PHP? There are directives to indicate which PHP engine to use, and also directives for which php.ini file to use as the default for the current page being requested. They may or may not apply to your situation, depending on your server configuration.

Evo is not at all picky about server support.

Also, try to remove eventual php.ini override in your Evolution root folder - it looks like that file "destroys" globally set php.ini on some SuPHP+FastCGI configurations...