Legacy PHP Maintenance
Legacy PHP maintenance keeps older PHP, CodeIgniter and hand-written applications usable while their security risk is reduced. It covers moving to a supported PHP version, fixing known weaknesses and documenting how the code works.
What these applications look like
Queries sit directly inside page files. There is no framework, or there is an old CodeIgniter. Settings are hard-coded near the top of a file, and uploads share a folder with code. This is not current practice, but such applications often carry a distributor’s ordering, and they deserve careful handling.
How the work proceeds
Rewrite or keep going
Keep going when the logic is correct and the business is not changing much. Rewrite when every change is slow, or when the data model blocks what you now need. That judgement is set out in a written assessment.
Frequently asked questions
Can an old PHP application keep running with maintenance?
Yes, if it is moved onto a supported PHP version and patched. What cannot continue is staying on a version that no longer receives security fixes.
Our code has no version control. Is that a problem?
Yes, and it is the first thing fixed. The live code is pulled into a repository, so every later change has a history and a way back.
Do you work with CodeIgniter and hand-written PHP?
Yes, along with older Laravel and WordPress installations that carry custom plugins. The pattern of problems is similar across all of them.
Can the old application and a new one run together?
Often yes, either sharing a database or connected through an API. That allows one module to be replaced at a time instead of stopping everything for a rebuild.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
- No obligation
- A reply within one business day
- Your details stay private
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirements