• Resolved diffler

    (@diffler)


    Found the following strings I can’t translate with Loco Translate:

    1. “Please tick this box to continue” (If customer didn’t tick the agree to privacy policy box in withdrawal form”
    2. “We could not match these details with an order in our records. Please double-check the order number and the email address using the “Edit data” button below. You can still confirm: your request will be registered and reviewed manually by the shop.”
    3. “We will review the request and confirm next steps as soon as possible. If you do not hear from us, please reply to this email.” (In email to customer after submitting withdrawal request)
    4. Order (In email sent to admin after withdrawal request)
    5. Scope (In email sent to admin after withdrawal request)
    6. ⚠ UNVERIFIED REQUEST: these details could not be matched with an order.
    The reference matches order #12561, but its billing email differs from the address submitted.
    It was registered because “Accept unmatched requests” is enabled. Verify it manually against your records before deciding. (In email sent to admin after withdrawal request)

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Fernando Tellado

    (@fernandot)

    Hi @diffler,

    Thanks for the detailed report, and for listing exactly where each string shows up. That made it quick to check.

    I have verified all six strings and they are translatable. All of them are wrapped in __() or esc_html_e() with the correct text domain, and all six appear in the translation project at translate.wordpress.org (411 strings in total).

    I also ran Loco Translate’s own string extractor against the plugin on a test site: it scans all 23 PHP files and finds 415 strings, including your six. So Loco does see them.

    What I think is happening is where Loco is saving your PO/MO file. Loco offers three locations, and only two of them work here:

    • Custom (wp-content/languages/loco/plugins/) -> works
    • System (wp-content/languages/plugins/) -> works
    • Author (inside the plugin folder /languages) -> does NOT work

    If you saved to “Author”, your translations are written correctly but never loaded, while whatever already came from wordpress.org keeps showing up translated. That gives you exactly what you are seeing: most of the plugin translated, a handful of strings stubbornly in English.

    Could you check under Loco Translate which location your file is in? If it is “Author”, create the translation again choosing “Custom”, which is the safest one: it also survives plugin updates and it merges with whatever comes from wordpress.org.

    One more thing that may explain the third string on your list. In version 2.2.1 I changed that line from “within 24 hours” to “as soon as possible”, so any earlier translation of it became stale and reverted to English. That one simply needs translating again.

    Finally, a suggestion. Rather than keeping a local file, consider translating the plugin at translate.wordpress.org:

    https://translate.wordpress.org/projects/wp-plugins/eu-withdrawal-compliance/

    Translations approved there are shipped to every site automatically, they never get lost on update, and other shops in your language benefit too. If you tell me your locale I can point you to the right team, and I am happy to help get your strings reviewed.

    If after switching the location you still see any of those strings in English, let me know your locale and your plugin version and I will dig further.

    Hugs!

    Fernando

    Thread Starter diffler

    (@diffler)

    Thank you very much for your quick reply and confirming these strings exists. I have selected Custom in Loco Translate.

    But ahh, I understand the problem now. I uploaded an unsynced .pot file from an older version of the plugin from another site. I uploaded the .pot to a new site and because of this, it didn’t find the strings of the new version.

    Thank you very much for your help! I added my translations to the project. I’m rarely translating the whole plugin, only the front-end parts so sadly it won’t be enough to get Finnish translations added.

    Plugin Author Fernando Tellado

    (@fernandot)

    You’re welcome @diffler. Glad to know it helped 🙂

    Fernando

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

You must be logged in to reply to this topic.