[Troubleshooting & Technical Issues] Common PHP Errors and solutions
[Troubleshooting & Technical Issues] Common PHP Errors & Solutions
V4 Quick Answer
PHP errors can stop a Link Whisper page, a background task, or the whole WordPress site. The exact log entry is more useful than a generic message, so capture it before changing server settings.
Before changing anything
- Copy the complete error, including the file path and line number, and note what action triggered it.
- Open Tools → Site Health → Info → Server to record the PHP version, memory limit, execution time, and other server values.
- If the dashboard is available, review Link Whisper → Settings → Debug and the relevant hosting/PHP logs.
- Take a current backup and use staging for configuration changes when possible.
Common errors
Allowed memory size exhausted
Large reports, scans, and AI-assisted work can use more PHP memory than the host allows. Ask the host to confirm the effective PHP and WordPress memory limits and whether they can be raised for the site. Do not assume one value such as 512 MB or 1 GB is a universal requirement.
Maximum execution time or input variables exceeded
Long-running requests and large forms can be stopped by max_execution_time or max_input_vars . Ask the host to review the effective limits and the matching error log. V4 background processing is intended for work that should not depend on one long browser request, but WordPress cron and loopback requests must be working. Do not repeatedly start the same task while it is running.
Class or function not found
This usually points to incomplete or mixed plugin files, a missing PHP extension, or a compatibility problem. Back up the site, download a fresh Link Whisper Premium ZIP from your Link Whisper account, and reinstall through Plugins → Add New → Upload Plugin when appropriate. Do not delete plugin data as a first step.
Parse error or unexpected token
Check the PHP version in Tools → Site Health → Info → Server and compare it with the current Link Whisper requirements. Very old PHP versions can fail to parse current code. Test a PHP change on staging first because themes and other plugins may also be affected.
Cannot redeclare a function or class
This commonly indicates a plugin or theme conflict. On staging or during a controlled test, isolate the conflict by disabling other plugins, testing Link Whisper, and re-enabling components one at a time. Keep security and caching changes temporary and restore them after the test.
503, cURL, or timeout errors
These can come from hosting limits, a firewall/WAF, blocked outbound HTTPS, REST or loopback failures, or a scheduled-task problem. Ask the host or security provider to check the request logs and allow the legitimate site requests required by Link Whisper. Avoid broad allow rules or disabling protection permanently.
Database errors
Record the exact database error and take a backup before attempting repairs. Do not run SQL changes manually unless you have a verified backup and specific guidance from support or your host.
AI and background-processing checks
For an AI-related error, open Link Whisper → Settings → AI, then check AI Subscription and AI Credit History. AI-assisted work requires available credits; keyword-based Auto-Linking rules are separate. For large sites, allow background processing to finish and check the dashboard or relevant current report after the task has had time to run.
Capturing a WordPress debug log
If support needs a WordPress log, enable logging temporarily in wp-config.php above the "That’s all, stop editing!" line:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
Reproduce the problem once, collect the new entries from /wp-content/debug.log or the hosting error log, then disable debug logging again. Do not expose the log publicly because it can contain sensitive paths or data.
When to contact support
Email support@linkwhisper.com with the exact error, file and line number, timestamp, action that triggered it, Link Whisper/WordPress/PHP versions, hosting provider, site size if relevant, active theme/plugins, and the relevant log excerpt. Do not send passwords, license keys, or API keys in plain text.