Meta

Status:

untranslated

Priority of the original:

normal

It is 100% compatible with Polylang. WPML is a bit wonky but might work depending on your setup. In order for this to work properly you should set the post types and all connected taxonomies to be translatable. The filtered urls will still work even if you don't set the post type to be translatable but when switching language Polylang still think it should add the new language to the URL which means it'll throw a 404 error. This is to be expected and NOT due to this plugin. If you experience 404 errors make sure you flush your rewrite rules by going to settings &gt; permalinks in the admin dashboard.

Original untranslated

It is 100% compatible with Polylang. WPML is a bit wonky but might work depending on your setup. In order for this to work properly you should set the post types and all connected taxonomies to be translatable. The filtered urls will still work even if you don't set the post type to be translatable but when switching language Polylang still think it should add the new language to the URL which means it'll throw a 404 error. This is to be expected and NOT due to this plugin. If you experience 404 errors make sure you flush your rewrite rules by going to settings &gt; permalinks in the admin dashboard.It is 100% compatible with Polylang. WPML is a bit wonky but might work depending on your setup. In order for this to work properly you should set the post types and all connected taxonomies to be translatable. The filtered urls will still work even if you don't set the post type to be translatable but when switching language Polylang still think it should add the new language to the URL which means it'll throw a 404 error. This is to be expected and NOT due to this plugin. If you experience 404 errors make sure you flush your rewrite rules by going to settings &gt; permalinks in the admin dashboard.

Meta

Status:

untranslated

Priority of the original:

normal

<strong>Since v 2.2 this has been fixed. Make sure you keep BTF updated</strong>
In order for the rewrite rules to work with a taxonomy that has a rewrite slug you also have to add the same slug to the <code>query_var</code> parameter of register_taxonomy. It wont have any visible impact for you but it's what's needed for the filtered urls to work!

Original untranslated

<strong>Since v 2.2 this has been fixed. Make sure you keep BTF updated</strong>↵
In order for the rewrite rules to work with a taxonomy that has a rewrite slug you also have to add the same slug to the <code>query_var</code> parameter of register_taxonomy. It wont have any visible impact for you but it's what's needed for the filtered urls to work!<strong>Since v 2.2 this has been fixed. Make sure you keep BTF updated</strong>
In order for the rewrite rules to work with a taxonomy that has a rewrite slug you also have to add the same slug to the <code>query_var</code> parameter of register_taxonomy. It wont have any visible impact for you but it's what's needed for the filtered urls to work!

Help

Validating Translations

After a contributor suggests a string, the string gets a status of “suggested”. In order to transform them into “approved” strings (which will be used in WordPress), a Translation Editor needs to accept (or reject) those suggestions.
Please give editors a reasonable time to validate suggestions — We are all volunteers.

Translation Status

◼︎Current: Indicates an approved string.

◼︎Waiting: Indicates a string that was suggested, but not yet approved by a Translation Editor.

◼︎Fuzzy: Indicates a “fuzzy” string. Those translations need to be reviewed for accuracy and edited or approved.

◼︎Old: Indicates a string that was obsoleted by a newer, approved translation.

◼︎Warning: Indicates validation warnings. These translations either need to be corrected or their warnings explicitly discarded by a Translation Editor.