Freedomification Plugins Log Viewer PRO — Documentation

13. Troubleshooting / workflow

This final section gives practical checks for the most common situations a PRO user may encounter. It is written as a quick workflow guide rather than a screenshot-based chapter, because troubleshooting is usually about choosing the right check in the right order.

Recommended troubleshooting workflow

1. Start with the exact log. Open the affected log in Log Viewer and confirm it still exists, is readable and displays new content.
2. Use a small test. Trigger one known action on the site, then use Refresh, Auto-refresh, Live Tail or Diff to see whether a new line appears.
3. Check Log Inspector. Use Full info to confirm the log status, safe path, file size, Log Hub participation, Reports participation, alerts and diagnostics.
4. Check the related module. If the problem is with Reports, check Reports filters. If it is with alerts, check Email Alerts and Webhooks. If it is with cleanup, check Maintenance targets.
5. Change one thing at a time. Avoid changing many settings at once while debugging.
6. Export settings before larger changes. Use Export before testing import, rollback, maintenance policies or security-path changes.

A log does not appear

• Confirm that the log was added to Log Viewer.
• Check whether filters, pagination or archived/removed visibility are hiding it.
• Confirm the file still exists and WordPress can read it.
• Check whether the path format is allowed by the current security settings.

A log appears in one PRO module but not another

• Remember that Log Viewer is the main list, while participation in Log Hub, Reports and Maintenance is configured separately.
• If ordering looks different between Log Viewer and Log Hub, confirm that the same logs were actually added to Log Hub. Log Hub follows the Log Viewer order for participating logs; logs not sent or added to Log Hub do not appear there.
• Use Inspector to verify the selected log's participation in Log Hub, Reports, Maintenance policies and other PRO workflows.
• Maintenance targets can remain enrolled after a log is removed from the main Log Viewer list.
• Reports depend on collected report data and the configured visibility, filters and time range, so they are not a direct copy of either Log Viewer or Log Hub.

Live Tail does not show new entries

• Confirm that the log is actively receiving new lines.
• Stop Auto-refresh before starting Live Tail.
• Turn off Diff mode if Live Tail is not expected to work with it.
• Refresh the page and start Live Tail again.
• Check Log Inspector for capabilities and diagnostics.

Auto-refresh is not updating

• Confirm that Auto-refresh is enabled for the selected log.
• Check the selected interval and line limit.
• Confirm that the log file is actually changing.
• Check whether the server can still read the file.

Diff / Show only new lines looks empty

• Set the baseline first, then trigger the action you want to test.
• Click Refresh after triggering the action.
• Remember that Diff shows new lines after the baseline, not older history.
• If the log was rotated, truncated or cleared, set a new baseline.

Find / search does not find expected text

• Check whether the text is inside the currently loaded log window.
• Try disabling Match case or Whole word.
• Check exclusions such as ((word)) if lines are hidden.
• Use a simpler query first, then add advanced syntax such as word1||word2.

Log Hub entries disappear or show fewer results than expected

• Check Log Hub display time window in PRO Settings. A smaller window hides older timestamped entries from the current Log Hub view.
• Check Log Hub tail/lines limits. Log Hub analyzes the currently loaded tail, not the full historical database.
• Check filters such as critical/error only, warning only, custom only or hide-noise behavior.
• Check ignore rules and muted logs.
• Use Reports when you need historical data that is older than the current Log Hub window.

Log Hub shows too much noise

• Add only useful logs to Log Hub.
• Use ignore rules for repeated low-value phrases.
• Use report include/exclude phrases to control what should be counted.
• Mute or remove logs that are not useful for monitoring.

Reports are empty or incomplete

• Confirm that the log participates in Reports.
• Check the selected date range and filters.
• Wait until enough activity has been collected.
• Check whether phrases are excluded or whether the log is archived/removed.

Email alerts are not received

• Confirm that global email alerts are enabled.
• Check the recipient address and email template.
• Confirm that alert phrases are configured for the relevant log.
• Check cooldown and dedupe settings.
• Use Send test alert.
• Confirm that WordPress mail works; for reliable delivery, use SMTP or a transactional email service.

Webhooks are not received

• Confirm that webhook delivery is enabled.
• Check the webhook URL and use HTTPS whenever possible.
• Confirm that the endpoint accepts JSON requests.
• Check timeout and payload limits.
• If HMAC is used, confirm that the receiving system verifies the same secret.

Maintenance does not run

• Confirm that maintenance features are enabled.
• Confirm that the log is enrolled as a maintenance target.
• Check whether scheduled maintenance is enabled and WP-Cron is running.
• Check the size threshold and whether the log has exceeded it.
• Use a budgeted manual run for a controlled test.

Settings import or rollback feels wrong

• Export the current settings before importing.
• Use only a JSON file exported from the plugin.
• After import, review Email Alerts, Webhooks, Security paths and Maintenance before testing live actions.
• Rollback restores the most recent import backup, not a full site backup.