<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?? ]]>
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:
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.
]]>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!
]]>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/
]]>https: //www.ads-software.com/support/topic/related-json-files-have-a-higher-priority/ ]]>
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.
]]>