Logify Troubleshooting — Fix Common Issues

Q: Why are no events showing in my activity log?

The most common cause is that Enable Tracking was switched off under Logify → Settings → General, or an exclusion rule is hiding the activity. Check the Exclusions tab for excluded user IDs, roles, IP addresses, event types, post types, and post statuses — exclusions drop matching events before they are written, so they never appear.

Q: How do I completely remove Logify and its data?

Tick Cleanup on Uninstall under Logify → Settings → General → Maintenance, then deactivate and delete the plugin from Plugins. This removes the Logify database table, settings, scheduled tasks, and metadata. If you delete the plugin without enabling that option, the data is left in place.

Most Logify problems come down to a setting: tracking is off, an exclusion rule is hiding events, retention is purging old logs, or a country lookup has not completed yet. This guide walks through the issues users hit most often and the exact setting to check for each. Start with the symptom that matches yours.

Events are not being logged

If nothing appears on Logify → Activity Logs, check these in order:

Confirm Enable Tracking is on under Logify → Settings → General. This is on by default; if it was switched off, no events are recorded.
Make sure you are not excluded. Open Logify → Settings → Exclusions and check Excluded User IDs, Excluded User Roles, and Excluded IP Addresses — an excluded user or IP produces no log entries.
Check Excluded Event Types, Excluded Post Types, and Excluded Post Statuses on the same tab. Exclusion rules drop matching activity before it is written, so nothing shows up later.
Trigger something obvious — log out and back in, or edit a post — then refresh the Activity Logs screen.

Exclusions apply before write

Exclusion rules discard events before they reach the database, so excluded activity can never be recovered — it is not hidden, it is never stored. See exclude users and activity from the log.

The country column shows "Unknown"

The country is resolved from the visitor's IP address by a background lookup that runs after the log entry is saved, so a brand-new entry can briefly show no country while the lookup completes. If the country stays "Unknown":

Private and local IP addresses (for example 127.0.0.1 or 192.168.x.x) have no public geolocation and will always show "Unknown".
A failed online lookup is cached for a while before Logify retries, so repeated local testing can keep showing "Unknown".
For reliable results without external calls, install a local MaxMind GeoLite2 database and point Logify at it with the kc_lf_geoip_database_path filter.

See how Logify determines IP address and country for the full lookup order and the related filters.

Logs disappear after about 30 days

This is retention working as configured, not data loss. Logify keeps 30 days of logs by default and purges older entries with a daily task. To change how long logs are kept:

Go to Logify → Settings → General → Maintenance.
Set Log Retention Period to 7 Days, 30 Days, or Keep Indefinitely.

"Keep Indefinitely" (value 0) disables the purge entirely. If you need a custom period such as 90 days, use the kc_lf_log_retention_days filter — see hooks and filters. For the wider picture, read data privacy and log retention.

A brute-force attack can flood the log with individual failed-login events. Logify handles this automatically: after 5 failed attempts from the same IP and username within a 5-minute window, it stops recording each failure and writes a single aggregated brute-force detected event instead (severity Emergency) for the rest of the window. So a burst of hundreds of attempts collapses into one high-severity entry that is easy to spot and alert on.

To tune the thresholds, use the kc_lf_failed_login_threshold and kc_lf_failed_login_window filters (see hooks and filters).

The email digest did not arrive

Confirm Enable Email Digest is on under Logify → Settings → Email Digest.
Check the Digest Status card on the same tab. If the last-sent time is "Never" or stale, WP-Cron may not be firing on your site.
Use Send Test to verify email delivery independently of the schedule.
Check spam and junk folders, and confirm the Recipients field is correct (blank falls back to the site admin email).

See set up the Logify email digest for the full configuration.

Real-time notifications do not reach Slack or a webhook

PRO feature

Real-time notifications to Email, Slack, a generic webhook, and Syslog are a Logify PRO feature, configured on the Logify → Settings → Notifications tab.

If a PRO notification destination is silent:

Confirm the destination is enabled and the Webhook URL is correct. Test the URL from outside WordPress (curl or Postman) to rule out the endpoint.
Check the destination's Send For Event Types and Minimum Severity — an event that does not match is not sent.
Check the Rate Limit (seconds) setting; a high value can suppress rapid follow-up notifications.
Failed network calls are silent by design and do not appear in the activity log.

See how Logify PRO sends real-time alerts and narrowing alerts by event and severity.

I set KC_LF_DEV_MODE but PRO features stay locked

KC_LF_DEV_MODE only unlocks PRO when the pro/ module is also present on disk. The free build from WordPress.org ships the lite/ code only, so PRO features stay locked no matter what the constant is set to. Install Logify PRO to get the pro/ module.

Conclusion

Most Logify issues are resolved by checking one setting — tracking, exclusions, retention, or a destination filter. If your symptom is not covered here, gather your WordPress, PHP, and Logify versions and the relevant log entries, then head to Logify support.

FAQs

Why are no events showing in my activity log?

The most common cause is that Enable Tracking was switched off under Logify → Settings → General, or an exclusion rule is hiding the activity. Check the Exclusions tab for excluded user IDs, roles, IP addresses, event types, post types, and post statuses — exclusions drop matching events before they are written, so they never appear.

How long does Logify keep logs?

By default Logify keeps 30 days of logs and purges older entries with a daily task. You can choose 7 Days, 30 Days, or Keep Indefinitely under Logify → Settings → General → Maintenance. For a custom period such as 90 days, use the kc_lf_log_retention_days filter.

Why does the country column say "Unknown"?

Country is resolved by a background lookup that runs after the entry is saved, so a new entry may briefly show no country. Private or local IP addresses (like 127.0.0.1) have no public geolocation and always show "Unknown". Failed online lookups are cached before retrying. Install a local MaxMind database via kc_lf_geoip_database_path for reliable results.

During a brute-force attack Logify records the first few failures, then after 5 attempts from the same IP and username within 5 minutes it collapses the rest of the window into a single aggregated brute-force event at Emergency severity. This keeps the log readable. Adjust the limits with the kc_lf_failed_login_threshold and kc_lf_failed_login_window filters.

Does Logify slow down my site?

No. Logify buffers log writes in memory during the request and saves them in a single batched query at shutdown, so hot WordPress hooks like wp_login and save_post do not take a database hit per event. Country lookups also run in the background after the entry is saved.

How do I completely remove Logify and its data?

Tick Cleanup on Uninstall under Logify → Settings → General → Maintenance, then deactivate and delete the plugin from Plugins. This removes the Logify database table, settings, scheduled tasks, and metadata. If you delete the plugin without enabling that option, the data is left in place.