How tweak settings persist
POM Tweaks keeps configuration after ordinary deactivation and reactivation. This is useful during maintenance, but it also means that reactivating the plugin is not the same as starting with an empty catalog.
Keep the settings scopes separate
The product has several independent configuration boundaries:
| Scope | Where it is managed | What it controls |
|---|---|---|
| Modern site settings | Settings → POM Tweaks | Modern modules and values for the current site |
| Modern network settings | Network Admin → Settings → POM Tweaks | Network administration appearance and network-wide update and theme controls |
| POM Tweaks license | Main site Settings → POM Tweaks → License on multisite | Access to the private update channel for the installation |
Network activation does not merge every site’s tweak configuration. Update and theme controls are explicit network policies and appear only in Network Admin on multisite, applying consistently to network, site and scheduled requests. The network administration appearance settings are also independent from individual site dashboards and login screens.
What Import / Export includes
The modern Import / Export tool transfers POM Framework settings and the managed CSS, JavaScript, and HTML assets that belong to that scope.
It does not include:
- historical configuration from the removed classic interface;
- settings from the other site or network scope;
- the shared POM Tweaks license;
- media, orders, posts, terms, or other content changed by a feature;
- generated output that is not one of the managed transfer assets.
A modern export is therefore a configuration transfer, not a complete WordPress backup.
Back up a configuration
Before an update, migration, or risky configuration change:
- Export the modern site settings from the current site.
- If network settings are in use, export them separately from Network Admin.
- If upgrading a classic installation, preserve its original backup until the replacement configuration has been verified.
- Take a suitable WordPress database and filesystem backup for persistent feature output.
- Record the licensed domain and status without copying the full key into ordinary support notes.
Use filenames and backup notes that identify the site, scope, and date. Do not assume that a network export represents a subsite.
Verify an import
- Import into the matching site or network scope.
- Reload the settings page and confirm the expected modern modules and values.
- Check managed custom CSS, JavaScript, or HTML where used.
- Confirm that unrelated site and network settings remain unchanged.
- Test one positive and one negative case for every imported feature.
- Recheck the license status independently.
If an imported switch is on but produces no output, inspect its dependencies and request conditions. If the goal is to undo behavior rather than transfer configuration, use the rollback guide.