If an extension will not activate, start in Extensions and check its current state and the latest message. Cedros uses Enable for activation: an extension can be installed successfully while still being Disabled.
An extension that already shows Enabled needs a different check. Its package may be running while its own configuration, a connected service, or a page it adds still needs attention.
Check the installed state first
- Open Extensions in the intended site's admin and find the extension. Clear any search or status filters that might hide it.
- Open its details and note the name, package ID, version, and current state.
- Read the latest error or requirement shown on the page. If an action is still running, wait for its result before trying again.
- If it is installed but Disabled, review its requirements and requested access before using the enable switch or Approve & enable, when offered.
- After the action finishes, confirm the state and test the feature itself. Keep any error text if the extension remains disabled or the feature is still unavailable.
If the package is not installed, follow Finding and installing an extension first. An available marketplace listing is not the same as an installed extension.
If you see a message that installed extension state could not be refreshed from the server, treat the displayed state as potentially out of date. Restore your connection or access, reload the page, and check again before repeating installation or enablement.
If the enable control is unavailable
Open Access requested and review Access and Compatibility where those details are present. Expand Compatibility to read the individual checks instead of relying only on a summary count. A package that has not yet been installed may instead show Resolve before installing.
A disabled switch does not identify one universal problem. It can mean that a requirement is unmet, approval is needed, or your account or hosting environment cannot perform the action.
If Approve & enable is offered, read what the extension can access and change before selecting it. That button approves the displayed access and starts enablement. Approval does not satisfy a separate missing dependency or compatibility requirement.
If you can view an extension but cannot manage it, ask the site owner to review your feature and settings access. Access to the extension's own admin page can also differ from permission to manage its installation.
When the page says the host does not support the action, ask the site administrator or hosting provider to resolve that limitation. Repeatedly clicking the switch or uploading the same package will not add the missing support.
Resolve missing dependencies and compatibility requirements
Read the name and details of each failed check. The next step depends on what is missing:
- Another extension is required: find that extension in Extensions, confirm it is installed, and check that it is enabled. An installed but disabled dependency does not satisfy an activation requirement.
- A particular dependency version is required: compare the installed version with the stated requirement. Follow the publisher's supported update instructions rather than assuming any newer or older version will work.
- A service or capability is unavailable: ask the site owner which service or extension should provide it and whether it is ready on this site.
- The platform version is incompatible: ask the site administrator and package publisher for a compatible combination of site version and extension package.
- The error identifies a conflicting page route: record the route and the extensions or content named in the error. Have the site owner or publisher resolve ownership before trying to enable it again.
Resolve the named requirement before returning to the original extension. Avoid disabling unrelated extensions or deleting pages simply to make a check disappear.
For a dependency update, Updating, disabling, or removing an extension explains how to review the effect on other features and verify the installed version afterward.
If enabling fails after you select it
Read the result message and check the current state before retrying. A request can fail before enablement, or a later setup step can fail after the extension has already become enabled.
An error about package verification, an untrusted package, a missing server component, or inconsistent state needs the site administrator or publisher's attention. Provide the exact message and package version. Do not modify package files or try to bypass the check.
For a connection or session problem, restore access, reload Extensions, and confirm which state was saved. Retry the available enable action only after the problem is resolved and the extension still needs enabling. Avoid repeatedly switching it off and on while another action is running.
If this followed a private ZIP upload, distinguish upload success from install and enable success. The file can be accepted even when a later step fails. Follow Uploading a private extension for package validation and re-upload recovery. Selecting the ZIP again can start installation and enablement automatically, so check the current state first.
Keep data while investigating. Uninstalling with Delete data is not a routine fix for activation: it can erase the extension's settings, secrets, and stored information without resolving the original requirement.
If it is enabled but the feature is missing
Check What this added to find where the extension's features belong. Some provide a separate admin page; others add a component or tool to an existing editor. A missing Open … button alone does not mean activation failed.
When an Open action is available, use it and complete the extension's setup instructions. Check required connections and configuration there. If another authorized teammate can open the page and you cannot, ask the site owner to review your access.
For a public feature, inspect the specific page or component and test it as a visitor. Confirm that the content is published and that the feature has been added or configured where you expect it. Enabling an extension does not place every optional component on your site automatically.
If setup reports a failure while creating pages or other site items, record that failure separately from the enabled state. The extension can remain enabled even when those additions are incomplete. Ask the site administrator or publisher how to finish the failed setup rather than treating a new install as the default remedy.
After an update, also check the publisher's instructions for changed settings or requirements. A successful version change does not establish that every feature is ready.
Verify recovery
- Return to Extensions after addressing the specific error or requirement, and refresh the page so you are checking the current state.
- Enable the extension if it is still disabled and the action is available. Review any access request before approving it.
- Confirm Enabled, then open the relevant admin page or editor and check the extension's configuration.
- Test the feature that originally failed and verify any expected page or record. Check the visitor experience as well when the feature is public.
Use the current state and newest result to judge recovery. An earlier failure does not mean the latest attempt failed, and an enabled switch does not prove that a form, page, or connected service works.
If the same failure returns after its stated cause has been addressed, stop repeating the action and collect the details below.
What to include when asking for help
Send the site administrator or extension publisher:
- The extension name, package ID, and installed version.
- Whether it shows Enabled, Disabled, or another state after refreshing.
- The exact error or failed requirement, including any named dependency, version, or route.
- Whether it came from the marketplace or a private ZIP, and whether the problem began after an install or update.
- The action you selected, what happened, and which page or feature still fails.
- Whether the problem affects all authorized users or only your account.
Include a screenshot of the relevant message if useful, leaving out credentials, secrets, and customer information. This gives the administrator or publisher a specific failure to investigate without asking you to repeatedly reinstall the extension.