Integrations
How to Track ACF Deletions with Logify
Deleting an ACF-registered post type or taxonomy can make custom sections of a site stop displaying, and it is rarely obvious afterwards what changed. Logify PRO records these ACF deletions in the activity log, so you can see what was removed, who removed it, and when — without checking every template or asking every administrator. The integration turns itself on automatically when Advanced Custom Fields is active.
PRO feature
ACF logging is part of Logify PRO and loads only when the Advanced Custom Fields plugin is installed and active.
What ACF activity does Logify record?
This integration is deletion-focused. When an ACF-registered custom post type or taxonomy definition is permanently deleted, Logify writes an activity under the acf event type with the deleted action, the affected item, the user, and the timestamp.
| Activity | What it captures | Action |
|---|---|---|
| ACF post type deleted | An ACF-registered custom post type definition is permanently deleted | deleted |
| ACF taxonomy deleted | An ACF-registered taxonomy definition is permanently deleted | deleted |
Deletions only — not field edits
This integration records deletions of ACF post types and taxonomies. It does not log field-value edits or changes to individual field groups. General content changes are covered by Logify's core post and taxonomy logging, which works in the free version.
Why deletion tracking helps
Removing an ACF post type or taxonomy can quietly break custom areas of your site. Instead of guessing what happened, Logify gives administrators an activity history to investigate the change.
- See when an ACF post type or taxonomy was deleted.
- Identify which user performed the deletion.
- Investigate unexpected missing custom content.
- Review website changes during troubleshooting.
- Improve accountability when multiple administrators manage the site.
Who is this for?
- WordPress administrators
- Website owners and developers
- Agencies managing client websites
- Teams using Advanced Custom Fields
No programming knowledge is required to read the activity logs.
How to view ACF deletion activity
Once Advanced Custom Fields and Logify PRO are both active, supported deletions are recorded automatically — you keep using ACF as usual.
Step 1: Open the activity log
From your WordPress dashboard, go to Logify → Activity Logs.
Step 2: Filter to ACF
Set the Event Type filter to the ACF entry — it appears in the dropdown (labeled from the event type) once at least one ACF deletion has been recorded — and click Filter. If it is not yet listed, type the deleted item's name into Search.
Step 3: Review the deletion
Click the view (eye) icon to open the entry and see the affected item, the user who performed the deletion, and the date and time.
Example use case
A custom Product Details area suddenly disappears from several pages. Instead of checking every template or asking each administrator, open Logify → Activity Logs and review recent ACF deletion activity. If a related post type or taxonomy was deleted, the entry names the user and the time, so the change is quick to identify.
Conclusion
ACF deletion logging gives you an attributed record of when an ACF post type or taxonomy is removed, turning a mysterious "the custom section is gone" into a clear who-and-when. Because it is automatic with Logify PRO, there is nothing to configure. For a broader view of structural changes, see the WordPress activity log overview.
FAQs
What ACF activity does Logify track?
Logify records deletions of ACF-registered custom post types and taxonomies. When one is permanently deleted, an entry is written under the acf event type with the deleted action, naming the affected item, the user, and the timestamp. It is a deletion-focused integration rather than a full change log.
Do I need to enable ACF tracking manually?
No. ACF deletion tracking is part of Logify PRO and works automatically when both Advanced Custom Fields and Logify PRO are active. There is no separate setting to switch on; supported deletions are recorded as they happen.
Does Logify record every ACF change?
No. This integration focuses on supported deletions of ACF post types and taxonomies. It does not log field-value edits or every ACF operation. Broader content changes are covered by Logify's core post and taxonomy logging, available in the free version.
Can Logify restore a deleted ACF post type or taxonomy?
No. Logify records the activity history but does not restore deleted data. Use your normal backup or recovery process if you need to bring the deleted structure back. The log helps you identify what was removed and by whom so you know what to restore.
Does this replace website backups?
No. Backups help you recover your site, while Logify helps you understand what changed and when. They serve different purposes — keep taking backups, and use Logify to investigate and attribute changes across your WordPress site.