{"id":2513,"date":"2025-03-18T22:34:59","date_gmt":"2025-03-19T02:34:59","guid":{"rendered":"https:\/\/cassiopea.ca\/blogue\/uncategorized\/debugging-a-wordpress-site-a-complete-guide-to-troubleshooting-errors-and-problems\/"},"modified":"2025-03-18T22:37:16","modified_gmt":"2025-03-19T02:37:16","slug":"debugging-a-wordpress-site-a-complete-guide-to-troubleshooting-errors-and-problems","status":"publish","type":"post","link":"https:\/\/cassiopea.ca\/en\/blogue\/web-design\/debugging-a-wordpress-site-a-complete-guide-to-troubleshooting-errors-and-problems\/","title":{"rendered":"Debugging a WordPress site: A complete guide to troubleshooting errors and problems"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A WordPress site that crashes can quickly become a headache. PHP errors, white screens, database problems&#8230; there are a multitude of causes that can affect the smooth running of your site. This guide will help you diagnose and solve these problems by following a structured approach and using the best tools and techniques available. Consult the <a href=\"http:\/\/Documentation%20officielle%20WordPress%20Debugging%20%E2%86%92%20https:\/\/developer.wordpress.org\/debugging\/\" target=\"_blank\" rel=\"noreferrer noopener\">official WordPress debugging documentation<\/a> in addition to this article.   <\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table des mati\u00e8res<\/h2><nav><ul><li class=\"\"><a href=\"#1-les-erreurs-courantes-sur-word-press-et-leurs-causes\">1. Common WordPress errors and their causes<\/a><ul><li class=\"\"><a href=\"#1-1-erreurs-fatales-et-erreurs-php\">1.1 Fatal errors and PHP errors<\/a><\/li><li class=\"\"><a href=\"#1-2-lecran-blanc-de-la-mort-wsod\">1.2. The white screen of death (WSOD)<\/a><\/li><li class=\"\"><a href=\"#1-3-erreur-de-connexion-a-la-base-de-donnees\">1.3 Database connection error<\/a><\/li><li class=\"\"><a href=\"#1-4-erreur-500-internal-server-error\">1.4 Error 500 &#8211; Internal Server Error<\/a><\/li><li class=\"\"><a href=\"#1-5-erreur-403-acces-interdit-forbidden\">1.5. Error 403 &#8211; Access forbidden (Forbidden)<\/a><\/li><li class=\"\"><a href=\"#1-6-erreur-503-service-temporairement-indisponible\">1.6 Error 503 &#8211; Service temporarily unavailable<\/a><\/li><li class=\"\"><a href=\"#1-7-erreur-too-many-redirects-boucle-de-redirections\">1.7 &#8220;Too many redirects&#8221; error<\/a><\/li><li class=\"\"><a href=\"#1-8-erreur-de-memoire-epuisee-allowed-memory-size-exhausted\">1.8. Allowed memory size exhausted&#8221; error<\/a><\/li><li class=\"\"><a href=\"#1-9-autres-erreurs-http-502-bad-gateway-504-gateway-timeout-etc\">1.9. Other HTTP errors (502 Bad Gateway, 504 Gateway Timeout, etc.)<\/a><\/li><\/ul><\/li><li class=\"\"><a href=\"#2-outils-indispensables-pour-deboguer-un-site-word-press\">2. Essential tools for debugging a WordPress site<\/a><ul><li class=\"\"><a href=\"#2-1-activer-le-mode-debug-word-press-wp-debug\">2.1. Enable WordPress to debug mode (WP_DEBUG)<\/a><\/li><li class=\"\"><a href=\"#2-2-plugins-de-diagnostic-et-de-debug\">2.2. Diagnostic and debugging plugins<\/a><\/li><li class=\"\"><a href=\"#2-3-utiliser-la-console-du-navigateur\">2.3. Using the browser console<\/a><\/li><li class=\"\"><a href=\"#2-4-acceder-aux-logs-du-serveur\">2.4. Access server logs<\/a><\/li><li class=\"\"><a href=\"#2-5-outils-externes-pour-analyser-les-performances\">2.5. External tools for analyzing performance<\/a><\/li><\/ul><\/li><li class=\"\"><a href=\"#3-etapes-de-diagnostic-et-resolution-des-problemes-word-press\">3. Steps for diagnosing and resolving WordPress problems<\/a><ul><li class=\"\"><a href=\"#3-1-desactiver-les-plugins\">3.1. Deactivating plug-ins <\/a><\/li><li class=\"\"><a href=\"#3-2-tester-avec-un-theme-par-defaut\">3.2. Testing with a default theme<\/a><\/li><li class=\"\"><a href=\"#3-3-verifier-et-regenerer-le-fichier-htaccess\">3.3. Checking and regenerating the .htaccess file<\/a><\/li><li class=\"\"><a href=\"#3-4-augmenter-la-memoire-php\">3.4. Increasing PHP memory<\/a><\/li><li class=\"\"><a href=\"#3-5-reparer-et-optimiser-la-base-de-donnees\">3.5. Repair and optimize the database<\/a><\/li><li class=\"\"><a href=\"#3-6-reinstaller-les-fichiers-word-press\">3.6. Reinstalling WordPress files<\/a><\/li><li class=\"\"><a href=\"#3-7-contacter-lhebergeur\">3.7. Contact the host<\/a><\/li><\/ul><\/li><li class=\"\"><a href=\"#4-resoudre-les-problemes-de-performance-et-compatibilite\">4. Solving performance and compatibility problems<\/a><ul><li class=\"\"><a href=\"#4-1-ameliorer-la-vitesse-du-site\">4.1. Improve site speed<\/a><\/li><li class=\"\"><a href=\"#4-2-resoudre-les-conflits-entre-plugins-et-themes\">4.2 Resolving conflicts between plugins and themes<\/a><\/li><li class=\"\"><a href=\"#4-3-verifier-la-compatibilite-des-mises-a-jour\">4.3. Check compatibility of updates<\/a><\/li><\/ul><\/li><li class=\"\"><a href=\"#5-bonnes-pratiques-pour-eviter-les-erreurs-a-lavenir\">5. Best practices to avoid mistakes in the future<\/a><ul><li class=\"\"><a href=\"#5-1-maintenir-word-press-et-ses-extensions-a-jour\">5.1. Keeping WordPress and its extensions up to date<\/a><\/li><li class=\"\"><a href=\"#5-2-faire-des-sauvegardes-regulieres\">5.2. Make regular backups<\/a><\/li><li class=\"\"><a href=\"#5-3-limiter-le-nombre-de-plugins\">5.3. Limiting the number of plugins<\/a><\/li><li class=\"\"><a href=\"#5-4-tester-sur-un-site-de-staging-avant-les-mises-a-jour\">5.4. Test on a staging site before updating<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"1-les-erreurs-courantes-sur-word-press-et-leurs-causes\">1. Common WordPress errors and their causes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-1-erreurs-fatales-et-erreurs-php\">1.1 Fatal errors and PHP errors <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">PHP errors are often caused by a plugin, a poorly coded theme or a lack of allocated memory. They can be displayed in debug mode. These errors prevent the site from functioning properly and can be located using error logs.  <\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-2-lecran-blanc-de-la-mort-wsod\">1.2. The white screen of death (WSOD) <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A critical problem that prevents WordPress from running correctly, is often caused by a fatal PHP error or a faulty plugin\/theme. We recommend activating debug mode to identify the source of the problem and test the site by disabling extensions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-3-erreur-de-connexion-a-la-base-de-donnees\">1.3 Database connection error <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This message indicates that WordPress cannot access the database, either due to an error in wp-config.php or a MySQL failure. Check the login details, repair the database via phpMyAdmin and contact the hosting provider if necessary. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-4-erreur-500-internal-server-error\">1.4 Error 500 &#8211; Internal Server Error <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A generic server error due to a corrupted .htaccess file, or a problematic plugin or theme. Check the error logs, test by disabling extensions and resetting .htaccess.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-5-erreur-403-acces-interdit-forbidden\">1.5. Error 403 &#8211; Access forbidden (Forbidden) <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Often caused by incorrect file permissions or overly strict security rules. Make sure files and folders have the correct permissions (644 for files, 755 for folders). <\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-6-erreur-503-service-temporairement-indisponible\">1.6 Error 503 &#8211; Service temporarily unavailable <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The problem is due to server overload or extension consuming too many resources. Test by deactivating plugins, and check the status of server resources with your web host.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-7-erreur-too-many-redirects-boucle-de-redirections\">1.7 &#8220;Too many redirects&#8221; error <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This can occur if the site URL is misconfigured or if conflicting redirects are in place. Check permalink settings and temporarily disable redirect plugins.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-8-erreur-de-memoire-epuisee-allowed-memory-size-exhausted\">1.8. Allowed memory size exhausted&#8221; error <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress reaches the PHP memory limit, which can be corrected by increasing the value in wp-config.php and optimizing heavy scripts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-9-autres-erreurs-http-502-bad-gateway-504-gateway-timeout-etc\">1.9. Other HTTP errors (502 Bad Gateway, 504 Gateway Timeout, etc.) <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">These errors are often due to a server problem or queries that are too long. Check whether your server is overloaded and optimize SQL queries. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"2-outils-indispensables-pour-deboguer-un-site-word-press\">2. Essential tools for debugging a WordPress site<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2-1-activer-le-mode-debug-word-press-wp-debug\">2.1. Enable WordPress to debug mode (WP_DEBUG)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Add this line to wp-config.php :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>define(&#8216;WP_DEBUG&#8217;, true);<\/li>\n\n\n\n<li>define(&#8216;WP_DEBUG_LOG&#8217;, true);<\/li>\n\n\n\n<li>define(&#8216;WP_DEBUG_DISPLAY&#8217;, false);<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Errors will be logged in wp-content\/debug.log.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2-2-plugins-de-diagnostic-et-de-debug\">2.2. Diagnostic and debugging plugins <\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Query Monitor<\/strong>: Analyzes SQL queries and PHP errors.<\/li>\n\n\n\n<li><strong>Debug Bar<\/strong>: Displays HTTP errors and requests.<\/li>\n\n\n\n<li><strong>Health Check &amp; Troubleshooting<\/strong>: Temporarily disable plugins to identify conflicts.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2-3-utiliser-la-console-du-navigateur\">2.3. Using the browser console <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Inspect for JavaScript and CSS errors via the browser&#8217;s development tools (F12).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2-4-acceder-aux-logs-du-serveur\">2.4. Access server logs <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">View PHP error logs via cPanel or FTP.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2-5-outils-externes-pour-analyser-les-performances\">2.5. External tools for analyzing performance <\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>GTmetrix<\/strong> and <strong>Google PageSpeed Insights<\/strong> to measure loading times.<\/li>\n\n\n\n<li><strong>New Relic<\/strong> for profiling PHP script execution.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"3-etapes-de-diagnostic-et-resolution-des-problemes-word-press\">3. Steps for diagnosing and resolving WordPress problems<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-1-desactiver-les-plugins\"><strong>3.1. Deactivating plug-ins <\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Rename the wp-content\/plugins folder to plugins_old to deactivate all plugins.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-2-tester-avec-un-theme-par-defaut\">3.2. Testing with a default theme <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Activate <strong>a default WordPress theme<\/strong> to see if the problem is with the theme.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-3-verifier-et-regenerer-le-fichier-htaccess\">3.3. Checking and regenerating the <strong>.htaccess<\/strong> file <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Rename .htaccess and save the permalinks in WordPress to recreate a new one.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-4-augmenter-la-memoire-php\">3.4. Increasing PHP memory <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Add this line to wp-config.php :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>define(&#8216;WP_MEMORY_LIMIT&#8217;, &#8216;256M&#8217;);<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-5-reparer-et-optimiser-la-base-de-donnees\">3.5. Repair and optimize the database <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Add define(&#8216;WP_ALLOW_REPAIR&#8217;, true); in wp-config.php and access wp-admin\/maint\/repair.php.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-6-reinstaller-les-fichiers-word-press\">3.6. Reinstalling WordPress files <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Download the latest version of WordPress and replace all files except wp-content.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-7-contacter-lhebergeur\">3.7. Contact the host <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the problem persists, request access to the logs and check the server status.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"4-resoudre-les-problemes-de-performance-et-compatibilite\">4. Solving performance and compatibility problems<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"4-1-ameliorer-la-vitesse-du-site\">4.1. Improve site speed <\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Activate a cache plugin<strong>(WP Rocket<\/strong>, <strong>W3 Total Cache<\/strong> or LiteSpeed).<\/li>\n\n\n\n<li>Optimize images with <strong>Imagify<\/strong>, <strong>SMUSH<\/strong> or <strong>ShortPixel<\/strong>.<\/li>\n\n\n\n<li>Activate a CDN to serve static resources faster.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"4-2-resoudre-les-conflits-entre-plugins-et-themes\">4.2 Resolving conflicts between plugins and themes <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Test by deactivating plugins one by one.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"4-3-verifier-la-compatibilite-des-mises-a-jour\">4.3. Check compatibility of updates <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check that your version of WordPress and PHP is compatible with the installed plugins.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"5-bonnes-pratiques-pour-eviter-les-erreurs-a-lavenir\">5. Best practices to avoid mistakes in the future<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"5-1-maintenir-word-press-et-ses-extensions-a-jour\">5.1. Keeping WordPress and its extensions up to date <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Update regularly to avoid vulnerabilities.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"5-2-faire-des-sauvegardes-regulieres\">5.2. Make regular backups <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use <strong>UpdraftPlus<\/strong> or <strong>BackupBuddy<\/strong> to automate backups.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"5-3-limiter-le-nombre-de-plugins\">5.3. Limiting the number of plugins <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Keep only essential extensions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"5-4-tester-sur-un-site-de-staging-avant-les-mises-a-jour\">5.4. Test on a staging site before updating <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid updating directly in production.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By following these steps, you&#8217;ll be able to diagnose and correct most WordPress problems. Apply best practices to minimize future risks and ensure the stability of your site! <\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A WordPress site that crashes can quickly become a headache. PHP errors, white screens, database problems&#8230; there are a multitude of causes that can affect the smooth running of your site. This guide will help you diagnose and solve these problems by following a structured approach and using the best tools and techniques available. Consult [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2510,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"_vp_format_video_url":"","_vp_image_focal_point":[],"footnotes":""},"categories":[79],"tags":[],"class_list":["post-2513","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-design"],"uagb_featured_image_src":{"full":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1.jpg",1280,653,false],"thumbnail":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1-150x150.jpg",150,150,true],"medium":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1-300x153.jpg",300,153,true],"medium_large":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1-768x392.jpg",768,392,true],"large":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1-1024x522.jpg",1024,522,true],"1536x1536":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1.jpg",1280,653,false],"2048x2048":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1.jpg",1280,653,false],"vp_sm":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1-500x255.jpg",500,255,true],"vp_md":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1-800x408.jpg",800,408,true],"vp_lg":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1.jpg",1280,653,false],"vp_xl":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1.jpg",1280,653,false],"vp_sm_popup":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1-500x255.jpg",500,255,true],"vp_md_popup":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1-800x408.jpg",800,408,true],"vp_xl_popup":["https:\/\/cassiopea.ca\/wp-content\/uploads\/2025\/03\/ecran-erreur-ordinateur-site-web-1.jpg",1280,653,false]},"uagb_author_info":{"display_name":"Arthur Cotton","author_link":"https:\/\/cassiopea.ca\/en\/blogue\/author\/acotton\/"},"uagb_comment_info":0,"uagb_excerpt":"A WordPress site that crashes can quickly become a headache. PHP errors, white screens, database problems&#8230; there are a multitude of causes that can affect the smooth running of your site. This guide will help you diagnose and solve these problems by following a structured approach and using the best tools and techniques available. Consult&hellip;","_links":{"self":[{"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/posts\/2513","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/comments?post=2513"}],"version-history":[{"count":0,"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/posts\/2513\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/media\/2510"}],"wp:attachment":[{"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/media?parent=2513"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/categories?post=2513"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cassiopea.ca\/en\/wp-json\/wp\/v2\/tags?post=2513"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}