如何导出兼容DNN Evoq 8.2的DNN Community站点

Got it, let's walk through how to get your Evoq 8.2 site exported in a way that works seamlessly with DNN Community 8.2—since you don't have access to the customer's Evoq instance, we'll focus on cleaning up your dev environment's export to strip out any Evoq-specific bits. Here's your step-by-step playbook, tailored to your simple 3-page, 3-module site:

Prerequisite First: Validate Your Site Components #

Before exporting, make sure your site doesn't rely on Evoq-exclusive features:

• Check modules: Confirm your 3 modules are either DNN Community 8.2's default modules (like HTML, Links, Events) or custom modules that don't use Evoq-only APIs (e.g., no Evoq Form Builder or Content Analytics). If you used any Evoq-specific modules, replace them with Community-compatible alternatives first.
• Check skins/containers: If you used an Evoq-specific skin, swap it for a default Community 8.2 skin (like DarkKnight or Apex) to avoid missing skin objects.

Step 1: Export the Site from Your Evoq 8.2 Dev Instance #

Since you built the site in your own Evoq environment, export it from there:

• Log into your Evoq site using a Host-level account (critical for full export access).
• Navigate to Host > Import/Export (in DNN 8.2, this is under the Host menu's core admin tools).
• In the export wizard:
  • Select your target site (if you have multiple sites on your dev instance).
  • Check boxes for Site Structure (page hierarchy, module placement) and Content (module content, page settings). Uncheck any options for Evoq-specific components (like Evoq analytics or premium modules).
  • Set the compatibility target to DNN 8.2 (look for a "Compatible With" dropdown or field to specify this).
  • Generate the export package (it'll be a .zip file).

Step 2: Clean the Export Package to Remove Evoq Bloat #

Open the exported .zip file to strip out anything that won't work in Community:

• Remove Evoq-specific modules: Navigate to the Modules folder in the zip. Delete any folders tied to Evoq premium modules (e.g., DNN.Evoq.Forms—you won't have these if you only used default modules, but double-check).
• Edit the manifest file: Open manifest.xml in a text editor:
  • Scan the <dependencies> section and delete any entries that reference Evoq-specific libraries (e.g., DNN.Evoq.Core).
  • Verify the <supportedVersions> tag includes 8.2.0 as a valid version (add it if missing).
• Swap skins (if needed): If you used an Evoq skin, replace the skin files in the zip's Skins folder with a Community 8.2 default skin, and update the manifest to reference the new skin.

Step 3: Test the Package on a Clean DNN Community 8.2 Instance #

Don't skip this—you want to catch issues before sending to the customer:

• Set up a fresh DNN Community 8.2 instance (match the customer's intended environment as closely as possible).
• Log in as Host, go to Host > Import/Export, and upload your cleaned zip package.
• After import, verify all 3 pages load correctly, modules display their content, and there are no error messages in the event log (check Host > Event Viewer for issues).

Step 4: Deliver to the Customer with Deployment Instructions #

Provide the cleaned zip and clear steps for the customer:

1. Install a fresh copy of DNN Community 8.2 (avoid newer versions to prevent compatibility gaps).
2. Log in using the Host account created during installation.
3. Navigate to Host > Import/Export, upload the zip package, and follow the import wizard.
4. After import, check site functionality and adjust permissions as needed (e.g., assign admin roles to their team).

内容的提问来源于stack exchange，提问作者kumiau