GaranLabs
Forum Replies Created
-
Hi @ucsendre,
Thank you for this — really made our day.
We’re really glad the setup went smoothly and that the localisation just worked without any extra steps on your end. It’s especially nice to hear the customisation options fit what you needed — feedback like this helps us understand what’s actually useful to the people using the plugin day to day.
Also glad the support team came through for you quickly. We try to actually be helpful when someone reaches out, not just fast — so it’s nice to hear both landed.
Thanks again for writing this. It genuinely helps.
— The GaranLabs Team
Hi @razvang95,
Greetings from GaranLabs!
Thank you so much for the kind words — we’re really glad to hear the setup and settings felt straightforward!
Thanks also for flagging the issue with your custom WooCommerce product page template. You’re right that the notice relies on the default template hook, so a custom template can sometimes skip it — and we’re glad the manual shortcode got it working for you. We’ll look into making the shortcode option more visible in our documentation for users with custom templates, so others run into this less.
Thanks again for taking the time to leave a review — it really helps us improve the plugin!
— The GaranLabs Team
Hi @ucsendre
Thank you for your kind words and for the detailed report. The environment details and stack trace were very helpful.
What we found so far
The error in the log (“Cannot use output buffering in output buffering display handlers”) is not the original error. Since version 6.9, WordPress processes the whole finished page at the end of each request. If another error happens during that step, PHP can’t display it and shows this message instead, so the underlying cause is hidden.
Our main suspect is that the page is using more memory than the 256 MB limit. The full GARAN label is a fairly detailed graphic. On variable products the plugin currently includes a copy of it for every variation, so a product with many variations can make the page very large. That would explain why only this one product is affected, only when GARAN is enabled, while [eu_guarantee_notice] works fine on the same page.
Could you help us confirm this?
- Is this a variable product? If so, roughly how many variations does it have?
- Could you temporarily raise the memory limit in wp-config.php and check whether the error goes away?
define( ‘WP_MEMORY_LIMIT’, ‘512M’ );
(If your host enforces a lower PHP memory_limit, this may need to be raised in the hosting panel as well.) - If possible, open the product page’s source (Ctrl+U) and tell us roughly how many times “eggl-widget–garan” appears.