Refresh routes after configuration changes

WordPress rewrite rules decide whether a prefixed request reaches POM Translate. The plugin registers rules for the root of every locale that uses a prefix and for paths below that root.

When rules are refreshed automatically

POM Translate flushes WordPress rewrite rules:

• when the plugin is activated;
• when Settings → POM Translate → Languages setup → Base setup is saved.

Changing an individual localized post or term slug does not require a rewrite rule for that one slug. POM Translate resolves those stored values dynamically after the prefixed request reaches its route handler.

Refresh manually only when needed

Use the standard WordPress permalink screen when prefixed URLs still return 404 after:

• moving the site or changing its home path;
• changing WordPress permalink structure;
• enabling or altering rewrite-capable plugins or themes;
• restoring a database without equivalent rewrite state;
• changing server rewrite configuration.

To refresh:

1. Open Settings → Permalinks.
2. Record the selected structure.
3. Select Save Changes without inventing a different structure.
4. Retest the exact prefixed URL.

Do not repeatedly flush rewrite rules on normal page views. It is an administrative repair operation, not a cache-clearing technique.

Separate rewrite failures from slug failures

A rewrite problem commonly affects many routes under the same language prefix. A slug problem is usually limited to one object, hierarchy, or localized segment.

After refreshing rules, verify:

1. the locale root;
2. one simple page;
3. one nested page or term;
4. an archive;
5. the previously failing route.

If the locale root works but one translated path does not, continue with Troubleshoot translated URLs instead of flushing again.