-
Not sure if this is a GeneratePress or a WPML issue.
I have made some elements in GeneratePress Elements and liked them to specific locations. For example, I made aan Element to show meta information on all posts within the category “Blog” which three exceptions. See screenshot.
I was assuming that if we translated the posts and the GeneratePress element, let’s say in Dutch, th translated element would automatically show up on all Dutch versions of the elements in the Display Rule. But it doesn’t
It seems we have to set display rules separatly for all the translations of the GeneratePress Element items.
Is this normal behaviour? It does not look like it to me.
-
Hi there,
the Element is just a post type, so it should have its own WPML settings. Can you check those are set correctly. ?
-
Thanks David, The only settings I can find look ok to me. I’ll pass this over to WPML also.
-
I got this answer to the same question from WPML:
“It seems an expected behavior of how Generatepress handles the display rules.”
-
To be honest I am not that familiar with WPML or how it handles the translated posts.
Its sounds like they are treated as unique posts, and therefore would require the exact post to be selected in the display rules.Would there be a different method of setting the Exclusions ? Perhaps using a taxonomy term ?
-
Thanks for the honesty. Completely understand. I run in to stuff I don’t know regularly 🙂
There isn’t really a problem with the translations of the posts or the Element. In this particular example it is just the exclusion rules which do seem to pass over correctly to the translated version of the Element.
It is, however, possible to set them differently for every language, so having the Dutch version of the Element be excluded on selected Dutch items. It’s not the end of the world to set the Exclusion rules separately per language.
When creating a translation of an element the rules are caried to the translated version also but they are just a copy of the original rules so connecting to the English posts. It would be nice if they would automatically transform to the correct language version of the item.
Also FYI: While trying out changing the Exlusion rules I missed an easy way to go to the front end (or backend) of the posts in the Rules. I had to search for the post on the WordPress “Posts” backend to find it. A link to the pages in the Elements rules would be so handy.
-
Hi there,
Can you check this WPML’s support ticket, is this the same issue?
https://wpml.org/forums/topic/generatepress-elements-not-appearing-in-the-frontend/Let me know 🙂
-
Thanks Ying!
It’s not clear to me what the issue was in the ticket you forwarded. I did find the setting and I changed it. I don’t really know what changed after changing the setting but it did not solve this issue.
-
So where we at 🙂
Is it confirmed that to use specific posts or pages in the display rules they must be specific to each language ? -
The exceptions only aparently. I mean, I have tested it only on our Blog section with an element with display rules to show on all posts within the “Blog” category, except some specified post. See the image I shared.
The element will show on all post on all languages but the exceptions need to be set per language.
That’s where I’m at. I haven’t tried it with other rules… yet 😉
-
Yeah, its unavoidable as the display rules are post specific and each language version is its own post.
-
Language versions are linked as being a translation of a post in the base language or one of the other languages so in theory it should be possible to create this feature. But, opviously it is all up to you and probably not as simple as described here 😉
Thanks again for your support!
-
It sounds kinda easy 🙂 but the display rules logic behind elements is crazy complicated.
So I am not sure its fixable… but ill make a note 🙂 -
Yeah, I can image scenarios in which it is needed to set rules differently per language also…
Having great fun with blocks and elements btw. Really impressed with the features and how wel it works
-
Thanks for the great feedback, its really good to hear that!
- You must be logged in to reply to this topic.