Skip to content

FAQ and troubleshooting

“View details” shows “plugin not found”

Section titled ““View details” shows “plugin not found””

The update check could not read the repository, so WordPress fell back to WordPress.org, where the plugin does not exist. On a private repository this means the update token is missing or wrong. Set a fine-grained token with Contents: read under Tools → Octa Editor → Settings. See Updates.

Two common causes. Either no token is set for a private repository, so the check cannot see releases, or the installed version is already the latest release. Use Check for updates on the Plugins screen to force a fresh check.

Too many failed Basic Auth attempts triggered the throttle (octa_too_many_attempts). Wait for the window to pass and retry with correct credentials. Make sure you are using an application password, not the account’s login password. See REST API overview.

Someone changed the record between the time it was read and the time you saved (octa_conflict). This is the optimistic lock protecting the other edit. Reload the current version and re-apply your change.

The field key probably does not match the field definition, so it raised octa_unknown_field and was dropped. Field names must match exactly, including nested keys. Export a pattern record and change only the values. See Preparing JSON files.

For hierarchical types such as pages, a slug can exist under different parents, so a bare slug is ambiguous (octa_slug_ambiguous). Include parent (the parent slug), or match by _match.id. See Record identity.

That is by design. Octa Editor only creates and updates, and a trash status is rejected. Remove content through WordPress itself.