Uploading a private extension

A private extension is a Cedros extension ZIP supplied directly by its publisher or developer. Use Upload extension when you already have that package. To find an extension through your site's marketplace, start with Finding and installing an extension.

Selecting or dropping a ZIP starts the upload and can automatically install and enable the extension. Review the package's purpose, access, and expected site changes before choosing the file. Do not rely on a separate confirmation screen to pause the process.

Prepare the package before uploading

Ask the publisher for a complete, built Cedros extension ZIP, its name and version, setup instructions, and any requirements your site must meet. A source-code download or a folder you compressed yourself may not contain the files Cedros needs.

Confirm that the package is intended for this site and that you trust its publisher. Ask what information it can read or change, which admin features it adds, and whether enabling it creates pages, content, forms, or scheduled work. Some extensions can create published pages automatically.

Check the installed list in Extensions before proceeding. A package with the same extension ID can update or reinstall an existing extension; uploading another ZIP does not necessarily create a separate copy. If you meant to add a different extension, clarify the package identity with its publisher first.

Keep the original ZIP and the publisher's instructions available. Uploading it to your site does not publish it in the public extension directory.

Upload the ZIP

1. Open the intended site's admin and select Extensions.
2. Find Upload extension and its Private package area.
3. Select Upload package and choose the ZIP, or drop one ZIP into Drop a .zip here. Choosing or dropping the file starts the process immediately.
4. Wait while the package is checked. Keep the page open and follow the progress as installation and enablement begin, or read the error if a step stops.
5. Check the resulting extension's name, version, and state in Extensions before treating the upload as complete.

Upload one package at a time. A message that the file was uploaded confirms receipt of the package; it does not prove that installation, enablement, and the extension's own setup all succeeded.

If the upload control is unavailable, check your feature and settings access with the site owner. Local package upload is unavailable on this host means the site's hosting environment does not provide that upload option. Changing the ZIP's name will not make the control available.

Follow installation and setup

During automatic setup, Setting up … shows the extension being processed. Its steps distinguish Install extension, Enable extension, and Set up pages, content, and automation. Finishing setup means that follow-up work is still being processed.

Let the current action finish before trying again. If the page returns to Extensions, check the installed version and whether the extension is Enabled or Disabled. Returning to the list alone is not confirmation that every added page or feature is ready.

An extension may be installed but unable to enable because it needs another extension or service. Read the listed requirements and resolve the named problem. If it concerns the hosting environment or a supported platform version, ask the site owner or hosting administrator for help.

When the result says the extension is installed and offers Enable extension, installation has completed but activation still needs attention. Use that action only when you are ready for the extension to run and make its expected site changes.

If a review screen appears

Some uploads stop at Review extension or an update/reinstall screen instead of continuing automatically. Use this opportunity to check the package identity, included items, permissions, and compatibility before proceeding.

Under What installing adds, distinguish automatic site additions from items added to your admin or made available for later use. Check whether any created pages are drafts or published. Review Access requested and any new permission requested notice, and address Resolve before installing when it appears. Technical details includes the package ID and version for comparison with the publisher's instructions.

For a new installation, Install and enable starts both steps. Install without enabling installs the extension without activating it. A package for an existing extension may instead offer Update or Reinstall actions. Reinstalling applies the uploaded build to the existing extension.

Do not assume an update labeled without enabling switches off an extension that is already enabled. Check its current state in Extensions when the action finishes.

If the package or requested access is unexpected, use Cancel while that review is still waiting for your decision. This is not an undo action for installation or setup that has already run.

Verify the extension on your site

1. Confirm that Extensions shows the expected package and version. Check the ID in its details if names are similar.
2. Confirm its enabled state. If it is disabled or blocked, resolve that state before expecting its features to work.
3. Open its admin page when an Open … action is available, and complete the publisher's setup instructions.
4. Review any pages, forms, content, or scheduled work it adds. Check public pages as a visitor as well as checking their saved state in the admin.
5. Try the specific feature you installed it for using a suitable test example, and confirm the expected result before relying on it for customers.

Not every extension has a separate admin page. Some add components or tools to an existing editor. Check the extension's listed additions and instructions to find where its features are used.

For created content, Understanding drafts, previews, and publishing explains how to compare the saved and public versions. An enabled extension can still need configuration, and a completed setup screen is not a substitute for checking the resulting pages and features.

Resolve a failed upload or installation

Start with the exact error and the extension's current state. An upload can fail before installation, while an install can succeed and a later enable or setup step can fail. These situations need different fixes.

• The ZIP is rejected. Ask the publisher for a complete Cedros package compatible with your site. Keep the error text so they can identify a missing file or invalid package declaration. Renaming an ordinary archive to .zip does not make it an extension.
• Validation reports a package identity or integrity mismatch. Stop using that copy and ask the publisher to verify or replace it. Do not edit package files to work around the check.
• A required extension or service is missing. Resolve the named requirement with the site owner, then return to the failed step.
• Cedros asks you to re-upload the local package. Select the original ZIP again when you are ready to resume. Check the installed state first, since re-uploading can start installation and enablement again.
• The extension is installed but disabled. Address its enablement requirements rather than repeatedly uploading the same ZIP.
• The extension is enabled but its feature does not work. Check its own configuration and the specific added page or tool. Capture any error there as well as the installation result.

If you are unsure whether an action completed, refresh Extensions and inspect the version and state before retrying. Avoid repeatedly selecting the file while an action is still running.

Share useful details when asking for help

Provide the extension name, package ID and version, ZIP filename, publisher, exact error, and the step where it stopped. Include whether the extension now appears in the installed list and whether it is enabled. Describe the expected feature and what you observed instead.

Share package files only through the publisher's or support team's agreed channel. Leave credentials and customer information out of screenshots and error reports.

If the extension has already created site content, do not assume disabling or removing it will undo those changes. Review the affected items separately before changing or deleting them.