Translations stopped being respected in Filter by Attribute block

  • This problem has already been solved before and it seems to have occurred again:

    https: //github.com/woocommerce/woocommerce-blocks/issues/9870

    The Filter by Attribute block has a Select %s translatable string for the placeholder (For example “Select Color”).

    I used Loco to translate it to just %s, so the placeholder would read simply “Color”.

    That used to work until the recent WooCommerce update.

    After the update, the placeholder reads “Select Color” again.

    I’ve verified the string is still translated on Loco, synced the translation, and saved it – it didn’t help.

    If relevant, the block is placed on the front page.

    Tested with Twenty Twenty Three and all other plugins deactivated.

    …

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Chris Moreira – a11n

    (@chrism245)

    Hello!

    <span style=”box-sizing: border-box; margin: 0px; padding: 0px;”>I understand that this issue started with the previous WooCommerce update. Can you update the plugin to the latest version,?9.6.0,?which was released one day a</span>go??

    Thread Starter i have a question

    (@freelancelab)

    Hi! I did not have the problem after updating the previous version of WooCommerce. There was no filter on the site before. It was connected and this problem occurred immediately. I have now updated to 9.6.0, the problem remains.

    Plugin Support Paulo P – a11n

    (@paulostp)

    Hello,

    Thanks for writing back and sharing the additional details.

    I tested this just now on a brand new test site with the latest WooCommerce and Loco Translate plugins and had no issue with removing the Select out of the Select %s string or with translating it to something else. Here are some screenshots from my test:

    Screen Shot

    Screen Shot

    If you’re still unable to see the translated version when using only WooCommerce, please make sure there isn’t any browser or server cache preventing you from seeing the latest version of the page.

    Thread Starter i have a question

    (@freelancelab)

    There is no line “Select %s” in my translation. The translation is uploaded automatically. When I make a copy of this translation and tick the “Merge strings from related JSON files” box, the “Select %s” field appears. Apparently these “related JSON files” have a higher priority.

    Plugin Support Paulo P – a11n

    (@paulostp)

    Hello,

    When I make a copy of this translation and tick the “Merge strings from related JSON files” box, the “Select %s” field appears.

    Great! Thanks for confirming you’re now able to edit the “Select %s” string. I’ll go ahead and close this topic then. Have a nice day!

    Thread Starter i have a question

    (@freelancelab)

    No, you don’t understand me. The field “Select %s” appears, but the problem remains. The changes in this translation do not lead to anything. Apparently these “related JSON files” have a higher priority. My generated translation is ignored. The information is taken from the content JSON files.

    Plugin Support Chris Moreira – a11n

    (@chrism245)

    Hello there,

    Thanks for sharing that. Based on your explanation, it seems the challenge isn’t specific to WooCommerce itself but rather relates to how translations managed through Loco Translate are influenced by the “related JSON files.” These JSON files appear to have a higher priority than the custom translations you’ve created.

    Since this issue touches on how Loco Translate integrates or prioritizes translations from JSON files, it may be best to consult directly with the Loco Translate support team or their community for specific guidance, you can reach them here: https://www.ads-software.com/support/plugin/loco-translate/

    Thread Starter i have a question

    (@freelancelab)

    Thank you, the issue has been resolved by the Loco Translate support team.
    https: //www.ads-software.com/support/topic/related-json-files-have-a-higher-priority/

    Plugin Support Mahfuzur Rahman(woo-hc)

    (@mahfuzurwp)

    Hi @freelancelab ,

    Thank you for letting us know! I’m glad to hear the issue has been resolved by the Loco Translate support team. I’ll go ahead and mark this thread as resolved now.

    If you have any further questions, feel free to reach out.

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.