|
Manuel
|
September 11, 2023 at 7:42 am
In one of the latest versions of Event Espresso there seems to be a problem that the translation is not used for “An error has occurred:”. I did not encountered this in the past. I have double checked the language file, and there is indeed a translation for this: “Er is een probleem opgetreden:”.
I have now encountered this with the error message if a clients selects more tickets than the allowed number of tickets. The second part of the error message is translated without any problems. Only the first part “An error has occured:”
|
|
Tony
|
September 11, 2023 at 9:07 am
Hi there,
Within the translation, do you have a <br> tag at the end of the string?
|
|
Manuel
|
September 13, 2023 at 9:44 am
Hello Tony, there is indeed a br tag in the end, but also in the orginal it’s the same. See screenshot of the translation:
https://pevaz.be/wp-content/uploads/Schermafbeelding-2023-09-13-174310.png
|
|
Tony
|
September 13, 2023 at 12:25 pm
When did you generate that POT file?
We haven’t had a <br> at the end of that string for some time now, to fix you need to update your translations with the latest POT.
Thats Loco Translate if I’m not mistaken? Where are you loading the POT (Template?) file from?
|
|
Manuel
|
September 13, 2023 at 1:13 pm
That’s indeed Loco Translate. I have just synced the rules, and indeed this resolved the issue. It was the <br>. You can close the ticket.
Thanks for your help.
|
|
Tony
|
September 13, 2023 at 1:22 pm
Oh, awesome… I forgot Loco allows you to scan for changes.
Anyway, I’m glad you’ve fixed it 🙂
|
|
Manuel
|
September 14, 2023 at 9:40 am
Loco is for me the best translator plugin 🙂 Thanks for all your help.
|
|
Tony
|
September 14, 2023 at 9:43 am
Yeah I don’t use a translation plugin often… but I’ve worked through a few to look at integrating with Event Espresso and out of all them if we put any time integrating with better it would like be loco.
No problem and any further issues just let us know.
|
