Joomla & TYPO3 PHP CMS Updates
Joomla, TYPO3, Concrete CMS and similar CMSs run PHP under the hood. When the PHP release lands, the CMS core and its extensions need patching or staging QA before deploy.
Core & extension patching · Staging QA · Backup and rollback
Core + Extensions Patched Together
We patch the CMS core and version the relevant extensions together, on staging, before production.
Extension Surface Under QA
A CMS attack surface is mostly extensions; we stage-test them against the patched PHP version before go-live.
Easy Rollback
A full backup is taken before the change, so a broken patch restores cleanly.
What's Included
Common Scenarios
Joomla / TYPO3 / Concrete on End-of-Life PHP
Your CMS on PHP 8.2 with the October 2026 RCE fixes pending, or on PHP 8.1 with no upstream fix at all.
Patch Breaks an Extension
The patched PHP version conflicts with a CMS extension; we stage-test, patch or replace, and re-test.
Emergency Patch for a Live Site
Need the CMS patched now for a CVE hit: same flow as the £999 emergency patch, plus staging QA.
How a CMS PHP Update Runs
£149 Check and Extension Audit
We confirm the PHP version, patch level and CVE exposure, then audit installed extensions/templates against the target PHP version — third-party extensions are the usual break point on Joomla, TYPO3 and Concrete.
Staging Clone
The site and its database are cloned to staging on the target PHP version. Platform configuration files are adjusted for the new environment before testing begins.
Patch or Upgrade on Staging
PHP moves to the fixed or supported release. Admin panels, front-end rendering, forms and scheduled tasks are exercised; extensions that fail are patched or replaced in scope.
Production Switch
The verified change is applied in a quiet window with rollback ready. Caches are cleared, cron confirmed, and a written summary records every change plus extension status.
Pricing
Transparent, scope-based pricing. Every job includes a backup, a staging test and a post-change check.
Emergency Patch
£999
Same or next day
- ✓Safe PHP patch to a supported release
- ✓Backup before change
- ✓Staging check
- ✓Post-patch verification
Managed Maintenance
£299 / month
£2,999 billed annually — two months free
- ✓Ongoing PHP and dependency patching
- ✓Advisory monitoring
- ✓Monthly report
- ✓Backups and uptime checks
- ✓The £149 PHP check included to start
Version Upgrade
£4,999
1–3 weeks
- ✓Move off end-of-life PHP
- ✓Compatibility testing
- ✓Staging QA
- ✓Rollback plan and post-upgrade support
Prices are indicative ranges based on project scope. Contact us for a tailored quote.
Frequently Asked Questions
Which CMSs do you support?+
Joomla, TYPO3, Concrete CMS and similar PHP-based CMSs. Each gets its own upgrade quote after the check; the £999 patch flow is the same for all.
Are extensions included?+
Yes — patching includes the core plus versioned extensions that are affected, tested on staging. Additional extension work is covered by the upgrade's repair terms.
Do I need an upgrade too?+
Only if your CMS version runs PHP 8.1 or older (no upstream fix) or if the check shows you should move to a newer PHP branch. The upgrade starts from the £149 check's findings.
Can you handle an unmaintained or abandoned extension?+
Where a small compatibility patch fixes it, we do that in scope. Where the extension is genuinely dead, we recommend a maintained replacement and quote the swap before doing it.
My CMS is several major versions behind. Is that a problem?+
It's scoping, not a blocker. Major-version hops are planned as intermediate steps — each one tested — and the check report spells out the path and price before any work begins.
Start With the £149 PHP Check
Tell us which application you run and which PHP version it's on. You get a written report of your exposure and the recommended next step.