WordPress Shows a Critical Error After Updating

A WordPress critical error usually means PHP encountered a fatal error while loading the plugin or running a feature.

Check Which Plugin Triggered the Error

If WordPress sends an admin recovery email, open it and check the plugin and file mentioned in the message.

GoshLinks has separate plugins:

• GoshLinks - The core plugin.
• GoshLinks Pro - The Pro add-on plugin.
• GoshLinks Admin Tools - Internal admin tools, if installed.

Check PHP Error Logs

Look at your hosting control panel, server error log, or WordPress debug log for the fatal error message.

The most useful details are:

• The error message.
• The file path.
• The line number.
• What action triggered the error.

Temporarily Disable the Plugin

If the admin area is unavailable, use your hosting file manager or FTP to temporarily rename the affected plugin folder.

For example, rename goshlinks-pro to goshlinks-pro-disabled.

This can let WordPress load again so you can investigate.

Check Plugin Folder Names

Make sure the Pro plugin folder is named correctly:

goshlinks-pro

An incorrect folder name can prevent files from loading as expected.

Check Version Compatibility

Make sure the core and Pro plugins are from the same release set. Updating only one plugin while leaving the other far behind can cause missing class or missing file errors.

What To Send Support

• The exact error message.
• The GoshLinks core version.
• The GoshLinks Pro version, if installed.
• The PHP version.
• The WordPress version.
• The action that triggered the error.