In most cases, Permalink Manager seamlessly supports both WPML and Polylang. You can use it to easily translate the permalink formats or define custom permastructure settings per language.
One of the most widely used features of this plugin is its ability to translate permalinks without any coding skills. You can find more detailed instructions in a separate article.
Some of Permalink Manager's built-in functions, however, might not function as intended when it is used in conjunction with other plugins or custom solutions.
WPML
Translating Custom Permalinks with WPML
Permalink Manager allows you to customize permalinks per language with WPML. Both Classic and Advanced Translation Editor use separate fields to manage translated permalinks.
This field is already built into the Classic Editor, so there is nothing extra you need to do:
If you are working with the Advanced Translation Editor (ATE) and the field is missing, you can display it for new translations by adding a below hook. To do so, simply paste it into the functions.php file found in your child theme directory:
add_filter( 'permalink_manager_ate_uri_editor', '__return_true' );WPML/Polylang language mismatch
You have the option to disable some integration functionalities in the plugin settings to avoid any potential conflicts with other plugins.
If you are having problems with the way the language of custom permalinks is recognized, consider deactivating the "WPML/Polylang language mismatch" and "WPML compatibility functions" options in the plugin settings.
TranslatePress
Unfortunately, Permalink Manager is not compatible with TranslatePress.
Unlike WPML or Polylang, which save translations as separate posts, TranslatePress adopts a different method to store translated content. As a result, Permalink Manager cannot process permalinks for translated content items.
Furthermore, if the slug is translated directly using TranslatePress, the algorithm that detects custom permalinks will be unable to identify the URI.