Conversation
supportHello Gerard, My main shop page has product categories listed, no products. Main shop page and single product pages are translated with the plugin and can be navigated. Butwhen I click on any product category on main shop page, it goes to 404. It should open the category page which list all the products under the category. I suspected it may be due to change in URL slugs, so I tried “Keep URL Slugs in English” but check box is going unchecked every time I save the config change. It may be an unrelated issue, but there it is. Best,
You are absolutely right on both issues. I have investigated it and fixed them along with some other issues with WooCommerce like translating the shopping-cart and your account. Which are not very likely to happen, but anyway. The “Keep URL Slugs in English” is fixed also, but is not advised to use. The URL is translated now for products and it is better for SEO to have a translated slug. Please update the plugin to v2.3.6 and let me know if all is fine now and close the ticket.
Hi Gerard, Thank you for swift support. I updated and tested the plugin on my website. My test findings are as follows; Selected French, as the sample language: Products Main page URL : /fr/produits/ Product Main Page. Lists “Products Categories” correctly in French and all other languages. Category Main Page URL : /fr/product-category/oil-hoses/ Category Main Page: Lists “Products” correctly in French and all other languages. Product Pages: /fr/product/flx-air-jaune-300/ : Product name translated. Product page goes “404”. Original URL(en) : /product/flx-yellow-air-300/ /fr/product/flx-oil-sd10-cannelé/ : When Product name translated, in some case “Page isn’t redirecting properly” error appears. Original URL(en): /product/flx-oil-sd-10-channeled/ /fr/product/flx-air-20/ : Translated Product page displayed. URL is same as original (en), ie “product name” is not translated. I also tried “Keep URL slugs in English” but it did not seem to work. I cleared all cache that plugin stores before and after in addition to purging site cache. But unfortunately, I was not able to make it work. Though, I may have missed somethings. As far as understand, there is problem of resolving translated product page URLs. It may be a good thing to translate “Product Name” for some cases/users, but in our case we don’t prefer them to be translated. So, it may be better to have a check box whether to translate Woocommerce Product Name or not. If you need any more details, please let me know. Best,
Thank you for the detailed test report — it was very helpful in pinpointing the exact issues. I have released an update that addresses all the routing problems you reported: Fixed in this update: “Keep URL slugs in English” now works reliably, including when translated slugs were already stored from a previous run. Previously the setting was only applied to pages that had never been translated. Old translated URLs (e.g. /fr/product/sorciere/) will automatically redirect (301) to the English slug version — no manual cleanup needed. French/accented slugs no longer cause a redirect loop. Slugs like cannelé are now correctly transliterated to cannele (matching how WordPress itself handles post names). This resolves the “page isn’t redirecting properly” error on products with accented characters in their name. 404 on previously-translated product URLs is fixed. If a product slug was re-translated after the source slug changed, the old translated URL is now recovered from history and redirected (301) to the current correct URL instead of returning a 404. Regarding your feature request — a checkbox to skip translating WooCommerce product names: that is a interesting request, especially for shops with brand names and product codes. I have noted it as a feature request . Please update the plugin, clear your site cache, and test again. Let me know if you run into anything else. Remark: WordPress recently introduced a 24 hour time lag for updating plugins to be able to scan for security issues. So you need to use the development version for now. Tomorrow v2.3.7 will be available.
Hi Gerard, The effort you put in this plugin, is just amazing. I hope, this plugin and you get the attention you clearly deserve in WordPress community soon. I could not find where to download development version. So I will wait until tomorrow. I will certainly update plugin and test it and get back to you. Just keep open the ticket for now. I also started translation of plugin to Turkish. We will see how it goes. Best,
I updated the plugin and my test findings are as follows; Selected French, as the sample language: Product Pages: Getting 404 error on all translated product name and pages. /fr/product/flx-air-jaune-300/ : Product name translated. Product page goes “404”. Original URL(en) : /product/flx-yellow-air-300/ /fr/product/flx-air-20/ : Translated Product page displayed. URL is same as original (en), ie “product name” is not translated. “Keep URL slugs in English” is now working. And it actually solves my problem with this site😊 Since “Keep URL slugs…” works, I guess translated page URLs might be creating some conflict with Woocommerce, since it is handling the shop side. There is also another issue I have encountered. I have tables that have numeric values on product pages, that I create with TablePress plugin. These numeric values are tanslated in some languages, I detected in Arabic and Russian. I think, it is an issue probably related to AI provider (gemini-3.1-Flash) that I am using. So, I tried Grog and the result is the same. I also noticed some different selections in translation of some words between 2 models. Of which I would prefer one and that resulted 2 new feature requests below. Feature requests: I agree with your Woocommerce remark. As Product names and Brands may be private and people may wanted no translation. In addition, Woocommerce has many features, so planning a Woocommerce section for the plugin may be better for future. As Woocommerce has a very large install base. New Feature requests: Do not Translate Shortcode: A shortcode that can be paste before the section in the content (table, paragraph, etc) that will tell AI model not to translate and show in original language. Exception list: There are homonymic words that can have different translation in other languages. It is especially important in technical (engineering, medicine, etc) jargon. User can enter on a 3 column list with Original word, Translated world and Translation language, that AI model can review before translation and process accordingly. Like a skill used on AI models. Additional Feature request: Shortcode for Language Switcher. People have very different designs so a shortcode accompanied by a Custom CSS section for switcher, may provide better design and user experience on their websites. To sum up, I am fine with the current solution but the issues are there as I stated. Thank you for your support. If there is anything I can help you with please let me know. Best,
Good observation about numeric values on product pages — this is not actually a bug and not a provider issue. Converting digits to Eastern-Arabic numerals (Arabic) and applying local number formatting (Russian) is linguistically correct localization, which is why Gemini and Groq give the same result: every provider does this by design. Whether it’s undesirable depends on what the numbers mean. For measurements/quantities it’s correct. For product codes, SKUs or technical reference values it’s better to keep them verbatim — and you can do exactly that without any code change: the plugin skips any element with the CSS class notranslate . In TablePress, open the table, go to “Table Options” → “Extra CSS classes” and add notranslate . That table (numbers and text) will then stay exactly as-is in every language.
You are absolutely right on both issues. I have investigated it and fixed them along with some other issues with WooCommerce like translating the shopping-cart and your account. Which are not very likely to happen, but anyway. The “Keep URL Slugs in English” is fixed also, but is not advised to use. The URL is translated now for products and it is better for SEO to have a translated slug. Please update the plugin to v2.3.6 and let me know if all is fine now and close the ticket.
Hi Gerard, Thank you for swift support. I updated and tested the plugin on my website. My test findings are as follows; Selected French, as the sample language: Products Main page URL : /fr/produits/ Product Main Page. Lists “Products Categories” correctly in French and all other languages. Category Main Page URL : /fr/product-category/oil-hoses/ Category Main Page: Lists “Products” correctly in French and all other languages. Product Pages: /fr/product/flx-air-jaune-300/ : Product name translated. Product page goes “404”. Original URL(en) : /product/flx-yellow-air-300/ /fr/product/flx-oil-sd10-cannelé/ : When Product name translated, in some case “Page isn’t redirecting properly” error appears. Original URL(en): /product/flx-oil-sd-10-channeled/ /fr/product/flx-air-20/ : Translated Product page displayed. URL is same as original (en), ie “product name” is not translated. I also tried “Keep URL slugs in English” but it did not seem to work. I cleared all cache that plugin stores before and after in addition to purging site cache. But unfortunately, I was not able to make it work. Though, I may have missed somethings. As far as understand, there is problem of resolving translated product page URLs. It may be a good thing to translate “Product Name” for some cases/users, but in our case we don’t prefer them to be translated. So, it may be better to have a check box whether to translate Woocommerce Product Name or not. If you need any more details, please let me know. Best,
Thank you for the detailed test report — it was very helpful in pinpointing the exact issues. I have released an update that addresses all the routing problems you reported: Fixed in this update: “Keep URL slugs in English” now works reliably, including when translated slugs were already stored from a previous run. Previously the setting was only applied to pages that had never been translated. Old translated URLs (e.g. /fr/product/sorciere/) will automatically redirect (301) to the English slug version — no manual cleanup needed. French/accented slugs no longer cause a redirect loop. Slugs like cannelé are now correctly transliterated to cannele (matching how WordPress itself handles post names). This resolves the “page isn’t redirecting properly” error on products with accented characters in their name. 404 on previously-translated product URLs is fixed. If a product slug was re-translated after the source slug changed, the old translated URL is now recovered from history and redirected (301) to the current correct URL instead of returning a 404. Regarding your feature request — a checkbox to skip translating WooCommerce product names: that is a interesting request, especially for shops with brand names and product codes. I have noted it as a feature request . Please update the plugin, clear your site cache, and test again. Let me know if you run into anything else. Remark: WordPress recently introduced a 24 hour time lag for updating plugins to be able to scan for security issues. So you need to use the development version for now. Tomorrow v2.3.7 will be available.
Hi Gerard, The effort you put in this plugin, is just amazing. I hope, this plugin and you get the attention you clearly deserve in WordPress community soon. I could not find where to download development version. So I will wait until tomorrow. I will certainly update plugin and test it and get back to you. Just keep open the ticket for now. I also started translation of plugin to Turkish. We will see how it goes. Best,
I updated the plugin and my test findings are as follows; Selected French, as the sample language: Product Pages: Getting 404 error on all translated product name and pages. /fr/product/flx-air-jaune-300/ : Product name translated. Product page goes “404”. Original URL(en) : /product/flx-yellow-air-300/ /fr/product/flx-air-20/ : Translated Product page displayed. URL is same as original (en), ie “product name” is not translated. “Keep URL slugs in English” is now working. And it actually solves my problem with this site😊 Since “Keep URL slugs…” works, I guess translated page URLs might be creating some conflict with Woocommerce, since it is handling the shop side. There is also another issue I have encountered. I have tables that have numeric values on product pages, that I create with TablePress plugin. These numeric values are tanslated in some languages, I detected in Arabic and Russian. I think, it is an issue probably related to AI provider (gemini-3.1-Flash) that I am using. So, I tried Grog and the result is the same. I also noticed some different selections in translation of some words between 2 models. Of which I would prefer one and that resulted 2 new feature requests below. Feature requests: I agree with your Woocommerce remark. As Product names and Brands may be private and people may wanted no translation. In addition, Woocommerce has many features, so planning a Woocommerce section for the plugin may be better for future. As Woocommerce has a very large install base. New Feature requests: Do not Translate Shortcode: A shortcode that can be paste before the section in the content (table, paragraph, etc) that will tell AI model not to translate and show in original language. Exception list: There are homonymic words that can have different translation in other languages. It is especially important in technical (engineering, medicine, etc) jargon. User can enter on a 3 column list with Original word, Translated world and Translation language, that AI model can review before translation and process accordingly. Like a skill used on AI models. Additional Feature request: Shortcode for Language Switcher. People have very different designs so a shortcode accompanied by a Custom CSS section for switcher, may provide better design and user experience on their websites. To sum up, I am fine with the current solution but the issues are there as I stated. Thank you for your support. If there is anything I can help you with please let me know. Best,
Good observation about numeric values on product pages — this is not actually a bug and not a provider issue. Converting digits to Eastern-Arabic numerals (Arabic) and applying local number formatting (Russian) is linguistically correct localization, which is why Gemini and Groq give the same result: every provider does this by design. Whether it’s undesirable depends on what the numbers mean. For measurements/quantities it’s correct. For product codes, SKUs or technical reference values it’s better to keep them verbatim — and you can do exactly that without any code change: the plugin skips any element with the CSS class notranslate . In TablePress, open the table, go to “Table Options” → “Extra CSS classes” and add notranslate . That table (numbers and text) will then stay exactly as-is in every language.