Help4 Builder Migration and Troubleshooting
Before the first click
Confirm what you are editing and where each kind of change belongs.
Read the page or template title first, select the exact element in the canvas or Navigator, then use the inspector tab that matches the job. This prevents a content change from becoming an accidental layout change.
Content
Change words, links, images, icons, data sources, shortcodes, and element-specific information.
Design
Change colors, typography, spacing, borders, radius, alignment, states, and desktop, tablet, or mobile values.
Advanced
Change labels, anchors, classes, attributes, visibility rules, motion, and other expert controls.
Page Settings
Use page-wide history, globals, publishing, template assignment, and recovery controls instead of editing one element.
Visual orientation
Match the screen before following the steps.
Open each image at full size. The numbered notes explain what the screen controls and what to confirm before changing customer content.
Screen 1
Current Studio workspace
See the element library, device controls, live page frame, inspector, performance guidance, and save state together.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 2
Builder Studio
Use the live page frame, element library, template library, inspector, responsive controls, performance guidance, and save state in one workspace.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 3
Updates
Confirm the installed version, free update status, manifest URLs, beta or stable channel behavior, and package checks.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 4
Security
Review SSL, headers, login hardening, XML-RPC controls, checkout safety, and production hardening settings.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Watch the real workflow
Watch the clicks before making the change.
Use the narrated walkthrough first, then follow the written steps and verification checks on this page.
Lesson 34
Migration, Import, Export, and Cutover
Move Builder layouts and settings through guarded exports, structural checks, media mapping, and a verified launch sequence.
Read the complete transcript
- Inventory Before Moving
Open the migration and cutover tools only after inventorying pages, templates, global styles, custom fields, menus, forms, media, redirects, SEO metadata, commerce data, users, and addon dependencies. Record the source and target versions. A migration is more than copying page HTML.
- Export a Guarded Bundle
Export the supported Builder bundle and keep its manifest and checksum with the recovery record. Do not place credentials, private customer records, payment secrets, or unrelated uploads in a portable design package. When a script will run through WP CLI eval-file, avoid first-statement assumptions and preserve every host and dry-run guard.
- Import Without Replacing by Accident
Choose style-only, merge, or explicit layout replacement according to the migration plan. Verify the import target and expected current hash before the first write. Preserve stable element identifiers, parent relationships, extension data, and non-pack global tokens unless replacement was approved.
- Validate Then Cut Over
Check block counts, unique identifiers, parent and slot graphs, media URLs, forms, menus, responsive layout, Studio parity, public pages, SEO output, and logs before changing traffic. After cutover, verify redirects, canonical host, sitemap, cache, SSL, checkout bypasses, and the exact rollback path while the recovery window is still open.
Lesson 8
Headers, Menus, and Mobile Navigation
Read the complete transcript
- Create a Header Template
Open Theme Builder and create or edit a header template. Reusable headers belong here so one controlled update can reach the assigned parts of the site.
- Insert the Menu Widget
In Studio, search the widget library for Menu. Insert the native component, then select the WordPress menu you want visitors to use.
- Configure Navigation
Set desktop orientation, dropdown behavior, submenu spacing, mobile breakpoint, and the compact menu trigger. Check that pointer and keyboard users can reach every submenu item.
- Assign and Test
Save the template conditions, then test a normal page on desktop and mobile. The mobile trigger should be visible, named, and able to open and close the complete menu.
Triage order
Preserve evidence before trying random fixes.
The fastest repair starts with a reproducible action and a known before/after state, not repeated edits on a damaged live page.
Editor crash
Do not keep deleting or adding blocks; reload only after recording the last safe state.
Missing styles
Verify Builder assets and addon module handles load on singular, archive, search, and 404 templates.
Media operations
Confirm WordPress temporary storage is writable before imports or large media changes.
Guided walkthrough
Make one verified change at a time.
Each step includes the action, why it belongs in this order, and the checkpoint to verify before moving forward.
-
Stop and record
Capture the page title, URL, Builder version, WordPress version, viewport, and exact click that caused the problem.
Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.
Done whenThe stop and record result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Check History
Load a verified recovery point as a draft when content or styling changed unexpectedly.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe check history result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Compare Studio and public
Check computed spacing, typography, media, menus, forms, and module assets in both contexts.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe compare studio and public result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Check source assets
Preserve uploaded-media URLs during migration and map old source URLs instead of substituting similar images.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe check source assets result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Check theme and cache layers
Confirm active parent/child theme assets, duplicate stylesheets, page cache, CDN cache, and query/cookie bypass behavior.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe check theme and cache layers result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Escalate with evidence
Send the screenshot, route, element label, browser console, fresh PHP log lines, and whether the issue reproduces on a clean draft.
Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.
Done whenThe escalate with evidence result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
How to know it worked
Verify the edit in Studio and on the real page.
A successful edit stays visible when the element is reselected, matches the intended responsive view, survives publish, and appears on the public URL without clipping or lost styling.
Studio preview
Reselect the element and confirm the saved value and visual result are still present.
Responsive preview
Check desktop, tablet, 390px, and 360px widths for overflow, squeezed controls, and inherited values.
Public page
Open the public route in a new tab after publishing and confirm content, interactions, assets, and spacing.
Recovery
If the result is wrong, stop editing and use History or a known-good revision instead of rebuilding the page.
Avoid the expensive mistakes
Stop when the page stops behaving predictably.
More edits do not repair a bad state. Preserve the evidence, return to a known revision, and reproduce the smallest failing action.
Changing several controls at once
Change one content, design, or responsive value, then confirm it in the preview. A small edit is easier to understand and recover.
Editing the wrong layer
Use Navigator and read the inspector heading. Deleting a parent section can remove every child even when the selected text or image looked harmless.
Checking only desktop
Review tablet, 390px, and 360px before publish. Width, gap, padding, type, alignment, controls, and menus can inherit differently.
Publishing before values persist
Reselect the element and reopen the responsive view. If the value disappears or another tab has a newer revision, reconcile it before publishing.
Continue learning
Use the next guide that matches the work in front of you.
The full tutorial hub remains available without repeating dozens of unrelated cards on this page.
Start here
Install and setup
Download the ZIP, activate Builder Suite, understand the blank-theme path, and run the first clean check.
First page
Build a page safely
Open Builder Pages, launch Studio, build structure first, check mobile, then publish or hand it to Help4.
Editor controls
Know which tab changes what
Use Content for information, Design for appearance and responsive values, and Advanced for identity, attributes, visibility, and motion.
Recovery
Edit without losing work
Replace media safely, recognize stale drafts, and restore a known-good page snapshot from Page Settings History.
Responsive
Control every viewport
Set spacing, widths, columns, alignment, and typography independently for desktop, tablet, and mobile.
Templates
Choose a starter
Pick a starter spec by page job: service, product, support, recent work, local SEO, launch, or checkout recovery.
Need help with this step?
Send Help4 the page, screenshot, or site goal.
Include the URL, what you are trying to build, what looks wrong, and whether this is a draft, staging site, or live customer page.