sajalwpdev
Forum Replies Created
-
Hi @pancrazio72,
Really glad to hear the setup was smooth and easy for you.
If you ever need anything, we’re here to help!
PluginEver SupportHey @bajlazzo,
Thank you so much, really glad it’s been useful!
If you ever need anything, we’re here to help!
PluginEver SupportHey @ephilant,
That really made our day, thank you so much! 😊 Comments like yours keep us motivated to keep improving.
If you ever need anything, we’re always here!
PluginEver Support
Really glad it’s sorted! 😊
If Min Max Quantities has been useful for you, a quick review on ww.wp.xz.cn would mean a lot to our small team, it genuinely helps other store owners find us.
👉 https://ww.wp.xz.cn/support/plugin/wc-min-max-quantities/reviews/#new-post
Thanks for your patience throughout!
PluginEver Support
Hi @joshuaall,
Good news, this has been fixed in the latest version (2.2.9). Please update the plugin and the workaround should no longer be needed.
Let us know if everything looks good after updating!
PluginEver Support
Hello @joshuaall ,
Thanks for reporting this, and great find on the workaround too! That’s really helpful for other users who might run into the same thing.
We’ll look into making the plugin properly compatible with Redis Cache so the workaround isn’t needed. I’ll update this thread once we have more information from our team.
PluginEver Support
Hello @fhwebdesign,
We’ve pushed a fix, and the plugin has been updated. Please update to the latest version, and it should resolve the missing assets and restore the frontend display.
Let us know if you’re still seeing any issues after updating. We’re happy to help!
Hi @fhwebdesign ,
Thank you for reaching out and bringing this to our attention. I’m sorry for the trouble you’re experiencing after updating to version 1.3.4.
Our development team is actively working on a fix, and we expect to release version 1.3.5 shortly with all the missing assets restored.
In the meantime, as a workaround, you can:
1. Download version 1.3.3 from the releases archive
2. Copy the assets/build/js/ and assets/build/css/ files into your current 1.3.4 installation
3. Clear your site and browser cacheWe sincerely apologize for the inconvenience this has caused. I’ll keep you updated on the fix release.
If you have any further questions or need assistance with the workaround, don’t hesitate to ask.
Best regards,
Support TeamHi @agroaxon
Thank you so much for your kind words. Glad to hear you found it useful!
If you ever need any help or have suggestions, feel free to reach out anytime. Happy to assist!
PluginEver Support TeamHello @asifmohtesham ,
Thank you so much for your great feedback!
We’re glad to hear that the plugin works as expected and that the combination of global settings and product-specific overrides is helping you fine-tune your setup easily.
If you ever have suggestions or need assistance, feel free to reach out. We’re always happy to help.
Thanks again for your support!
Hello @mik800,
Thank you very much for your kind words and for sharing your experience.
We’re really glad to hear that you found the plugin simple and helpful for managing personal finances. Our goal is exactly that: to make accounting easy and accessible for everyone, even for users without an accounting background.
If you ever have questions or suggestions, feel free to reach out. We’re always happy to help.
Thanks again for your support!
Hello @luboslives ,
Thank you for testing this again and for explaining the exact steps you followed. That’s very helpful.
It sounds like the “Maybe Later” button may not be triggering the expected action immediately, while the rightmost button forces a refresh that clears the notice. We will review the banner logic on our side to see why the dismiss action is not responding properly in some cases.
We appreciate you taking the time to investigate and share your findings. We’ll look into this and update if we identify the cause or release a fix.
Thanks again for your detailed feedback.
Hello @luboslives ,
Are you still facing the issue? We have tested in our system it’s working.Hi@johanlinder ,
Thanks for reaching out.
That message is not generated by our plugin and therefore won’t appear in Loco Translate for it. The string “Value must be greater than or equal to X” comes from WooCommerce itself and is shown by the browser when a number input field has a
minattribute that is not met.Since this notice is controlled by WooCommerce, it cannot be translated from our plugin. For guidance on translating or customizing this message, I recommend reaching out directly in the WooCommerce support forum:
https://ww.wp.xz.cn/support/plugin/woocommerce/
They’ll be best placed to advise on available options or workarounds for this.
Hope this clarifies things.
Thank you so much for the kind words and for taking the time to share your experience!
We’re really glad we could quickly resolve the issue for you and get everything back on track. Your feedback means a lot to our team and motivates us to keep improving both the product and the support experience.
If you ever need anything else, please don’t hesitate to reach out. We’re always here to help!