Modx revo and PHP 5.3

Hi All,

I need to have FileInfo installed on my server for another script to run and my host has suggested upgrading to PHP 5.3.
I was wondering if there were any known issues in 5.3 ? like having magic_quotes set to off by default, which I saw in a older post, or can I just have it upgraded and all good to go ?

Using the latest release Of Revolution

Thanks

I’ve had no problems with PHP 5.3.x on my site which is running Revolution. You should be good to

The core runs perfectly under 5.3 but there might be some issues with addons using the deprecated split()

Cheers both, I’ll go ahead and upgrade then

You shouldn’t have any issues. Revo is optimized for 5.3+, and the core team develops with 5.3.3+.

Hi Shaun,

They did the upgrade and I then got warnings about the time zone ( easy enough to fix via htaccess ) and one about PDO not being installed, which surprised me as they claimed to support Revo 100% and knew that Revo was installed on the server.

Anyway after 1 hour shouting at them the issues were fixed and the site was back up and running, got a responce from the support team that the issues were not with them and it was down to a php.ini file in the root of my directory that had caused it, funny that as I don’t know what one look’s like and refuse to override server php.ini files with custom ones, but hey ho the site’s up and that’s all I care about.

Sorry for involving here: What about this bug? Is it a core/XPDO bug? http://bugs.modx.com/issues/3342
How can this be solved if using such a plugin?

That would be a good question for the core team. The fact a bug is filed on the problem is a great start, I suspect they will address this in a later release.

On a side note for anyone making custom php.ini files to set time/date or other items, use this: http://tips-scripts.com/php_ini to make the php.ini file. It will use the server default php.ini file and then add your changes, so everything should be configured properly

Quote from: smooth-graphics at Feb 16, 2011, 01:24 AM

Sorry for involving here: What about this bug? Is it a core/XPDO bug? http://bugs.modx.com/issues/3342
How can this be solved if using such a plugin?

Um ... the fix is listed in the bug report in the link you provided.

And to be honest, that file is not yet used by anything in MODX or any MODX components I am aware of. It will be fixed before it is used...