Updating SETN Schema Builder

Keep SETN current to receive compatibility improvements, bug fixes, security updates, and new features included with your edition.

Before significant updates, maintain a current backup and consider testing on staging for business-critical websites.

Automatic Updates

Licensed update delivery verifies entitlement before WordPress receives an approved package. Keep the license active and allow outbound HTTPS connections to the SETN services required for update checks.

If an update is expected but missing, refresh license status and WordPress update checks.

Release Channels

SETN may use channels such as Stable, Beta, or Release Candidate.

Use Stable for most production sites. Beta and Release Candidate builds are intended for testing, validation, or customers who explicitly opt into pre-release software.

Do not assume a pre-release version will automatically be offered to a site following the Stable channel.

Beta Releases

Beta releases may contain new capabilities still undergoing broader validation.

Use them on staging or selected test sites first. Report reproducible issues with environment details and avoid deploying beta software to critical production sites unless you understand the risks.

Version Changelog

Review the changelog before updating when a release includes major feature, compatibility, or behavior changes.

For troubleshooting, always record both the currently installed version and the version you are attempting to install.

Upgrading Between Editions

When moving from Free to Single, Professional, Agency, or another licensed edition, follow the approved replacement process and verify that existing settings remain intact.

After upgrading, activate the new license, review newly available features, and re-check Schema Health and compatibility status.