2 Translation issues - by WF-PMG - on WordPress WooCommerce support

This topic has 10 replies, 2 voices, and was last updated 4 years, 6 months ago ago by WF-PMG

  • Avatar: WF-PMG
    WF-PMG
    Participant
    June 3, 2021 at 08:25

    Hello,
    1) I can’t find the text to translate in the string translator of WPML for the promo slider I have used in our Header. Where can I find this?
    2) The same problem with the shopping cart (with Icon) in the main header. Where do I find this to translate? Right now it is staying in our main language (Dutch) for all three languages.

    Please, contact administrator
    for this information.
    9 Answers
    Avatar: Olga Barlow
    Olga Barlow
    Participant
    June 3, 2021 at 12:07

    Hello,

    1) We have created bottom slider using Static block instead of the Promo element because Promo element has some issues with the translation to other languages. So, translate Header promo slider static block to other languages.

    2) To translate strings that you added from theme options use admin strings translator
    https://gyazo.com/be67cf749356a35d314c32f393bd3477 Look for your strings and add them to string translator. Translate string using strings translator after that.

    Regards

    Avatar: WF-PMG
    WF-PMG
    Participant
    June 3, 2021 at 20:54

    Hello,
    Thank you for your quick reply.
    2) is solved, thank you.
    !) I am not sure what you mean. Should I create a new static block to insert in the header area, instead of using the prom slider? Perhaps you can show me a screen shot to point me in the right direction…

    Avatar: Olga Barlow
    Olga Barlow
    Participant
    June 4, 2021 at 12:33

    Hello,

    2) No. You need to add the header strings to the string translator. For example:
    a) You have the cart string https://prnt.sc/14044lx
    b) Click this link in the string translator (at the bottom of the page ) https://gyazo.com/be67cf749356a35d314c32f393bd3477
    c) Look for this string https://gyazo.com/f51bf545f3eb417969c1049871a14d06 and add this to string translator and translate this string after that.

    Regards

    Avatar: WF-PMG
    WF-PMG
    Participant
    June 4, 2021 at 18:37

    Hi,

    Sorry, a slight misunderstanding. I have solved the Cart issue, I am still stuck on the Promo Element. Where do I find these texts?

    Avatar: WF-PMG
    WF-PMG
    Participant
    June 4, 2021 at 18:42

    Actually, I have found the texts, and translated them but they are not displaying in their respective languages, as I think you suggested.
    Do you mean that I need to create a new static block and not use the Promo Slider in the header?

    Avatar: Olga Barlow
    Olga Barlow
    Participant
    June 7, 2021 at 10:17

    Hello,

    To translate the promo texts you need to translate the Header promo slider static block to other languages https://gyazo.com/fa7d9edc3f0252c67f05793a0ea32110

    Regards

    Avatar: WF-PMG
    WF-PMG
    Participant
    June 9, 2021 at 12:11

    I have translated the sliding texts in the string translator. I have also translated the header promo slider titles as you suggested in your screenshot. This has not changed the display in the other languages. Could you take a look and tell me what I am doing wrong?
    Regards

    Please contact administrator
    for this information.
    Avatar: Olga Barlow
    Olga Barlow
    Participant
    June 9, 2021 at 21:58

    Hello,

    String translator is not for the Static block editing.
    Go to Static Blocks and don’t use WPML editor to edit Pomo static block https://gyazo.com/687f2f2a1bb732a1f637127a472d288d but switch to the Header promo slider DE/Header promo slider EN and use Elementor to change the content https://gyazo.com/2b0f7b796a317f7b18ed0f12a7c7c09d
    Got it?

    I did it for you. Check.

    Regards

    Avatar: WF-PMG
    WF-PMG
    Participant
    June 10, 2021 at 08:36

    Thank you! Thank you! Thank you! That was super service!

  • Viewing 10 results - 1 through 10 (of 10 total)

The issue related to '‘2 Translation issues’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.