DickRaney

what I am saying is, whenever I log in, it shows update available for translations. When I run the update it says translation successfully updated and does not show updates available. But if I log out and then log back in it says there’s an update available for translations.

I don’t know if there are translation updates. We are just using Loco Translate to change the word “wholesale” to “contractor”. That is the only translation.

Wholesale for Woocommerce

https://we.tl/t-da4doi4ggL

If Community Translations are the normal translations, then yes I have them updated.

For download link link, do you mean for your plugin. We’re using the latest version.

• This reply was modified 1 year, 10 months ago by DickRaney.

if I uninstall loco translate the message stops. But I don’t want to uninstall it.

Thanks! Sorry for the confusion

I used troubleshooting mode to deactivate everything and then updated translations. It said it was successful and then I exited troubleshooting mode and I don’t have an update available notice right now. So, maybe it is working now, even though I am right back to the same setup I had.

Plenty of space
No Health issues
WordPress 6.1.1

I deactivated everything except “WooCommerce” and “reCAPTCHA for WooCommerce”?and my theme “Flatsome” and it is still the same, No Captcha on the popup login form. Also there are no errors in developer console.

This is not ideal, but allows you to set the link to color you want without any box around it.
<div class="unsub"><style>.unsub a{color:#0000ee!important;}</style>{{cart.unsubscribe}}</div>
Developer still needs to come up with a setting for link color or just remove the inline color style.

I have the same issue and would like an answer too.

Sorry, after further inspection, the lightbox was coming from another plugin.

Since it is a default theme for WooCommerce and used by so many people, I was sure there had to be a better way. But thanks for your trouble. I guess we can’t expect a real fix anytime soon, so will have to resort to this hack solution.

I increased memory_limit from 128M to 256M and am not seeing the errors now, so I will watch and see if that fixed it.

That snippet will help. If I do that, how do I designate a page (other than home page) that I do want to cache?

It looks like that snippet force DONOTCACHE (not cached) on everything except homepage/front_page that isn’t specifically defined as DONOTCACHEPAGE. So, a page /EXAMPLE would not be cached unless I define it as DONOTCACHEPAGE. In other words. defining as DONOTCACHEPAGE actually makes it get cached. Or am I misunderstanding the PHP logic ! defined('DONOTCACHEPAGE')?