Get started with POM Tweaks
POM Tweaks provides optional WordPress and WooCommerce features that can be selected individually. This chapter helps a site owner understand the two settings interfaces, install the production package, connect the license, and prove one bounded change before using the larger catalog.
Choose the right article
| If you need to… | Read |
|---|---|
| Understand the product’s scope, module isolation, dependencies, and limits | What POM Tweaks does |
| Check WordPress, PHP, permissions, multisite, and optional integrations | Requirements and compatibility |
| Install the official package and verify the relevant administration entry | Install and activate POM Tweaks |
| Authorize the domain for private updates | Activate your POM Tweaks license |
| Locate sections, tabs, and network settings | Tour the POM Tweaks interface |
| Find the current location of a former classic feature | Classic and modern tweak interfaces |
| Prove one low-risk feature from on to off | Enable and test your first tweak |
| Prepare evidence, compatibility checks, and rollback for production | Enable tweaks safely on a production site |
| Update the plugin or prepare a safe support request | Updates, support, and safe maintenance |
Recommended path for a new installation
- Read What POM Tweaks does and list the exact outcomes you need.
- Confirm the platform and feature requirements.
- Install the production ZIP with no assumption that every tweak should be enabled.
- Connect the zero-cost subscription license and authorize the installation’s domain.
- Locate the relevant section under Settings → POM Tweaks and check its site or network scope.
- Select one reversible, presentation-only feature for the first test.
- Verify its positive case, negative case, saved state, and off state.
- Use the production change workflow before enabling a persistent, security-sensitive, SEO, media, email, or commerce feature.
The isolation boundary
Modern modules have an explicit runtime boundary: POM Tweaks loads a module’s runtime only while that module is enabled. A disabled modern module therefore registers none of that module’s hooks, assets, classes, or queries.
The plugin’s shared bootstrap, settings, licensing, translations, administration, and update integration still load while the plugin is active. The built-in classic components have been replaced or retired; their catalog points to the current feature guides.
This distinction matters when diagnosing performance or conflicts. “POM Tweaks is active” does not mean that every feature runs, and disabling one module does not disable another plugin or theme option with similar behavior.
Documentation map
After this chapter:
- Concepts explains settings, lifecycle, dependency, conflict, security, performance, and rollback boundaries.
- Modern tweaks documents each POM Framework module.
- Classic tweaks maps former feature names to current modules and retirement notices.
- Workflows combines features around complete editor and customer journeys.
- Developer reference covers supported lifecycle and extension contracts.
Enable only features with a named owner, a verified dependency set, and a rollback appropriate to what the feature can persist.