Saul

Firstly I never claimed to be the creator of those threads. I honestly have no idea why you’re making these assumptions.

Secondly, are you joking? Default WooCommerce archive AJAX redirects to the product page to show the error notice when there is one. And the newer product archive block shows the error notice directly above the catalog list.

You’re making false claims just like the replies in those support threads, to avoid a few minutes of development. Rendering error notices and inserting them into the page is far from “impossible”. Even if you just redirected to the same product page to show the notice I’m sure your users would be fine with that.

I’m also done wasting my time trying to convince you to fix your own theme. My review remains as it’s a review of how you and your team has handled this issue over the years. By gaslighting your users, making false claims, and a general lack of pride in the product you’re shipping.

You’re right, I’m not a user of OceanWP, fortunately. But I am a plugin developer who’s users have been running into this issue on your theme. Because as I and many other people have mentioned over YEARS, you have zero support for simple WooCommerce product stock error notices with your AJAX add to cart which is enabled by default.

Since you’re so attentive you’ve surely seen these threads. Not that you should need to since you could look at the JS file I mentioned for 2 minutes and see no support is implemented.

• https://www.ads-software.com/support/topic/notices-after-ajax-add-to-cart/
• https://www.ads-software.com/support/topic/notices-after-ajax-add-to-cart-2/
• https://www.ads-software.com/support/topic/notification-while-trying-to-add-to-cart-more-than-stock/

Ignoring issues being reported from multiple users for years and then accusing bad reviews of being fake is peak delusional I must say.

(DELETED)

@ksaltik, you can use attribute stock like that, except it doesn’t handle pricing automatically. Only stock quantities are calculated and tracked. Pricing must still be managed on your products.

Glad to hear. Looks much better now.

I assumed you guys actually fixed this, but I just had another user run into the same issue with your plugin.

I checked and you haven’t updated the code I was referring to at all. You still have the same bug that causes an error to show when using OAuth params in the URL.

If my explanation of the problem wasn’t clear enough, go to your WordPress admin (with Rank Math activated) and add an access_token param to your URL like this:

https://example.com/wp-admin/?access_token=123

See how it says The link you followed has expired.? Now imagine another plugin needs to use access_token in the URL. Well they can’t because you’re basically blocking it for any other plugin but your own.

Get this fixed asap or I’m reporting this blatant disregard for other plugins to the WP plugin directory moderators.

This looks really great. Nice work!

That’s great news! I’ll definitely try it out, at least to make sure it’s working with my plugin.

Thanks for the heads up on the text domain. I’m using woocommerce-attribute-stock because that’s the slug/name of the full version. I figured the text domain of the lite version wouldn’t work with GlotPress anyway since WP says this in their docs:

The text domain must match the slug of the plugin. If your plugin is a single file called my-plugin.php or it is contained in a folder called my-plugin the domain name must be my-plugin. If your plugin is hosted on www.ads-software.com it must be the slug portion of your plugin URL (www.ads-software.com/plugins/<slug>).

I’ll add it in anyway, at least so the lite version works better with Loco Translate. The full version should already work since the plugin name and domain are the same.

Thanks for the feedback thus far @timwhitlock. I appreciate the prompt responses, and the effort you’ve made with this feature already.

If you don’t get a chance to follow up on Monday I won’t hold it against you ??

I might agree with you, but having answered over 2000 support requests for this plugin I can safely say that this does not reflect reality.

Fair enough. However, my limited experience has been users asking me why my plugin doesn’t work with Loco Translate, not the other way around.

But I can’t make it a high priority as so few people have actually asked for it.

Understandable. I expected to find a lot more threads about this, after 2 years since WP 5.0 was released. Though some more general “translations don’t work” threads may be related to this indirectly.

Feel free to post a link to your plugin, so when I next get the chance to look at this I can take yours as a best case example.

https://www.ads-software.com/plugins/attribute-stock-for-woocommerce/

But that’s exactly how wp i18n make-json works. It generates the JSON files and hashes based on the file paths provided in the POT file.

If a plugin’s POT file contains invalid paths, that’s on the plugin author. I don’t think anyone expects Loco to do any more magic than wp-cli would be able to do.

DELETED

Thank you!

Thanks, I’ll give it a try.

Ok I’ve done so.