Content Guard Pro automatically resolves findings when you fix the issue and save the post. This feature streamlines your workflow by eliminating the need to manually mark findings as resolved.

How Auto-Resolution Works #

The Process #

1. You open a post that has existing findings
2. You edit the content to remove the malicious element
3. You click Save or Update
4. Content Guard Pro scans the saved content
5. If no issues are found, existing findings are marked Resolved

What Gets Resolved #

• All “open” findings for that specific post
• Only findings that were previously detected
• Only when save-time scan finds zero new issues

What Doesn’t Get Resolved #

• Findings for other posts
• Findings in post meta (if meta wasn’t fixed)
• Findings from manual scans (only save triggers resolution)

Why Only on Save? #

Auto-resolution only happens when content is actually saved to the database. This prevents a critical edge case:

The Problem with Manual Scan Resolution #

Imagine this scenario:
1. User opens post with malicious content
2. User manually scans (clicks “Scan” button)
3. Scan checks editor content (not database)
4. Editor happens to be clean (perhaps user made changes)
5. If findings were auto-resolved…
6. User navigates away without saving
7. Malicious content still in database, but findings marked resolved!

The Solution #

By only resolving on save:

• Database content is guaranteed to be what was scanned
• No mismatch between scanned content and stored content
• Findings accurately reflect database state

User Experience #

In the Editor #

When you save a post that had findings:

If content is now clean:

✓ Scan complete: No issues found.
  Previous findings have been resolved.

If issues remain:

⚠ Scan complete: 2 issues found.
  See details below.

In Findings List #

Resolved findings show:

• Status: Resolved
• Resolution method: “auto_scan_on_save”
• Timestamp of resolution
• User who saved the post

Manual Scan Behavior #

When you manually scan (click “Scan” in editor):

If Clean and No Existing Findings #

✓ No issues found.

If Clean but Existing Findings in Database #

✓ Current content appears clean.
  Save to resolve existing issues.

This message clarifies that:

• The content you’re viewing is clean
• But database may have different content (if you haven’t saved)
• Saving will trigger auto-resolution

Resolution Metadata #

When findings are auto-resolved, metadata is stored:

{
  "resolved_by": {
    "method": "auto_scan_on_save",
    "timestamp": "2025-01-15T10:30:00Z",
    "user_id": 1
  }
}

This metadata:

• Provides audit trail
• Distinguishes auto-resolution from manual resolution
• Records who saved the post

Viewing Resolved Findings #

Resolved findings remain in the database for audit purposes:

1. Go to Content Guard Pro → Findings
2. Set Status filter to Resolved
3. View all auto-resolved and manually resolved findings

Each resolved finding shows:

• Original detection details
• How it was resolved (auto or manual)
• When it was resolved
• Who resolved it

When Auto-Resolution Doesn’t Trigger #

Finding Remains Open If: #

1. Issues still exist – Content still contains threats
2. New issues found – Different threats detected
3. Scan disabled – On-save scanning is turned off
4. Scan failed – Error during save-time scan (fail-open policy applies)

For Post Meta Issues: #

If the finding was in post meta:

• Post content scan won’t detect it
• Need to fix the meta and re-scan
• Consider manual resolution

Manual Resolution Option #

If auto-resolution doesn’t apply, you can manually resolve:

1. Go to finding details
2. Click Mark as Resolved
3. Optionally add a note explaining the resolution
4. Status changes to Resolved

Re-opening Resolved Findings #

If the same threat returns:

• A new finding is created (new fingerprint if content differs)
• Resolved findings remain resolved
• You’ll be alerted to the new finding

Best Practices #

For Clean Remediation #

1. Edit the content to remove malicious elements
2. Save/Update the post
3. Verify the “resolved” confirmation message
4. Check the Findings list to confirm resolution

When Issues Persist #

1. Check the new findings in the editor panel
2. Review what wasn’t fixed
3. Make additional edits
4. Save again and verify

For Post Meta Issues #

1. Fix the meta content (custom fields, ACF, etc.)
2. Save the post
3. Manually resolve the finding if needed
4. Or run a new scan to verify

Troubleshooting #

Finding Not Resolving After Save #

1. Ensure on-save scanning is enabled
2. Check if the issue is in post content vs. meta
3. Verify the exact malicious content was removed
4. Look for similar but different content

Wrong Finding Resolved #

If a finding was incorrectly resolved:
1. It cannot be “un-resolved” automatically
2. A new scan will re-detect if issue exists
3. New finding will be created with new timestamp