Should I always use the Loco plugin, even after the theme translation?

This topic has 2 replies, 2 voices, and was last updated 3 years, 9 months ago ago by Olga Barlow

  • Avatar: Rodrigo
    Rodrigo Carlos
    Participant
    July 11, 2020 at 20:55

    Hello people,

    In the Loco plugin there is an information saying that the location where the .po file is (wp-content/languages​/themes/xstore-pt_BR.po) can be modified or deleted in the automatic update of the WP: https://prnt.sc/tg0zzk

    And it’s really true, because if I translate the entire .po file and instead of using the Loco plugin location (wp-content/languages/loco) to save the .po file I use the default theme location (wp-content/languages​/themes/), when the theme is updated, my .po file (all translated) will be replaced by your .po file.

    In this case, do you recommend that I keep the Loco plugin always activated, even after the whole theme has been translated?

    I ask because I wanted to translate the whole theme with the Loco plugin, download the fully translated .po file, go up to the standard wp-content/languages​/themes/ folder (instead of the Loco plugin folder wp-content/languages/loco) and then disable the Loco plugin in order not to get a plugin activated while not using it, this helps to slow down the site.

    Thank you!

    1 Answer
    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 13, 2020 at 12:53

    Hello,

    During the update, our theme does not affect any files in the wp-content/languages​/themes/ directory, only in the wp-content/themes/xstore/languages​/folder. Even if you update the WordPress itself wp-content folder does not change. But in the update we add the new strings sometimes and once you Sync your translated file with the updates pot file from our theme you may get new untranslated strings.

    Regards

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

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

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