Why modern modules are isolated

The modern POM Tweaks catalog uses enablement as a runtime boundary. On each request, the plugin reads the effective modern settings and loads a module’s runtime only when that module is explicitly enabled.

What isolation guarantees

For a disabled modern module:

• its runtime classes are not introduced;
• its WordPress and WooCommerce hooks are not registered;
• its feature scripts and styles are not enqueued;
• its feature queries and request callbacks do not run.

Enabling one modern module does not silently enable another. This makes it possible to use a small part of the catalog without paying the runtime cost of every installed feature.

What still loads

POM Tweaks remains an active WordPress plugin. Its shared bootstrap, administration integration, settings discovery, translations, licensing, and update integration can still participate where relevant.

The accurate boundary is therefore:

A disabled modern module performs no runtime work belonging to that module.

It is not accurate to say that disabling one module removes the whole plugin from memory or eliminates every instruction associated with POM Tweaks.

Isolation does not reverse earlier outcomes

Module isolation controls future requests. It does not remove an image variant, restore a renamed attachment, recover deleted records, withdraw an email, renumber an order, or delete a generated catalog that already exists.

This distinction is especially important for:

• media optimization and renaming;
• cleanup and database maintenance;
• generated files;
• WooCommerce order and checkout records;
• messages or email already sent.

Use Plan and perform a rollback before enabling a feature that can persist changes.

Verify the boundary from the outside

1. Choose one modern module and record its current state.
2. Disable it under Settings → POM Tweaks and save.
3. Open the exact frontend or administration context where it would normally act.
4. Confirm the feature output and feature-specific assets are absent.
5. Enable only that module and repeat the same request.
6. Disable it again and confirm future behavior stops.
7. Inspect any files or records previously produced separately; their presence does not mean the disabled runtime still runs.

For a fair cost comparison, continue to What happens when a tweak is disabled.