Enable and test your first tweak

This walkthrough proves that one selected tweak can be enabled, saved, observed, and disabled without activating unrelated features. Use staging or a low-risk site and choose a presentation-only tweak whose result is easy to see.

Do not use media renaming, image optimization, cleanup tools, sequential order numbers, checkout rules, payment changes, or another persistent or transactional feature for this first exercise.

Choose one observable result

Write down:

• the exact feature name;
• its section and tab under Settings → POM Tweaks, or the network equivalent;
• the URL or administration screen it affects;
• the user role and conditions required to see it;
• the current result;
• the expected result after enabling it.

If the feature depends on WooCommerce, Bookings, Polylang Pro, a theme hook, or another plugin, confirm that dependency before continuing.

Enable a modern module

For a feature shown on the modern page:

1. Open Settings → POM Tweaks.
2. Select the section and tab named in the feature guide.
3. Read every field before using the module’s enable control.
4. Configure only the values needed for the chosen result.
5. Save the settings.
6. Reopen the same section and confirm that the module remains enabled and its values persisted.

After saving, POM Tweaks reads the enabled state on later requests and loads that module’s runtime only while it remains enabled.

Verify the positive case

Open a fresh browser context appropriate to the feature:

• use a private window for public frontend output;
• use the intended non-administrator role for permission-sensitive changes;
• use a real cart and checkout session for a commerce presentation feature;
• use the exact post type, taxonomy, language, or screen selected in the settings.

Perform the action that should trigger the tweak and record the result. Refreshing the settings page alone is not verification.

Verify a negative case

Change one relevant condition and prove that the tweak does not apply where it should not. Examples include another role, another post type, a URL outside the selected scope, a product without the configured rule, or a request in a different site of the network.

This negative test catches over-broad settings that a successful positive example cannot reveal.

Prove the off state

1. Return to the same interface.
2. Disable only the selected tweak.
3. Save and reopen the setting.
4. Repeat the positive-case request in a fresh browser context.
5. Confirm that the tweak’s runtime behavior has stopped.

Disabling the module prevents its runtime from loading on subsequent requests.

If the test created or changed persistent data, switching the feature off may not reverse that completed action. Restore the prepared snapshot or follow the feature-specific recovery guide.

Completion criteria

The first activation is complete when:

• exactly one tweak was changed;
• its saved state survived a page reload;
• the expected case changed;
• an out-of-scope case did not change;
• disabling it stopped future runtime behavior;
• any persistent test data was removed or retained intentionally.

Use Enable tweaks safely on a production site before applying the real change.