You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In woocommerce/woocommerce.php:648 the product-category global slug goes through i18n, which means that once I change the locale in my configuration, the old page slugs are still effective yet the paths generated afterwards are incorrect.
Perhaps there shouldn't be any i18n in the routing?
The text was updated successfully, but these errors were encountered:
I also experienced severe wonkyness with core slugs in combination with WPML. Solution was to force-translate other language to use core english slugs. Not sure if this applies entirely, but I'm definitely going to watch here.
For the DD release we have been working with the developers of WPML (ticket ref: #1579). The changes that we've pushed referenced in that ticket are done to ensure it all works fine. WPML is able to change the static slug (now moved to Permalink settings btw) that you can set for products, for different languages as done here: e159952 So this is issue will be resolved when DD rolls out our factory and WPML releases a new compatible WPML version.
In woocommerce/woocommerce.php:648 the
product-category
global slug goes through i18n, which means that once I change the locale in my configuration, the old page slugs are still effective yet the paths generated afterwards are incorrect.Perhaps there shouldn't be any i18n in the routing?
The text was updated successfully, but these errors were encountered: