Polylang Pro/Polylang for WooCommerce bugs
Hello @Richard and @arminunruh,
as @doorofperception I also have problems with polylang.
This is frustrating because it is the Plugin you recommend and I also really need a multi-language site.
After @Richard verified that I would need to purchase the Polylang Business Pack in order for it to work with WooCommerce I did that.
However so far the paid version of the plugin does not seem to work as intended with Laytheme.
For example there is a duplicate content option, for the different translations. But with Laytheme it actually doesn't duplicate anything but an empty page shows up.
I'm also not sure if the different slug options offered by Polylang Pro work either (translations sharing slugs for example).
Please let me know how to get Polylang to work properly.
Have sent you a message via 'Chats'. ✨
Reference to the Last "polylang" thread : http://laythemeforum.com:4567/topic/6851/multilanguage-shop/4
doorofperception last edited by
Agreed. I also find it especially frustrating because Polylang is mentioned in the documentation as the plugin of choice. I just switched from WPML because I thought that would finally fix it.
In my opinion, Laytheme should not make the claim of supporting multilanguage (I love Lay, but this gives me trouble for years).
@Bella thank you for sharing the problem regarding the duplication of content. I'm glad I haven't bought the Pro version yet. If this doesn't work and every translated page starts empty, this plugin is almost useless I would say.
Because a gridder page can be quite complex and to rebuild it again every time is impossible.
Good Luck to us. Please share your findings.
Before you post
Use the Search Feature. Maybe there is already a solution to your issue.
1. Update Lay Theme and all Lay Theme Addons
2. Disable all Plugins
3. Go to Lay Options → Custom CSS & HTML, click "Turn Off All Custom Code ", click "Save Changes"
4. Now see if your problem solved itself
5. Go here, see if your problem is listed here:
When you post:
1. Post a link to where the problem is
2. If the problem is difficult to explain, post screenshots / link to a video to explain it