What happens when a tweak is disabled
Disabling a modern module under Settings → POM Tweaks prevents that module’s runtime from loading on later requests. Its feature hooks, assets, callbacks, and queries therefore do not run while it remains off.
Disabled does not mean uninstalled
The active plugin still provides its shared settings, licensing, translations, update, and administration services. Requests to the POM Tweaks settings page must also build the catalog so an administrator can configure it.
Those shared costs are different from the cost of an individual disabled module. Do not use the settings screen as evidence of what a normal public page loads.
Completed work remains completed
Turning a switch off does not reverse earlier side effects. Depending on the feature, the site can retain:
- compressed originals or generated WebP files;
- renamed attachments and updated references;
- deleted revisions, metadata, comments, terms, posts, or scheduled events;
- generated PDF catalogs or other static output;
- saved WooCommerce order numbers and acceptance evidence;
- sent email and completed checkout actions.
Persistent output can continue to affect storage, records, or what another system serves even though the tweak itself no longer runs.
Confirm an off state
- Record the enabled behavior on a representative request.
- Disable only the target tweak and save.
- Clear only the cache layer that can retain that output.
- Repeat the same request with the same user and data.
- Confirm feature-specific scripts, styles, or output are absent where applicable.
- Check an unrelated page to ensure the test did not disturb other modules.
- Review stored files and records separately from runtime behavior.
If the feature appears to remain active, first rule out browser, page, object, and CDN caches. Then check for another module, theme customization, snippet, or plugin that owns the same behavior.