Common Issues
A fix says “stale”#
Cause: the post was edited after the fix was proposed, so the proposal no longer matches. Nothing was written.
- Open Fix Queue > Issues and find the issue again (a re-scan runs when the post is saved).
- Click Propose fix to create a new proposal from the current content.
- Review and approve it.
A fix says “failed” and the content was restored#
Cause: another plugin or a content filter changed the saved content, or the current user lacks the unfiltered_html capability and WordPress stripped part of the markup. The plugin restored the snapshot.
- Open Fix Queue > History and read the reason in the log.
- Check for a plugin hooking
content_save_pre, or approve as a user who hasunfiltered_html. - Propose the fix again.
Approve is disabled and the Queue says the editor would reject the markup#
Cause: the proposed result would not pass the block editor’s validation, so the plugin blocks it.
- Do not force it. Fix the block by hand in the editor.
- Re-scan the post.
An issue is marked manual#
Cause: the plugin does not understand the block’s saved markup well enough to change it safely, or no safe automatic answer exists (for example, no palette colour passes the contrast ratio). No content is touched.
- Open the post in the editor from the issue.
- Make the change by hand, following the guidance on the issue.
A template can’t be fixed#
Cause: it is a theme file, not a template stored in the database. Only customised templates are editable.
- Open the Site Editor and customise the template so it is saved in the database.
- Re-scan and propose the fix again.
The AI button says to connect a provider#
Cause: AI proposals are off, or no text-generation provider is connected.
- Connect a provider under Settings > Connectors.
- Tick AI proposals in Fix Queue > Settings.
Roll back is refused#
Cause: the post was edited after the fix, and the changed block no longer matches what the fix produced.
- Open the link to the post’s revisions in the message.
- Restore the revision you want.