Hi @dirkd ,
AFAIK, Polylang Pro hasn’t supported Slim SEO yet. Would you mind asking them for support and a workaround? I’m happy to collaborate to resolve this issue.
Thread Starter
dirkd
(@dirkd)
Hi, thank you for replying. OK, I will try to contact their support and see where this is going …
Thread Starter
dirkd
(@dirkd)
Hi @rilwis , I received a reply from Polylang with the solution.
It seems the ‘Custom fields‘ checkbox under the Polylang settings in Languages > Settings > Synchronization has to be unchecked because the Meta description is stored as a custom field. In my case it always overwrote the descriptions for the other languages with the last one that I was editing.
So, the issue is solved!
They also mentioned that you – as the author of Slim SEO – can check their doc for a finer control of the multilingual behavior of the custom fields: https://polylang.pro/doc/the-wpml-config-xml-file/
Configuring this file would help you to control the behavior of the custom fields as well as multilingual options in both WPML and Polylang/Polylang Pro.
Thanks!
-
This reply was modified 3 years, 2 months ago by
dirkd.
Hi @dirkd ,
Thanks for your feedback. It’s very helpful.
In this case, I think the settings for the custom fields should be “translate”? I see Polylang provides 3 options:
- “ignore”: no action from Polylang
- “translate”: the custom field is copied from the source post but may be modified
- “copy”: the custom field is copied from the source post and synchronized accross translations
I guess, by default, if you check the checkbox for synchronization, it’s the “copy” action. So, to make it translatable, the value should be “translate”?
Thread Starter
dirkd
(@dirkd)
Good morning @rilwis ,
Yes, that’s exactly my thought too. ‘Translate’ makes the most sense here.
When I copy an article to another language it takes over the Meta description but this time I can edit it correctly in the other languages.