Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • I’m wondering the same thing. Does anyone have any workaround for it?

    Thread Starter nikhlede

    (@nikhlede)

    Well, if I was searching for a company, say “Pepsi” in this case, I would always use the search term “pepsi”, regardless of which country I’m from and which language I use.

    The same would apply if I was searching for a specific product, for example “Samsung Galaxy S22”, that product name doesn’t change regardless of where you’re from, you (or me) would always type in “samsung galaxy s22” in the search bar, correct?

    These are my thoughts, anyway. Thank you for the reply and provided links, but I’m afraid that they don’t help me specifically tackle my issue. I’ve read through several articles and posts, but I have yet to find what I’m looking for to help me answer my question, hence why I’m asking for help here.

    Thread Starter nikhlede

    (@nikhlede)

    Hey Sravan,

    Any news regarding this yet? I need to know if you can “add” this in, or if I need to start looking at other alternatives.

    Kind regards

    Thread Starter nikhlede

    (@nikhlede)

    Hey Sravan,

    Well, I wish it would, but I still get this.

    https://www.loom.com/share/0243ae30285344948e02e4af32da81f8

    I’ve made sure everything is updated before posting this, and like I’ve previously stated I’ve also made sure that those Colors, as well as subsequent strings are actually translated.

    Kind regards

    Thread Starter nikhlede

    (@nikhlede)

    Hi Sravan,

    I’ve tried it and they actually don’t appear eitherway.

    Thread Starter nikhlede

    (@nikhlede)

    Hey Sravan,

    I tried to do that. Like I said, I’m using TranslatePress for the website, and temporarily I’ve even installed LocoTranslate – yet no matter what I do that text just won’t change.

    Like I said, I can “primarily” edit it – meaning I can choose what the button says (however the choice I make seems to be made for both languages by default).

    I’ve tried and searched the strings, etc. … I’ve even tried custom coding to change it based on the language chosen – but so far I’ve had no luck doing any of those things.

    Kind regards

    Thread Starter nikhlede

    (@nikhlede)

    Hey Karla,

    I read through that ticket, yeah, but unfortunately that ticket doesn’t really help at all since it just basically says that that’s out of your hands – sort of.

    About the thread you linked to – I can see that at the very bottom a supposed “solution” has been posted (pointing to this link).

    Rest assured I’ve read through it, but I’m still a bit confused. First of all, am I supposed to copy that piece of code and place it into my functions.php file? Have I understood that right? If this is the case, I should probably copy the folder into my child theme and then add this content at the bottom, correct?

    Plus – there’s a note above it which says:

    Note: “As of TranslatePress Version 2.3.5, this functionality was implemented natively by TranslatePress, making this Code obsolete.”

    I’m just trying to make sure I have everything down correct – and admittedly it’s my first time dealing with these sorts of issues, hence why I’m being careful and asking about everything twice, before I go and do something that might mess things up.

    I seriously appreciate the help though.

    About the screen recording / screenshot – I’m not quite sure what you mean, I mean … which screenshots would you like me to take?

    I can show you how the emails that were sent out look, and that everything on them is in the correct language (based on the user making an order either on the Primary page language (Slovenian) or the secondary (English)). But I’m not sure why or how this is something that you would need to replicate.

    Also – one other thing which bugs me, now that I think of it. Shouldn’t the basic WooCommerce emails also behave in the same way as the Kadence ones, in terms of recognizing the correct language in which to send the email out to? Since this is basically an E-mail customizing plug-in, but it’s not what keeps track of languages chosen.

    My apologies if I haven’t been clear enough at some points in my post, and mostly for not understanding everything down to its core – just know that it’s not due to a lack of trying.

    I’m willing to do what it takes to get stuff to work properly, it’s just that I need some help / someone to point me in the right direction.

    Thanks for the info and help so far, here’s hoping for some more clarification on the issue at hand

    Kind regards

    Nik

    Thread Starter nikhlede

    (@nikhlede)

    * Update *

    When searching for “Price” under strings, it shows me 3 seperate “Price” strings from Kadence.

    However, only one of those strings can actually be translated for some reason (and even that one doesn’t get recognized during the e-mail translation), the others simply refuse to keep their translations regardless of how many times I save them over.

    Thread Starter nikhlede

    (@nikhlede)

    Hey Dragos,

    sure, I’ve actually done that already. And the default woocommerce emails are showing the correct translations for those subjects. I am however having trouble with translating certain parts of the email text (namely subjects and headings with dynamic content).

    For example, on the “Refunded order” template, I’ve set the Subject as “Vaše vračilo za naročilo #{order_number} je na poti” (it’s in Slovenian)

    – and it translates to “Your refund for order #{order_number} is on its way”

    However when looking for those strings, the dynamic ones don’t show, and instead I’ll find a specific one (for example: “Vaše vračilo za naročilo 9311 je na poti”)

    Which would basically only translate it for that specific order, which is obviously useless.

    Neither way is perfect, though I guess this one’s closer.

    But ideally I’d use Kadence because these default emails just look awful truth be told.

    Cheers

    Thread Starter nikhlede

    (@nikhlede)

    Hi,

    my apologies, but that video’s a bit redundant in my case. Like I said – everything functions perfectly in the main language, I’ve set everything up just like it should be, from that point of view.

    I haven’t worked with WPML before, but from what I can compare TranslatePress and Polylang are a bit different from one another.

    Eitherway, I’m a stickler for details, so I’ve gone through all of the translation (website & string-wise) before opening this topic.

    That’s just it, I know everything is translated, because I’ve done so manually, on all the pages.

    Cheers

    Thread Starter nikhlede

    (@nikhlede)

    Hi, thanks for the reply

    My apologies, but I don’t get how exactly this should be done.

    I mean, I’ve done what you’ve asked of me, however installing the 2021 theme basically breaks my website (I generally build all of my websites with Divi).

    Second, while I guess everything else can go, I have to have the AJAX filters plug-in, TranslatePress and WooCommerce (atleast) all activated in order to be able to troubleshoot this.

    Also, just to point it out – The website itself seems “broken” with the 2021 theme (which is to be expected I guess), however the filters themselves do show/work as intended. As soon as I switch from the 2021 theme to the Divi theme though, that’s when the text in the sidebar starts “dissappearing” so-to say.

    So judging by the information gathered, I’m guessing the culprit in this case should be Divi itself (not any other plug-ins), though that seems odd, since I don’t recall reading/hearing anywhere about this – as far as I know Divi plays nice with TranslatePress, and also with the AJAX filter plug-in I’m using (since the issue(s) literally began once I made the website multilingual).

    Hoping to hear back from you soon,

    Cheers

    Thread Starter nikhlede

    (@nikhlede)

    Hey,

    thanks again for the quick reply.

    This one’s on me. I’ve managed to translate it fully now, it’s just that at the time of writing this initially, TranslatePress wouldn’t allow me to edit that specific page for some reason, hence why I turned to this forum again.

    It’s working fine now, but seriously – thanks again.

    Have a good one

    Thread Starter nikhlede

    (@nikhlede)

    Found the culprit and fixed it.

    Thread Starter nikhlede

    (@nikhlede)

    P.S. – I just remembered something, just incase you or anyone else might find it useful:

    I used this piece of CSS code in order to make sure everything in the order details table fits on mobile view – I might be missing something, but by default some of the information on it was being cut off.

    @media (max-width:600px) {
    .table-text .et_pb_text_inner {
    overflow-y: auto !important;
    }
    }

    Have a good one, and thanks again!

    Thread Starter nikhlede

    (@nikhlede)

    Hi,

    thank you so much. That solved it, you’re awesome!

Viewing 15 replies - 1 through 15 (of 18 total)