Extensions add optional capabilities to your Cedros site. Start with the outcome you need, find a suitable extension, then review what it changes and what access it requests before installing it.
Installation and setup are separate steps. An extension can be installed but disabled, and an enabled extension may still need its own configuration before customers can use it.
Find an extension for your site
- Open Extensions in your site's admin and check the installed list first. The feature you need may already be installed but switched off.
- Select Browse extensions to see additional extensions available through your site's marketplace.
- Use Filter extensions… to narrow the results. Adjust Categories and the All, Installable, or Unavailable filters as needed.
- Select View details for a candidate. Read its description, publisher, and version, then review its changes and requirements.
- Compare the extension's stated features with the outcome you need before choosing to install it.
You can also browse the public extension directory before signing in. It contains public listings, while your site's marketplace reflects the catalog and compatibility information available to that site. A public listing is not a guarantee that the extension can be installed on every site.
If a result disappears while filtering, return the availability and category filters to All and clear the search text. No marketplace extensions match this search is different from No additional extensions are available.
Use View details when you want to inspect an extension. Install on a marketplace card starts the installation action and can approve the requested access as part of that action; it is not a button for opening the review page.
Review what installation adds
On the detail page, open the groups under What installing adds. The groups appear when the extension declares items in them:
- Added to your site lists things created when the extension is enabled, such as pages, forms, docs, or scheduled jobs.
- In your admin lists the pages or sections where you will manage its features.
- Available to use lists optional components or tools that become available for you to choose.
Check individual page routes and whether pages are marked draft or published. Some extensions can create published pages when enabled. Do not assume every page they add will wait for a separate publishing step.
Other items are offered for later use. For example, a component becoming available does not mean it has been placed on your homepage. Review what the extension will create automatically and what you will still need to add or configure.
If you plan to edit content it creates, Understanding drafts, previews, and publishing explains how to check the saved and public versions.
Check access and compatibility
Open What it needs and expand Access. Read the areas the extension can reach and why it needs them. Where available, Can make changes and Read-only distinguish access that can modify information from access that only reads it. Show technical permissions provides the detailed permission names when you need them.
Decide whether the requested access fits the feature you intend to use. If a package reports permissions without describing them, ask the publisher or site owner for clarification before approving it.
Expand Compatibility to inspect its checks. If Resolve before installing appears, address the listed requirement first. A requirement can concern the site's supported platform version, another extension, or a service or capability the site needs to provide.
For a missing dependency, check whether the named extension is installed and enabled. If the requirement concerns the hosting environment or a platform version, ask the site owner or hosting administrator to resolve it. Approving access does not satisfy a separate compatibility requirement.
The actions available to you also depend on your account's permissions. If you can read the details but cannot install or enable the extension, ask the site owner to review your feature and settings access.
Install and enable the extension
- Return to the extension's detail page after reviewing its changes, access, and compatibility.
- Select Install, or Approve & install when that combined action is shown. Use it only once you are ready to approve the displayed access and start installation.
- Wait for the action to finish. Read any error or follow-up message, then confirm that the extension appears in the installed list with the expected version.
- Check its state. If it is Disabled, use its enable switch. If Approve & enable is offered, review the access request before using that action.
- Confirm that it shows Enabled, then open the extension's own admin page when an Open … action is available.
Installing a package does not by itself prove that it is running. The installed list, version, and enabled state are useful checks; a button returning to its idle state is not enough.
Enabling can make the extension's admin features available and create the site items you reviewed earlier. Check those changes before inviting customers to rely on the feature.
If an action fails, read the error and check the current installed state before retrying. The package may be present even when a later step needs attention. Repeating installation is not a substitute for resolving a failed enable or missing prerequisite.
Upload extension is a separate path for a Cedros extension ZIP supplied to you privately. Use Browse extensions for marketplace discovery. A private ZIP needs its own package review; it is not necessary for an ordinary marketplace install.
Finish setup and verify the result
Open the extension's settings or admin page and complete its setup instructions. Depending on the extension, this can include choosing options, connecting a service, or preparing content. An enabled switch does not confirm that those steps are complete.
The detail page changes to What this added after installation. Use it to review the extension's site and admin additions. Access requested remains available so you can revisit the permissions later.
Not every extension provides a separate admin page. Some add components, templates, or other tools to an existing editor. Use In your admin and Available to use to find where the extension's features belong. A missing Open button is not, by itself, evidence that installation failed.
Check the outcome you installed it for:
- Open any relevant admin page and confirm that its setup is complete.
- Review created pages at their listed routes and check whether they are drafts or public.
- If it offers an optional component or template, select it in the appropriate editor and preview the result.
- Follow the extension's documented test flow for the customer action you need, then confirm the expected result.
Keep the test appropriate to the feature. Seeing a checkout page, for example, does not verify a completed payment. Use the feature's test process before relying on it for real transactions.
Reopen Extensions after setup to confirm that the expected version and enabled state remain visible. If you no longer want the extension running, use its disable control when available. Disabling should not be treated as undoing every page, record, or external action it has already created.
Resolve a missing or blocked installation
You cannot find the extension. Check the installed list, clear marketplace filters, and compare the publisher and name. A public listing may not be available through your site's catalog. Ask the site owner about availability rather than installing a different package with a similar name.
Install is unavailable. Open View details and read Resolve before installing, Compatibility, and any action message. Address the named blocker. Access approval cannot override a missing dependency or an unsupported site capability.
The package could not be downloaded or verified. Keep the exact error and version. Retry after a temporary connection problem is resolved. If the message identifies a package or verification problem, ask the publisher or site owner to resolve it; do not alter the package just to get past the check.
The extension is installed but not active. Check the enable switch and any pending access review or requirement. If enabling fails, investigate that message rather than reinstalling immediately.
The extension is enabled but its page or feature is missing. Check what it actually adds, your access to that feature, and any remaining setup. Return to its details and look for an Open action. Optional components may need to be selected in an editor before they appear on the public site.
Installed state could not be refreshed. Treat the visible state as potentially out of date. Reload Extensions and check whether the error clears before taking another action. A refresh failure does not prove that installation failed.
Keep the details needed for help
If the issue continues, give the site owner or publisher the extension's name, publisher, version, the action you attempted, and the exact error. Include whether it appears in the installed list and whether it is enabled.
A useful example is: “The extension appears as installed at this version, but enabling it reports a missing dependency.” That identifies the failed step more clearly than “the extension does not work.”
Share screenshots of the relevant status or requirement with private information removed. Keep credentials in the service's normal setup fields rather than including them in a support message.