TopicWordPress →
⌚ About 2 min read
Reasonably add the memory limit available for WordPress when, a memory error the requires.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Check the current limit
See Tools > Site Health > Information > Serving.
-
2
Control the boundaries of the hosting
The WordPress value cannot exceed the limits actually allowed by PHP/host.
-
3
Edit wp-config.php if appropriate
Add a WP_MEM constant before the end of edition line.
-
4
Retester site
Check if the error disappears.
-
5
Searching for cause
Excessive consumption may come from a plugin, a theme or an abnormal request.
Commands utiles
(g) ‘WP_MEM', ‘256M';
À retenir
- Overtime incrementing memory does not fix a faulty leak or plugin.
- Contain a copy of wp-config.php before modification.
WordPress: deepen diagnosis without hiding the root cause
Technical checkpoints
- WP_DEBUG_LOG usually writes to wp-content/debug.log only when WP_DEBUG is enabled and the PHP process can write the file.
- Renaming a plugin directory prevents it from loading without changing the database, which is useful when wp-admin is unavailable.
- WP_MEMORY_LIMIT cannot exceed the memory actually granted by PHP/hosting; memory errors require reading memory_limit and peak usage.
Controlled recovery
Isolate the failing plugin or layer, keep logs, then re-enable one component at a time.
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);Topic-specific pitfalls
How to validate
- The site loads with clean logs and the failing component is identified, not merely disabled.
- Temporary debug constants are removed or adjusted after the intervention.