Partial translation of woocommerce plugin into Spanish

This topic has 6 replies, 3 voices, and was last updated 7 years, 1 months ago ago by Olga Barlow

  • Avatar: pdisanti
    pdisanti
    Participant
    November 20, 2016 at 22:39

    Install the wordpress Xstore template correctly and configure it in general
    correctly. But I note that the translation of some screens woocommerce is partial, such as the cart or payment of the purchase, some terms are in English and others in Spanish. And this happens even though the file in the folder “wp-content \ languages \ plugins \ woocommerce-es_ES.po” has all the corresponding translations. How do I do to make the template completely translated and in particular the referred to woocommerce?

    Please, contact administrator
    for this information.
    5 Answers
    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    November 21, 2016 at 19:09

    Hello,

    Please, follow the instructions to translate our theme https://www.8theme.com/documentation/xstore/theme-translation/base-theme-translation/ and XStore Core plugin.

    Regards

    Avatar: pdisanti
    pdisanti
    Participant
    December 4, 2016 at 16:22

    I have tried the indicated and I manage to translate a good part of the site including the chains of woocomerce but some terms like “Checkout” or “View Cart” of the dialogue of purchases can not be translated, as it is seen in the attached image.

    http://dev1.bluetoothshop.com.ar/translation-error.png

    Could you tell me how to proceed? Thank you.

    Please, contact administrator
    for this information.
    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    December 5, 2016 at 13:54

    Hello,

    Provide me temporary admin panel and FTP access.

    Regards

    Avatar: Blackbeard
    Blackbeard
    Participant
    November 22, 2017 at 14:00

    Hi, I also can’t seem to get cart widget strings translated.

    Edit: it seems to have solved after 30 minutes…

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    November 22, 2017 at 15:24

    Hello, @Blackbeard

    So, the problem was solved, right? Maybe it was some cache.

    Regards

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

You must be logged in to reply to this topic.Log in/Sign up

Helpful Topics

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