WebePc Gianluca Molina
Forum Replies Created
-
I’m out of the office at the moment, but I’ll check as soon as I get back.In any case, other WooCommerce customers are experiencing the same issue.
Of course, but doing so would mean that all products would be without cache and pages would open more slowly…Can’t you exclude only the buttons from the caching system?
That’s what I had already done, and in fact they work perfectly on the shopping cart page at checkout, but I wanted them to work on individual products as well.
Opppsss sorry!
I opened a new ticket in the correct placeDespite having excluded the URL in Google Merchant, the error continues to appear
Limited numberIt is as if it did not recognize the quantity of products
Ok I added the URL in the exclusions of Litespeed
This is the configuration:

I confirm the problem
I confirm, as indicated in the problem solved and …


Hello Antonio,
Thanks again for your support.
Just a quick follow-up: after a lot of testing (and a bit of frustration), I’ve finally found the real cause behind the hamburger menu breaking on mobile.
It wasn’t Elementor or any of the related integrations — it was actually the plugin YotuWP – YouTube Gallery.
What’s really odd is the behavior:
- If the user refused all cookies: the hamburger menu worked fine.
- If the user accepted all cookies (including marketing): the menu stopped working after a few seconds.
A bit counterintuitive, right?
Usually, consent enables features — in this case, it broke one.I’ve now simply disabled YotuWP and moved on — problem solved, amen 😅
But I thought it was worth sharing with you in case this pattern shows up elsewhere. It might save someone else hours of debugging.Thanks again and keep up the great work with Complianz.
Thanks for your reply.
I understand the policy about commercial support, but this question touches a very basic GDPR requirement, which affects any user in the EU — including those using the free version.In my opinion, if the plugin cannot be used in a GDPR-compliant way without purchasing the pro version, it should be clearly stated in the public documentation.GDPR compliance is not an optional “feature” — it’s a legal obligation.
- This reply was modified 1 year ago by WebePc Gianluca Molina.
OK thank you!
Forum: Themes and Templates
In reply to: [ColorMag] Elementor 3.26 > fatal errorHi
Thanks for the update, I would like to point out that with the latest update there was a CSS problem, the title and background took on a different color
Look: giurisprudenzapenale.comOk but if I disable for that type of “post” Elementor and return the standard editor (Gutenberg) I would expect that if I go to edit the page with the standard editor then I would see the content changed not that it would “force” remain the Elementor content that should be disabled I am talking about websites where Elementor is used only for content so no header, footer, etc.
I explain in detail
During the development of a new site a client started writing articles, simple text.
Instead of using the WordPress editor he clicked, out of habit, on “edit with Elementor.”Considering that the articles will only be featured image + simple text I disabled Elementor for that type of post (articles)
On the backend, opening the articles that had been made with Elementor now appeared properly editable with Gutenberg.
But in the frontend the content was not updated, it continued to retain the initial version created with Elementor.I had to re-enable Elementor for that type of post, go into the articles and click on the appropriate “return to standard editor” button
But what could it be? I mean I’m sorry to leave Cloudflare disabled