Help4 Builder Updates and WordPress 7 Readiness
Upgrade safety
Do not turn customer sites into the test track.
Release candidates are for testing. Help4 uses md to find issues before live sites get core upgrades.
Package channel
Use /help4-builder-suite/latest.zip for the current public Builder Suite release and /manifest.json for update checks.
Live track
Live Help4 WordPress stays on production WordPress with the current non-beta plugin package.
md beta track
md helps test Builder Suite, Help4 Blank, templates, redirects, forms, commerce, SEO, and admin screens against WordPress 7 RC behavior.
Before WordPress 7
Check plugin updates, theme output, Builder Studio, forms, commerce, redirects, cache purge, rollback, and mobile rendering.
When an update fails
Restore from backup, disable the failing module, keep package redirects intact, and record the exact screen and error.
When to ask Help4
If the site makes money or handles customers, let Help4 run the upgrade and QA instead of guessing in production.
Tutorial pages
Pick the next thing you need to do.
These are evergreen WordPress pages for Help4 Builder Suite users. They are written for site owners who want plain steps, not developer homework.
Install and setup
Download, upload, activate, run the wizard, and install Help4 Blank.
Build the first page
Open Builder Pages, launch Builder Studio, create layout, and publish safely.
Templates and icons
Pick starter templates, apply a theme pack, and use default icon assets.
Fields and dynamic content
Create field groups, repeaters, galleries, relationships, and dynamic output.
Commerce and payments
Set up native catalog, variations, subscriptions, and payment routing.
Sliders and forms
Build motion sections and lead forms without loading every asset everywhere.
SEO, security, speed
Turn on metadata, schema, redirects, SSL, headers, cache, and images.
Updates and WordPress 7
Understand live stable, md beta, package updates, and core upgrade checks.