Updates, support, and safe maintenance

POM Tweaks updates use the private POM release channel. A valid POM Tweaks subscription, stored license, authorized domain, and compatible WordPress/PHP environment are required before WordPress can receive the gated package.

Before an update

1. Read the release notes and identify changes to every tweak enabled on the site.
2. Record the installed POM Tweaks version.
3. Confirm Settings → POM Tweaks → License shows a valid license for the current site or network.
4. Create a current database-and-files backup.
5. Export the relevant modern POM Framework settings.
6. When upgrading an older classic installation, retain its complete backup because the modern export does not include historical configuration.
7. Capture a positive and negative baseline for each affected tweak.
8. Schedule persistent, security-sensitive, email, SEO, media, or commerce changes for a suitable maintenance window.

On multisite, run the update review from the network context and identify which sites use the affected features. A site-level success does not approve every site in the network.

How private update discovery works

The common POM updater can advertise POM Tweaks updates from the main or network update screen even when the plugin is inactive. When that shared updater is unavailable, the active plugin boots its local signed updater as a compatibility fallback.

Both routes use the network license on multisite. The local fallback requires POM Tweaks to be network-active or active on the main site. No update metadata is exposed without a stored valid license.

The update client verifies the integrity of the downloaded release package. Use the normal Dashboard → Updates or Network Admin → Dashboard → Updates flow; do not replace the plugin with an unverified source archive.

Verify an update

After WordPress reports success:

1. Confirm Plugins shows the expected POM Tweaks version.
2. Open Settings → POM Tweaks and confirm the modern sections load.
3. On multisite, open Network Admin → Settings → POM Tweaks and check any network policies in use.
4. Reopen each affected setting and confirm the intended value persisted.
5. Repeat the recorded positive and negative tests.
6. Test every affected role and site scope.
7. Complete the relevant public URL, email, media, or WooCommerce journey.
8. Clear only caches that contain changed output.

Do not assume that a successful plugin-file replacement proves an enabled tweak still behaves correctly. Updates can change hook registration, settings fields, dependency checks, generated output, or integration behavior.

Routine maintenance

Review POM Tweaks when:

• WordPress, PHP, the active theme, WooCommerce, Bookings, Polylang Pro, or another dependency changes;
• a feature changes its settings location or configuration options;
• administrators add custom snippets that target the same hooks;
• the domain or multisite mapping changes;
• enabled tweaks are no longer owned or understood;
• imports, bulk tools, media processing, or commerce rules have accumulated operational data.

Keep an inventory that identifies the exact interface and scope for each enabled tweak. Remove unused features deliberately and verify their off state; review overlapping theme and plugin options that produce the same result.

Prepare a useful support request

Provide:

• POM Tweaks, WordPress, and PHP versions;
• single-site or multisite topology and the affected site;
• the exact section, tab, and module;
• relevant dependency versions;
• affected URL, screen, role, language, product, or order state;
• steps to reproduce;
• expected and actual results;
• whether the result changes after disabling only that tweak;
• the last relevant configuration or software change;
• sanitized screenshots, response details, or error text.

Never provide:

• the full license key;
• WordPress, hosting, database, payment, email, or POM account credentials;
• authentication cookies or nonces;
• customer personal data;
• unrestricted exports or raw logs containing private information.

Controlled recovery

If an update causes a regression:

1. Disable the affected tweak when the settings page remains usable.
2. Verify whether the problem stops.
3. Restore the previously approved plugin package only through the controlled deployment process.
4. Restore database or files when the feature completed persistent changes.
5. Reapply only the known-good settings.
6. Repeat the baseline test before reopening the affected workflow.

Deactivating POM Tweaks stops its future hooks but does not erase saved modern or classic settings and does not reverse completed media, cleanup, generation, or commerce actions.