[Support request] Use GP element Layout on all translated (WPML) pages

Home Forums Support Use GP element Layout on all translated (WPML) pages

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1231420
    p

    We have some Element display rules that sometimes include a list of pages and sometimes exclude a list of pages.
    We have 10 different languages and translated some pages using WPML. We also duplicated the Elements using WPML.
    However. the translated pages do not have any of the Element display “styling”.
    Only when we manually add a translated page we seem to get to make this work..
    However with 1o languages this would mean sometimes adding 130 pages to include, sometimes 80 pages to exclude and so on..
    This is not workable.

    We just need the Element to (automatically) be used on all translated pages. .
    Just like the Front-page which is the only pages that seems to work in translation mode with an Element.

    #1231992
    Tom
    Lead Developer
    Lead Developer

    Hi there,

    So you’ve created the Element in multiple languages.

    Is the Element content translated in each language when you view the site?

    When you say the styling isn’t working, do you mean things like the background color, text color etc..?

    Let me know 🙂

    #1232169
    p

    Hi Tom,

    First we created many elements
    Then we used WPML to duplicate these elements, because there is no need to adjust them for our translated pages.

    But then when we select a translated page.. the layout (element) is not used, probably because we (as explained) did not add new display rules for the translated page.
    example: default language layout: https://www.hiartiyl.com/about/
    German translated page: https://www.hiartiyl.com/de/ueber/
    different layout, 1) because an Element exclusion rule (search) is now not “activated” on this translated page (because this German page was not manually added).
    2) because an other Element was not activated that would include the layout for this design.

    A solution that we would manually add 10 language translated pages for each include/exclude list of pages.. is not the desired way to move forward.

    There should be more clever way to manage this..

    #1232853
    Tom
    Lead Developer
    Lead Developer

    Just to get my head around this.. would the ideal solution be to apply that one Element to all languages?

    #1233004
    p

    Yes.. Of course.
    We have
    1: very simple element to only be used/display rules (Content (no sidebars) + Full Width (no padding)) on 3 pages
    2: we also have another simple element to only be used/display rules (Content (no sidebars) + Contained (no padding)) to be used on all pages except 10 pages (all our member pages).
    3: we also have a Hook to only be used on certain pages.

    And now that all these pages are translated.. of course we want the layout to be the same on translated pages and on the default language page.

    but somehow this seems very complicated..

    and we are running in circles, because we follow WPML generatepress element translation guidelines, contacted them (https://wpml.org/forums/topic/use-generatepress-element-hook-on-all-translated-pages/#post-5877639)
    but it’s just not working..

    very frustrating because we like the speeds of your theme (And had used many other themes before). But now we get stuck.

    #1233350
    Tom
    Lead Developer
    Lead Developer

    It’s been a while since I played with WPML, sorry for my rusty-ness.

    Looked through their forum a bit and found this one: https://wpml.org/forums/topic/how-to-display-the-same-posts-for-all-languages/

    It says this:

    Go to WPML->Translation Management -> Multilingual Content Setup-> Post Types Translation -> and set Posts/Pages (depends which one you need) to
    “Translatable – use translation if available or fallback to default language”

    In your case, you would choose the “Elements” post type. If you choose the “use translations if available or fallback to default language”, you should be able to remove those “translated” elements, and all languages should use the one single Element.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.