Plugins

Update or repair a plugin

Keep installed plugins current, and bring back one that failed to start.

Update one plugin

Open Settings and choose Plugins.
Open the action menu of a plugin that has a newer version and choose Update.
Approve any additional permissions the new version asks for. Declining leaves that plugin's current version untouched.
Wait for the plugin to show Applied.

Update all plugins

Choose Update all plugins and confirm.
Wait for the run to finish.

Chetty updates the enabled plugins together, with one short restart, so several updates never mean several restarts. Disabled plugins stay disabled, and they are updated when you enable them.

Manual install, update and repair requests work even with automatic updates turned off.

Repair a plugin that cannot start

An installed plugin that cannot start stays listed as Not loaded, with the reason and a Repair button.

Read the reason first; it often names a missing permission or an incompatible version.
Choose Repair. It joins the same queue and the same startup check as an update.
Chetty also requests repair for missing or unloaded enabled publisher plugins at boot, but it does not keep retrying a version whose startup check already failed.
Your organization's own plugins are reported, not replaced.

Read the outcome

A request can end in any of these ways. Read the shown reason before you retry.

Applied — the plugin was updated.
Skipped — Chetty deliberately left this plugin out of the run, for the reason shown.
Consent required — approve the permissions it asked for and retry.
Not licensed — your licence does not cover this plugin. See Licence and activation.
Cancelled before execution — a newer request, or a changed approved download, replaced this one before it ran.
Failed — the run failed; retry after reading the reason.
Operator attention required — preserve the update files and recover with elowen update --recover, or contact the administrator of the host. See Update Chetty on a server.

Restarts and connected users

Changes to ordinary plugin configuration or to a plugin's enabled state keep their daemon restart behaviour. Connected chat users see the restart notice, and recoverable work resumes after boot.

Continue with Plugins, Install and update plugins and Follow an update in the web app.