sorry @leap13 but i really think you should investigate the issue a bit more in depth (not mine in particular, but the compatibility between Premium Addons and Polylang in general).
i’ve just done a quick test using Elementor’s own Post widget:
1) i have a category in main language with a few posts – the category is translated in a second language, so are the attached posts
2) i’ve created a page in main language, added Elementor Post widget and targeted such category (Elementor calls it “Term” – typing the first 3 letters, it autosuggests the right category)
3) i translated the above page, edited the Elementor Post widget to change the “Term” and typing the first 3 letters it autosuggests the correct translated category, and the posts appearing are the ones in second language
so it seems that Elementor itself is perfectly compatible with Polylang, right “out of the box”. i don’t understand why, in the case of your Premium Addons, it should instead be a problem that Polylang should solve…
anyhow, too much time has passed and i don’t think i’ll have much success bringing your case up with Polylang support. i think i’m going to review usage of Premium Addons throughout the site instead and consider @atickettotakeoff approach, replacing the plugin if necessary.
unfortunately, until WordPress does not finally come with a solution in its core, translation plugins will have priority over extensions in multilanguage sites.
but thanks for your time, hope you will want to consider digging more into why Premium Addons is not compatible with Polylang (and i suspect other translation plugins).
-
This reply was modified 3 years, 9 months ago by
maxgx.