Updates
CanAI installed as a normal plugin updates through the standard WordPress update screens, fed by a published release file.
What it is
A site that has CanAI in wp-content/plugins/canai checks https://wpmanage.web.app/wpcanai/info.json for the newest release. When that file lists a version higher than the one installed, WordPress shows the usual "update available" notice and installs the package the file points to. The Download button on the guide's home page reads the same file.
You use the tools you already know:
- Plugins list: the update notice, Update now, and a "Check for updates" link on the CanAI row. View version details opens the details modal, which shows the description from the release file (there is no changelog in it).
- Dashboard → Updates.
- The per-plugin Enable auto-updates toggle. CanAI does not force it on; it stays your choice.
- WP-CLI:
wp plugin update canai, orwp plugin auto-updates enable canai.
The release file only offers the latest version. There is no rollback in WordPress; to go back, install an older zip yourself.
Check the update channel
Open CanAI → Tools → Diagnostics and find Plugin updates, or ask an agent to call wpcanai/diagnostics. The row also shows in Site Health. It reads the last known result without a network request. The Diagnostics run that includes the network probes (include_network over MCP) refreshes it first.
| Value shown | Meaning |
|---|---|
| Up to date (1.97.1) | Nothing newer is published. |
| 1.98.0 available (installed 1.97.1) | Update from Plugins, or wp plugin update canai. |
| Update check failed | The last check against the host failed; the message says why. |
| Not applicable (mu-plugin or symlinked install) | WordPress cannot update plugins in this layout. |
| Disabled | Update checks are switched off on this site. |
| Library missing | The bundled vendor/ folder is incomplete. |
Point a site elsewhere, or switch checks off
Add to wp-config.php before the "stop editing" line:
define( 'WPCANAI_UPDATE_URL', 'https://staging.example.com/canai/info.json' );
// or switch update checks off:
define( 'WPCANAI_UPDATE_URL', '' );
Developers can do the same with the wpcanai_update_metadata_url filter. Only https:// addresses are accepted; anything else disables the check.
If something looks wrong
- No update ever appears. Check Plugin updates in Diagnostics. A CanAI loaded as a must-use plugin (
mu-plugins) or through a symlink reports "Not applicable"; whoever deployed it delivers new releases. - "Update check failed". The server could not reach
wpmanage.web.app. IfWP_HTTP_BLOCK_EXTERNALis on, add that host toWP_ACCESSIBLE_HOSTS. Otherwise check your firewall and DNS (Diagnostics also has outbound HTTPS checks). - "Library missing". Re-upload the plugin including its
vendor/folder. - "Disabled". Look for
WPCANAI_UPDATE_URLinwp-config.phpor awpcanai_update_metadata_urlfilter in a snippet. - Update fails after download. CanAI needs PHP 8.1+, and the package must include its
vendor/folder. - The starter theme did not change after updating. The bundled
wpcanai-emptytheme is copied once and never overwritten, so your edits are safe, but new theme files do not arrive on their own.