Skip to content

Theme migration sandbox (LocalWP, GeneratePress, Kadence)

Published on October 11, 2025

Last updated on June 8, 2026

This session extended the theme migration experiment into deeper troubleshooting and architectural analysis, moving beyond basic setup to explore real‑world issues that arise during restoration, CPT registration, and parent–child theme alignment. The primary objective remains to establish a fully functional local clone of the live site capable of supporting modern parent themes while retaining all structural logic, ACF relationships, and narrative hierarchy.

Actions completed

  • Installed and configured LocalWP as a stable development sandbox, and tested UpdraftPlus full‑site restores (database + files).
  • Experimented with both GeneratePress and Kadence as possible long‑term parent themes for migration.
  • Discovered that GeneratePress’s minimalism offers clean structure but requires manual re‑creation of many layout and color settings; Kadence provides visual flexibility but introduced theme JSON fragility (e.g., accidental deletion of global color variables).
  • Investigated CPT rendering issues (“page not found” after registration) and resolved them via permalink flushing, confirming CPTs were registered correctly.
  • Explored ACF Pro activation behavior on local environments and confirmed that while license reactivation is allowed for local testing, production keys should remain restricted to live and staging domains.
  • Identified the container width control as a critical layout setting (700–2000px range) and verified that default responsive behavior is preserved across screen sizes.
  • Recognized that XML import alone cannot restore relationships, menus, or ACF data — confirming that future migrations require a hybrid restoration strategy (importing only relevant database tables such as posts, postmeta, and taxonomy relationships).
  • Documented that a full DB restore re‑establishes all logic but also risks carrying theme cruft and script errors, underscoring the need for a controlled re‑architecture phase.

Next steps

  • Outline a step‑by‑step hybrid migration blueprint, detailing which database tables to import and which to omit to preserve CPT data without reintroducing theme dependencies.
  • Test child theme creation methods under both GeneratePress and Kadence to ensure long‑term flexibility if a switch is made.
  • Maintain Author as the current active framework until a functional prototype theme can replicate its layout and ACF‑driven relationships in the new environment.
  • Rebuild lost global styles and colors within Kadence manually, and document their relationships to CPT templates and navigation components.
  • Continue using LocalWP for controlled testing and only move to live site adaptation after all structural, visual, and performance issues are stabilized.

This phase evolved from simple cloning into a deep diagnostic of WordPress migration realities — clarifying what can and can’t be cleanly transferred between frameworks. The process now serves as both a sandbox and a roadmap toward a future site architecture prioritizing stability, responsiveness, and maintainability without compromising creative continuity.