Not sure why, but checking “Disable translation for gettext strings”, as you previously suggested actually breaks the translation on my homepage. So I’ve re-enabled that (having it disabled didn’t solve my current problem anyways).
I’m also now wondering if perhaps there’s an incompatibility with TranslatePress and the latest version of WordPress that’s caused this issue with the WooCommerce URL’s translating and the translations now being attached to those URL’s. I’ve run the staging and disabled every other plugin (aside from the theme and WooCommerce itself), and this still persists.
The default language has always been English, never French.
I have now checked the box to disable translation for gettext strings. This has not fixed the issue at hand.
This issue still persists with caching and security disabled.
I’ve also excluded /product/ and /product/* from translation (via exclude strings), this has not fixed the issue.
To reiterate, currently all of my woocommerce product translation pages only work when the url is /fr/produit/sample-product/ . Before updating this plugin, they only worked when the url was /fr/product/sample-product/ . I would prefer that they only work with /fr/product/sample-product/
I’ve created a temporary workaround with my header menu, which is why you see success there: For some reason the plugin is translating the urls from the menu when they are inserted as custom links, and not when they are inserted into the menu as product pages. However my general shop page continues to reference /fr/product/sample-product/ and thus leads to a 404 error, and going to edit translations on the product pages themselves always leads to a 404 error.
This issue began after I updated the translate press plugin, but I believe I was two updates behind, so one of the last two updates seems to have caused this issue for me.
I don’ think I can attach a picture to my reply, the loader is spinning endlessly, but if I can it will be here:
It’s been 5 days now, since I’ve last received a response. Any update on this issue???
To reiterate, I’ve removed every instance of “Product” translating to “Produit” that I have access to, with no success in rectifying this error. I do not have a paid version of the plugin, so I cannot translate urls to be able to make the final edit you are saying is required.
If the resolution is locked behind a paywall, then I’ll be officially filing a negative review stating as such.
I have the free version of this plugin, so I don’t have access to the PRO required to manually update slugs.
Following your advice as best as I can considering no slugs access, I’ve went through the Strings and deleted any instance of “Product” translating to “produit” and then refreshed my site cache. This issue still persists despite all of those steps.
Please advise a solution that works with the free version of this plugin. This issue only came to be after I updated to the most recent version, however reverting to an older update is not fixing it.
Update: The issue seems to be with the URL string. Specifically that “product” needs to be translated to “produit” for the french translation page to work.
Further update, the limiting to USA only feature is completely broken, in that it does not work. I can set a VPN to Canada, USA, Shanghai and it will showcase this popup in all 3 locations.
Thank you very much for your prompt reply! I was running some further tests after making this post, and it seems that the front page pop-up only works when the visibility rules have it noted as a static page, with no other potential static page or regular page options. This seems to be the case even when “Any” is the choice selected as opposed to “All”.
It also seems to be the case that the only certain countries field only works one time, meaning if I make two rules on the pop-up where rule#1 is only visible in the USA on the static front page, and rule#2 is only visible in the USA on the other page, the rule#1’s country limited visibility breaks. This is why the country limited visibility wasn’t working for your viewing purposes.
I had wanted this pop up to appear on the front page as well as one other page. Since it seems to be unable to handle this request, I’ll be making a second pop-up just for that page as a work around.
Thank you very much for your time and attention into this matter.
Error still happens. I believe it’s to do with one of the following:
Divi 4.14.7
WooCommerce 7.0.0
WordPress 6.3.2
This issue began with one of your updates a few months back, I typically do not update plugins/themes unless they state a security reason to do so. So with that in mind, I’d say it’s one of your updates that’s conflicting.
I’ve waited a month without a reply, so no this has not in anyway been resolved. I simply gave up on asking for help.
As I said in my last update, this happens when the WooCommerce shopping cart is set to a value of 0.
I also asked if you thought the troubleshooting area would be of use to me, to which I also received no reply. I decided not to wait and try them anyways, and I can confirm to you that the troubleshooting area did not resolve the issue.
I won’t be removing WooCommerce from my site, nor will I be removing the Divi theme, so if there isn’t a solution I guess I’ll be switching translation providers sometime in the future. Your plugin was great until one of the updates caused this issue, but it must be causing a big conflict with either woo commerce or divi if it’s still not resolved.
