WordPress core and PHP form part of the runtime foundation for every WordPress instance.
Changes to either can affect plugins, themes, custom code, and site behavior.
What this area shows
The WP and PHP area can help you review:
- Current WordPress version
- Current PHP version
- Available maintenance information
- Compatibility signals
- Update results
Before changing WordPress
Check:
- Recent backup
- Plugin compatibility
- Theme compatibility
- Custom code requirements
- Current baseline test
- Site Health
Before changing PHP
PHP changes should be treated as compatibility changes, not cosmetic configuration.
Older plugins, themes, or custom code may rely on behavior removed from newer PHP versions.
Establish a baseline before the change.
Recommended update workflow
- Use a CanaryWP testing environment.
- Verify a backup.
- Run baseline Site Testing.
- Apply one WordPress or PHP change.
- Wait for the environment to stabilize.
- Open the public site.
- Open WP Admin.
- Review logs and Site Health.
- Run Site Testing again.
- Compare results.
Prefer controlled changes
Smaller changes are easier to diagnose.
When possible, avoid simultaneously changing WordPress, PHP, plugins, themes, and database content.
If everything changes at once, a regression becomes much harder to attribute.
After an update
Pay particular attention to:
- Fatal errors
- Deprecation warnings
- WP Admin
- Forms
- Checkout or account workflows
- Custom plugins
- Theme rendering
- Scheduled jobs
Failed update
If a change causes problems:
- Capture the failure.
- Review logs.
- Identify the affected component.
- Restore or revert if appropriate.
- Retest the recovered state.
Do not use production as the first place to determine whether a major runtime change is compatible.