Updating, disabling, or removing an extension

Use Extensions to apply a new version, switch an extension off temporarily, or uninstall it. These actions have different effects on the package and its saved data.

Action	What to expect
Update	Replaces the installed version. Check access, requirements, and behavior afterward.
Disable	Keeps the extension installed and retains its settings and data. Use it to stop its features temporarily.
Uninstall with Keep data	Removes the extension while retaining its saved settings and data for a later reinstall.
Uninstall with Delete data	Also deletes the extension's server-stored settings, secrets, and data. Treat this as permanent.

Disabling or uninstalling an extension is not a general undo for changes it has made to your site. Check affected pages, customer journeys, and integrations separately.

Check the impact before changing an extension

Open the extension's details and note its name, package ID, installed version, and enabled state. Review What this added and the publisher's instructions to identify the pages, admin tools, components, and services that rely on it.

Check whether customers or teammates are using those features. For a feature used on public pages, plan how those pages should behave while it is unavailable. Removing a component's extension does not automatically redesign the page around its absence.

Also check other extensions' requirements. Cedros can block disabling or uninstalling an extension when another enabled extension declares it as a required dependency. If a message names a dependent extension, decide whether its features can be stopped before disabling it first. Do not switch off a chain of extensions without reviewing the effect on your site.

If you cannot use a control, read its explanation and ask the site owner to check your feature and settings access. A disabled button can reflect permissions, a missing requirement, or an action the site does not support.

Update an installed extension

1. Open Extensions and find the installed extension. Use the Updates filter to narrow the list to Updates available when needed.
2. Open its details and compare the installed version with the available version. Review the publisher's release instructions and any changed access or compatibility requirements.
3. Resolve any blocking requirement. If approval is requested, review the access before choosing Approve & update.
4. Otherwise, use the available update action. The Update control in the installed list starts the action; it is not just a version check. Wait for the result before trying again.
5. Confirm the new installed version and enabled state, then test the feature the extension provides.

An update may need new permissions or dependencies. Do not assume an extension is ready simply because the version changed: check whether it is enabled, complete any new setup, and review the affected public pages or tools.

If the update control says Up to date, there is no update action available from the site's current catalog. That does not promise that every privately distributed build is listed there. If your publisher supplied a ZIP instead, follow Uploading a private extension. Selecting that file can automatically update or reinstall the existing extension and attempt to enable it.

Keep the publisher's recovery instructions available for important changes. Do not assume uploading an older ZIP safely reverses a newer version's data changes.

Disable an extension temporarily

1. Find the extension in Extensions and check that it currently shows Enabled.
2. Use its enable/disable switch in the installed list or on its detail page. Switching it off starts the disable action.
3. Wait for the result and confirm that its state is Disabled. If Cedros reports a dependency or permission problem, resolve that before retrying.
4. Check the public pages and admin workflows that used the extension, and adjust any links or content that now lead to an unavailable feature.

Disabling keeps the package installed and preserves its settings and data. It stops the extension's enabled features; it does not delete the records it previously created or reverse completed work in another service.

To use it again, switch it on and wait for Enabled. If Approve & enable is shown, review the requested access before proceeding. Resolve any missing dependency or configuration, then test the feature again. Re-enabling is not a guarantee that external connections or extension-specific setup are still ready.

Choose what to keep when uninstalling

The uninstall dialog has a Data choice. It defaults to Keep data.

Keep data retains the extension's saved settings and data for a later reinstall. Choose it when you want to remove the package without intentionally erasing its stored information. You will still need a compatible package to reinstall; keeping data does not keep the extension's features running.

Delete data also deletes the extension's settings, secrets, and stored data on the server. Only choose it when you no longer need that information and have saved anything you need using the extension's supported export or backup process. Reinstalling the package is not an undo for this choice.

Customer records and tags the extension created are kept as your site's data. Do not use Delete data as a way to erase a customer or remove every trace of the extension across the site. Review shared site content and any connected external service separately.

If you do not know what the extension stores, ask its publisher or your site administrator before choosing Delete data. The confirmation changes from Uninstall and keep data to Uninstall + delete data, so read the final button before confirming.

Uninstall the extension

1. Open Extensions, find the correct package, and review its details and dependencies.
2. Select its trash icon, labeled Uninstall or Uninstall extension, to open the confirmation dialog.
3. Check the extension name in Uninstall …? and choose Keep data or Delete data in the Data field.
4. Read the consequences and select the matching confirmation button. Use Cancel if you are not ready; opening the dialog alone does not uninstall the extension.
5. Wait for the result, then confirm it is no longer in the installed list. Check the pages, navigation, and workflows that used its features.

If a dependency blocks removal, the error identifies an extension that still needs this one. Review that dependent feature before disabling it and retrying. A required service should remain installed and enabled while you still need the extensions that depend on it.

Removing a private extension can also remove its uploaded package from the site's available choices. Keep the publisher's original ZIP or a way to obtain a supported replacement if you expect to reinstall later.

Verify the result and recover from errors

Check both the extension's state and the feature itself. After an update, confirm the expected version. After disabling, confirm Disabled. After uninstalling, confirm it is absent from the installed list. Then check the actual page, form, component, or admin tool affected by the change.

If the result is unclear, refresh Extensions before repeating the action. An error does not always identify which earlier steps completed, and a button becoming available again does not establish success.

• An update fails: read the error, check which version is still installed, and resolve any access or compatibility requirement before retrying.
• Disabling or removal is blocked: address the named dependency or ask the site owner to review your permissions.
• Removal reports a data-deletion failure: do not assume the data was deleted. Keep the error text and have the site administrator check the result before another attempt.
• A feature stops working after an update: record the old and new versions, current enabled state, and exact failure for the publisher. Avoid repeatedly reinstalling different builds without recovery instructions.
• You want an uninstalled extension back: obtain a compatible package and follow Finding and installing an extension. If you kept data, check that its settings and records are available after reinstalling and enabling it.

Review remaining site content

Check navigation links, published pages, and content that referred to the removed or disabled feature. Some shared content can remain even when the extension is gone; other pages may still contain a component that needs it to render or work.

Edit or unpublish those items deliberately rather than assuming uninstall will clean them up. Understanding drafts, previews, and publishing explains how to review the saved and public versions before changing what visitors see.

When asking for help, include the package ID, version, action you selected, data choice if applicable, exact error, and the state shown after refreshing Extensions. Explain which page or workflow is affected, without including credentials or customer information.