Search recent PHP errors, identify the plugin, theme, or WordPress component involved, and collect useful troubleshooting details without opening server log files.
WordPress can appear to work while a plugin, theme, or background task produces warnings. BitFire brings recent PHP messages into a searchable dashboard so you can connect a symptom with the software that reported it.
Enable temporary error logging when you need it, reproduce the problem once, and review the newest entries.
Open BitFire settings and enable Log Site Warnings & Errors. Logging automatically turns off after 24 hours to limit disk usage.
Note the time, then safely repeat the failing page, form, login, upload, or dashboard action.
Open the BitFire Error Log. Entries are listed newest first so you can compare them with the time of your test.
Compare this with the time a feature failed.
Start with Fatal and Error entries.
Often identifies a plugin, theme, or core file.
Useful to a developer; do not edit it yourself.
Use distinctive wording when searching or asking for help.
Severity helps you choose what to investigate first, but repetition and the affected website feature also matter.
A notice about something the software observed. Review it when diagnosing a related feature.
Monitor when relevantCode met an unexpected condition but may have continued. Check new or repeating warnings.
Review repetition and impactAn operation failed or software reported a serious problem. Test the related feature promptly.
Investigate promptlyPHP could not continue the current request. This may cause a blank page or critical-error screen.
Investigate immediatelyYou do not need to understand PHP. Look for familiar folder names in the file path.
wp-content/plugins/plugin-name/A pluginThe folder usually names the plugin to update, test, or report to its developer.
wp-content/themes/theme-name/A themeCheck the active theme and any related parent theme for updates.
wp-admin/wp-includes/WordPress coreWordPress reported the error, although a plugin or theme may have passed it incorrect information.
custom-or-unknown-folder/Custom or unfamiliar codeAsk the developer or agency that installed it. Investigate unfamiliar PHP in upload folders promptly.
Recognize it. Confirm the plugin, theme, or custom component.
Update it. Install available WordPress and component updates.
Test again. Repeat the affected action once and check the newest entries.
Search across file paths and messages, then combine the search with a severity filter when you need a narrower result.
woocommerceSearchwoocommerceMessage: Undefined array keyFile: rest-api.phpUse a plugin name, file name, or recognizable part of the message. Short searches usually work better than copying the entire message.
Select an Info, Warning, Error, or Fatal filter chip. Its number shows how many entries match that level.
Use Older and Newer when the results span more than one page.
An understood warning can repeat so often that it hides more useful entries. Ignored patterns keep the table readable without changing website code.
First identify the source and confirm that the related feature works. The matching pattern is then hidden from the main table.
The most useful clue is an entry recorded at the same time as a problem you safely repeated.
This lets you separate your test from unrelated background activity.
Do not repeatedly submit a live payment, order, import, or email campaign.
Compare their times and file paths with your test.
Update recognized software. Ask its developer or your host if the message returns.
Record what changed, install related updates, clear website caches, and test the affected feature once.
Update older plugins and themes. If several unrelated components fail, give your host the time of the PHP change.
Check entries from the feature plugin and related payment, email, anti-spam, membership, or caching software.
A malformed or hostile request can trigger an ordinary warning, but the warning alone does not show that an attack succeeded.
BitFire's firewall, security events, and malware scanner answer different questions. An empty Error Log does not prove that a website is secure.
Copied text and clear steps help a support technician diagnose the problem faster than a screenshot alone.
Use this route when the file clearly belongs to a specific product.
Use this route for PHP versions, databases, storage limits, permissions, or a site that cannot load.
Include the evidence below so the team can review the situation.
Quick answers to the questions WordPress administrators ask most often.
No. Start with fatal errors and errors related to a feature that is not working. Then review warnings that are new, frequent, or connected with an important function.
No. It means BitFire has no matching PHP entries to show from the active logging window. Browser, database, network, and external-service failures may be recorded elsewhere.
Log Site Warnings & Errors is a temporary troubleshooting setting that automatically turns off after 24 hours to limit generated log size. Enable it again when you need another troubleshooting window.
A search, severity filter, or ignored pattern may be hiding them. Clear the search and filter chips, then check the ignored-pattern banner.
No. It only hides a matching pattern from the table. The plugin, theme, WordPress component, or custom code may continue producing the warning.
Not automatically. Update it first and test the affected feature. Deactivating an important plugin can disable checkout, forms, membership, backups, or security.
No. Public errors can confuse visitors and expose internal details. Use the private BitFire Error Log and your hosting provider's logs instead.
Include the domain, event time, complete message, severity, file path, line number, and the action that produced the problem. Never include passwords or private credentials.