Blog Sections Open
Preparing Evolution CMS 1.1b Builds for PHP 5.5
What to expect when running older Evolution branches on PHP 5.5 and why deprecation warnings should be treated as a migration signal, not background noise.
Running an older Evolution build on PHP 5.5 is the kind of upgrade that often “almost works”. The site may still load, but deprecated mysql_connect() and similar warnings show that the stack is living on borrowed time.
These warnings are not just cosmetic. They tell you the environment is now ahead of the codebase.
What to do first
- identify whether the current branch officially supports the PHP version,
- test the manager as well as the frontend,
- review database and parser components that still depend on deprecated mysql functions,
- plan an upgrade path instead of suppressing warnings indefinitely.
On legacy stacks, compatibility questions are often really upgrade questions. If a branch only survives because warnings are hidden, the project is already telling you it needs maintenance time.
So the practical answer is not “can I silence the warning?” but “which branch or patch level should this site move to next?”
Fixing ImportX Encoding and Field-Mapping Errors on CSV Imports
How to troubleshoot ImportX when CSV files arrive with broken encoding, question marks, or field-mapping errors such as invalid pagetitle.
When title and H1 Should Not Be the Same
How to think about page title and visible H1 as related but separate fields instead of mirroring them blindly across the whole site.