发布前,若步骤依赖主机商,我们会在至少两家平台各走一遍;否则在同一环境隔日执行两次。我们记录控制台报错、不同地区的界面文案差异,并在厂商调整按钮位置后立即更新文案。路径与截图每季度抽检。涉及 DNS、SSL 或付款时,我们确认回滚/补救选项,并链接到官方文档以获取权威表述。
In wp-config.php set WP_DEBUG_LOG true and WP_DEBUG_DISPLAY false to capture fatals without showing errors to visitors. Revert after fixing.
Read wp-content/debug.log and your hosting error log in cPanel/hPanel for the first fatal stack trace.
Rename wp-content/plugins to plugins-old via FTP/SFTP. If the site loads, rename back and re-enable plugins one by one.
Rename your active theme folder to force Twenty Twenty-Five. confirms theme vs plugin issues.
Add define('WP_MEMORY_LIMIT', '256M'); in wp-config.php if logs show allowed memory exhausted. then find the greedy plugin.
In hosting panel select PHP 8.1 or 8.2 compatible with your plugins; incompatible PHP causes opaque 500s.
If core files were edited, restore clean wp-admin/wp-includes from a backup or official zip.