• Resolved evatb

    (@evatb)


    Hi again!

    I’m working on translating the create account/login proces with the help of Loco Translate. I’m noticing that while a lot of the strings are available in the back-end, the translated version never appears. Most noticeability the whole Login page (/account) can’t be translated.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Anonymous User 14012828

    (@anonymized-14012828)

    @evatb
    I also use Loco translate to translate Masteriyo strings into Turkish. Just a few minutes ago, Masteriyo was upgraded and I translated the added 12 strings as well. Seeing your post above, I checked the issue on two websites – one on the internet and the other on localhost – but everything looks fine. All strings appear in Turkish. Perhaps clearing your internet browser’s cache might help.

    My translation file is at this location: languages/loco/plugins/. If the problem still persists, you might use Loco and try moving the language file to languages/plugins/ or plugins/learning-management-system/i18n/languages/

    Good luck! 🙂

    Hi @evatb,

    All strings translation should work properly as we have now at this point made many updates regarding translation process and all. However, I will ask my team to check and confirm that everything is fine on this.

    Yes, just confirmed by retesting. It is working all fine.

    Anonymous User 14012828

    (@anonymized-14012828)

    I do not know whether evatb has already solved the problem, but I am having a similar problem now with the “account” page. The language for the whoke website is Turkish. Users’ preferred language is also set as Turkish in the WP profile page. However, /account/#/dashboard remains in English. Using Loco translate plugin, moving the language file to the system or plugin folder makes no difference.

    Hi @hakangur,

    Well, the issue evatb raised previously was already resolved. This new issue may have come after version 1.4.0 which our team is already looking into.

    Also, I suggest you to create new ticket as we were unaware that you had commented here else we would have checked this issue few days earlier. I know this was similar ticket so you may have decided to just add comment here but still new support thread would have notified us better. 🙂

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Translation strings not available’ is closed to new replies.