Upgrade an existing v8 map
Version 9 changes the editor and data-authoring workflow. Review a migration before replacing a working publication.
Back up and preserve the baseline
Section titled “Back up and preserve the baseline”Back up WordPress data, uploaded SVGs, and the installed plugin packages. Keep the original v8 publication available while testing a v9 draft.
Opening the new interface and successfully viewing a map is not the same as migrating and publishing that map. Read the migration notice and version information before editing.
Review the migration draft
Section titled “Review the migration draft”Create/open the offered v9 migration draft for the existing App. It should provide an editable configuration while preserving the existing v8 publication. The retained Old editor entry is the path for working with the v8 baseline where offered.
Inspect Layout on every responsive profile. Legacy header/sidebar/footer settings become a tree of containers and components. Review widths, height, visibility, padding, and the Mobile Toolbar rather than assuming every old CSS/layout combination transfers unchanged.
Where settings moved
Section titled “Where settings moved”- Database records and schema fields: global Database → Collections.
- Data selection: Database → Queries, then Page → Objects/Regions bindings.
- Region status/choropleth presentation: Region → Settings → Data rules.
- Marker image mappings: Marker → Settings.
- Filter controls: Filters → Settings → Edit form.
- Templates, CSS, events: the owning component’s Code picker.
- Draft/publication actions: the clock Versions panel.
Audit customization
Section titled “Audit customization”Check custom selectors against the new Layout and component rendering boundaries. Review template field context, JavaScript event signatures, external integrations, and optimized script loading.
Test the actual frontend. The v9 Details action has a known instance-selection limitation, so do not use a successful v8 Details setup as proof that the new action path is ready. Preserve the baseline and use verified alternatives while reviewing it.
Publish deliberately
Section titled “Publish deliberately”Publish the migration draft only after checking the intended data, interactions, responsive layouts, and WordPress embedding. Check both logged-in and logged-out visitors.
Rollback of an App publication restores configuration, not shared records or Query definitions. Keep independent backups for those resources.