Quick troubleshooting view
The site or the administration displays "A critical error occurred" right after updating, a plugin, theme or WordPress.
- PHP incompatibility
- non-existent function or class
- plugin incompatible with a new version
- Identify the last modification
- Disable without deleting
- Read the log
- return to previous version of the wrong plugin
- install a compatible corrected version
- correct code if plugin is internal
Contextual technician plan
Note the plugin, theme or version updated just before the problem.
The calculated usable capacity should match the actual RAID level, disk count, smallest-disk size, spare/reserve and TB/TiB conversion.
If the theoretical calculation matches the controller/OS values, the capacity is explained by the design rather than a fault.
If values still differ materially, preserve the controller layout and investigate hidden reserve, hot spare, mixed disk sizes or filesystem overhead before resizing.
Rename the suspicious plugin folder via FTP if wp-admin is inaccessible.
“Disable without deleting” should produce an observation that clearly confirms or rules out “non-existent function or class”.
If the observation is normal, lower “non-existent function or class” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “non-existent function or class” first. Related action: install a compatible corrected version.
temporarily activate a debug log without showing any errors to visitors.
The calculated usable capacity should match the actual RAID level, disk count, smallest-disk size, spare/reserve and TB/TiB conversion.
If the theoretical calculation matches the controller/OS values, the capacity is explained by the design rather than a fault.
If values still differ materially, preserve the controller layout and investigate hidden reserve, hot spare, mixed disk sizes or filesystem overhead before resizing.
Compare PHP to the plugin requirements.
“Check PHP” should produce an observation that clearly confirms or rules out “conflict between extensions”.
If the observation is normal, lower “conflict between extensions” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “conflict between extensions” first. Related action: test updates on preproduction before production.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Crack if the error persists even after deactivation of the last modified component or touches the WordPress heart.
The site or the administration displays "A critical error occurred" right after updating, a plugin, theme or WordPress.
Causes probables
- PHP incompatibility
- non-existent function or class
- plugin incompatible with a new version
- conflict between extensions
Diagnostic étape par étape
- 1
Identify the last modification
Note the plugin, theme or version updated just before the problem.
- 2
Disable without deleting
Rename the suspicious plugin folder via FTP if wp-admin is inaccessible.
- 3
Read the log
temporarily activate a debug log without showing any errors to visitors.
- 4
Check PHP
Compare PHP to the plugin requirements.
Solutions possibles
- return to previous version of the wrong plugin
- install a compatible corrected version
- correct code if plugin is internal
- test updates on preproduction before production
Crack if the error persists even after deactivation of the last modified component or touches the WordPress heart.