• Hi,
    With the new update, this plugin caused be to lose all translated words being sent via email. Not even in the preview mode, also the actual messages sent with original language not the language used in the website.

    When I de-activate only this plugin, I can receive email messages with the translated words. But of course I lost my customisation by this.

    Please update it.

    Thanks

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hey,
    Did you translate this plugin manually through POedit and upload the language files or through another plugin like Loco translate? What were your settings?

    Woocommerce plugin can’t translate this plugin. Woocommerce has translations already for the emails: https://translate.www.ads-software.com/projects/wp-plugins/woocommerce

    When you run this plugin you have to manage the translations.

    Ben

    Thread Starter bo9adiq

    (@bo9adiq)

    Hi,
    I am using loco translate plugin. I used to do like this previously and everything was fine until today.

    I have tested in that plugin without issue. What are your settings? What language?

    When you preview in the customizer what isn’t being translated?

    Ben

    Thread Starter bo9adiq

    (@bo9adiq)

    Hi,

    What settings are you asking for exactly?
    Language is Arabic.
    When preview, strings remain untranslated, like (welcome to the site this is your username:) even tho it is translated.

    Hey,
    One of the goals of this plugin was to make the body text editable. Which means that it’s not a static string that you translate. It’s content similar to content in a page or post. You don’t translate the content you just edit it to be whatever you want.

    “welcome to the site this is your username:” is part of the body text of the new account email. It’s not a static string for translation when you use this plugin it’s content that you control and edit right in the customizer.

    If you are trying to translate that string then it won’t work like that you have to edit the content. Does that make sense?

    Ben

    Thread Starter bo9adiq

    (@bo9adiq)

    Sure, this sounds right.
    I posted this because it was working properly when I relied on this plugin to customize the fonts colors size paddings etc. I was satisfied with the same original content but translated. People may use part of the features you provide and everyone has different needs.

    Well, its now not working like (two days and the days before that.)

    Solving this is always up to you guys. Issue reported and my job is done.

    Thanks for your effort,
    Jaafar

    Hey,
    I’m not sure I understand. Can you send me a screenshot of the customer new account email showing the body text input field on the left?

    There isn’t a default Arabic translation in this plugin yet (you can help provide that if you like, you would be helping everyone who needs Arabic with this free plugin).

    Without it as soon you saved body text in the customizer that body text is defined. Since there isn’t an Arabic translation that body text would default to be English. Once saved and defined you are the only one that can control it because you can add whatever content you want into that body text. Nothing I do with this plugin, no update can change what you’ve defined as your body text.

    Does that make more sense? I’m not sure what you are thinking I can do but I can’t change what is saved in your body text. So are you saying the body text is in Arabic and it’s not taking effect in the email?

    Thanks!

    Thread Starter bo9adiq

    (@bo9adiq)

    Hi,

    It might be my fault not explaining this perfectly.

    What I meant, I was using this plugin to make my emails more cute (playing with CSS). I changed nothing in the body text. I customized the default body text that woocommerce provided.

    Now, when I translate the strings (which are used as default body text in woocommerce emails) to Arabic using Loco Translate plugin, the body text appears in Arabic in both your plugin and the actual email sent.

    For example, if this is a default body text: Hi %s welcome to %S.
    I make a translation to: ?????? %s, ???? ?? ?? %s.

    This way, I can see the arabic words in your plugin and play with CSS.

    Unfortunately something happens after the latest auto-update which stopped the Arabic words to show in either your plugin or the actual email sent. Even tho I am sure all strings have translation but ignored in the emails.

    Can you send me a screenshot of the customer new account email showing the body text input field on the left? That is the “Email Type and Text” section.

    That will help me understand. If the screenshot shows English in the body text then it was saved and that is overriding any translations.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘translating being ignored’ is closed to new replies.