Updates

Octa Editor is not on the WordPress.org directory. It delivers its own updates from GitHub releases, so updates appear in Dashboard → Updates and on the Plugins screen like any other plugin.

How it works

The plugin checks its configured repository for a newer release and offers the built ZIP as the update. The repository and branch are fixed in code for this plugin, so the only value an operator supplies is the token.

When you need a token

A public repository needs no token. A private repository does, because the update check has to authenticate to read releases. Without a token on a private repo, the update check fails and the plugin information screen shows “plugin not found”. See FAQ.

Use a fine-grained personal access token with Contents: read on the repository, ideally from a dedicated machine account rather than a personal one.

Where the token is read from

The token resolves in this order.

1. The OCTA_EDITOR_UPDATE_TOKEN constant in wp-config.php.
2. The value saved on Tools → Octa Editor → Settings.
3. The octa_editor_update_token filter.

The constant wins when present, which suits hosts that manage secrets in wp-config.php. The Settings field suits hosts where wp-config.php cannot be edited.