Case 22 · Plugin & theme updates
Are Your Plugins and Themes Compatible with the Latest WordPress Version?
Short answer
Before a major WordPress update, check each plugin's 'Tested up to' version and changelog, confirm your theme supports the new release, check PHP requirements, and test the update on a staging copy. Plugins that are not compatible should be updated, temporarily held back, or replaced before you update the live site.
The challenge
This is a typical scenario based on the kinds of challenges WordPress site owners bring to us. Names and details are illustrative.
A professional services firm wants to adopt the latest WordPress release for its improved editor, but the site uses a booking plugin, a multilingual plugin and a theme built on an older framework. The marketing team is ready to click “Update now”.
A compatibility review shows the booking plugin is already tested with the new version, the multilingual plugin has a fix pending in its next release, and the theme framework triggers deprecation warnings that will become errors under the newer PHP version the hosting company is moving to.
Warning signs to look for
- Plugins show 'Compatibility with your version of WordPress: Unknown'.
- Warnings appear after a WordPress update, or features stop working.
- The theme has not been updated since an older WordPress version.
- The site depends on custom code written for an old WordPress or PHP version.
Common causes
- Plugins lagging behind
- Some plugin developers take weeks to test and update after a major WordPress release; some never do.
- Theme frameworks
- Older themes may not support newer editor features or block changes.
- PHP requirements
- New versions of WordPress and plugins gradually require newer PHP versions, which in turn affect older code.
- Custom code
- Custom functions using deprecated WordPress features can stop working without warning.
What it costs your business
Incompatible components can break layouts, forms and editing tools right after an update, or cause gradual errors that are hard to trace. Knowing compatibility in advance turns a risky update into a planned one.
Our approach
- 1
Build a compatibility list
We list each plugin and the theme with their 'Tested up to' version, last update date and PHP requirements.
- 2
Read changelogs
For key components, we read release notes for breaking changes and known issues with the new WordPress version.
- 3
Test on staging
We run the new WordPress version on a staging copy and test the features your business depends on.
- 4
Resolve conflicts
Incompatible plugins are updated, replaced or temporarily held back, and custom code is updated to current standards.
- 5
Update with confidence
Once staging is clean, we update the live site and continue to watch for warnings and errors.
Services delivered
WordPress Maintenance
- Compatibility checks before every major update.
- Staging tests for WordPress, theme, plugin and PHP changes.
- Replacement suggestions for abandoned or incompatible plugins.
- Custom code kept up to date with WordPress standards.
The outcome
On staging, the update is tested with a patched version of the theme functions, and the multilingual plugin's fix is applied when it is released. The live site is updated a week later with no visible issues, instead of discovering three problems on a busy morning.
How to prevent it happening again
- Choose actively maintained plugins and themes.
- Wait a short time after major releases for plugin developers to catch up, but don't wait indefinitely.
- Keep custom code following current WordPress coding standards.
- Keep the PHP version current and supported.