Rollback Retention
ACF Image Auto Filler reduces repetitive image assignment, but bulk convenience becomes risky when WordPress content contains different ACF structures. A simple Image field can be mapped predictably, while repeaters, flexible content, galleries and clones introduce nested relationships that should not be guessed. Existing values also need protection when an editor does not intend to overwrite them.
The plugin therefore needed a previewable mapping workflow, optional overwrite, manual mapping, batch limits, rollback and an audit trail. The portfolio story had to explain why some field types are deliberately excluded and that content is not sent to external services. The challenge was to make large image assignments faster without sacrificing visibility, permissions or recovery when automatic order is not enough.
I built ACF Image Auto Filler around a review-first admin flow. Editors select content, supported fields and Media Library images, then see the proposed mapping before any write. Top-level ACF Image fields are supported, along with Image fields inside Groups when enabled, while featured images can be handled separately.
Existing values are skipped unless overwrite is explicitly enabled. Manual mapping, batch mode and CSV dry-run export provide more control, and saved runs can retain rollback data for the current user. An admin audit log records operations, while capability and per-item permission checks protect bulk changes. Repeaters, flexible content, galleries and clones remain excluded from automatic filling. The portfolio case now explains a bounded image-assignment workflow instead of pretending complex ACF data can be safely guessed.
