Cookie Rocks
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Excluding a script from Delay JSThanks, Emre, that’s all we needed.
Ben, Cookie Rocks
Thanks for the quick answer. No need for a ticket then: Cookie Rocks now asks for the visitor’s country with a POST request, so the REST cache question no longer applies to us.
Ben, Cookie Rocks
One more, if you don’t mind: does the NitroPack service cache JSON responses, for example a /wp-json/ route called with GET, and does it honour Cache-Control: no-store?
Ben, Cookie Rocks
Thanks a lot, Lilly, that’s exactly what we needed: written only on scroll, plus Excluded URLs, Excluded Resources and data-nitro-exclude. Very clear.
Ben, Cookie Rocks
Thanks Andrés, that’s very clear.
Good to know the WooCommerce session is the default, and that the cookie only appears with a full-page cache or when the wcml_user_store_strategy filter asks for it. We’ll describe it that way, next to WooCommerce’s own session and cart cookies.
Ben
Hi Ernest, thanks for looking into it and for the background. We’ll keep the 30 days in our description for now and check again when 5.0 is out.
Rock on,
Ben
Hi @collizo4sky, thank you for the clear answer. We’ll note that the length is fixed for now, and add the ppress_device_cookie_lifetime filter to our description once the update is out.
Keep rocking,
Ben
Hi @abanobakram, thank you, that’s great news. Once the new version is out, we’ll test the Returning Visitor condition with consent given and refused, and describe it that way.
Keep rocking,
Ben
Thanks again for the clear answer. Cookie Rocks 2.11.7 now reads X-Sucuri-Country, and only for requests that come from your firewall’s published IP ranges, as you advised.
Ben, Cookie Rocks
Forum: Plugins
In reply to: [The Events Calendar] Click-to-load placeholder for the venue mapThanks, Darian, that was very helpful. Following your explanation, Cookie Rocks 2.11.7 holds the Google Maps API that Map view loads with jQuery.ajax until consent, and loads it right after, without a reload.
Rock on,
Ben, Cookie Rocks
Forum: Plugins
In reply to: [The Events Calendar] Click-to-load placeholder for the venue mapHi @d0153,
Thanks for the detailed questions, they helped us look closer. In the end we didn’t need a new hook. Cookie Rocks already holds the venue map iframe until consent. For maps drawn with the site’s own API key, version 2.11.6 holds embedded-map.js together with the Google Maps API and runs them in order after consent, so the map is drawn without a page reload. We describe the test with The Events Calendar 6.18.3.1 on our website, on the page about The Events Calendar.
One question: do the venue page and Map view in Events Calendar Pro use the same embedded-map.js?
And a small suggestion, only if it’s ever convenient: an exposed init function for embedded-map.js would make this easier for any consent tool.
Rock on,
Ben, Cookie Rocks
Forum: Plugins
In reply to: [Breeze Cache] Cloudways Varnish and a no-store plugin PHP fileHi @owaisalam,
Thanks again, that was very useful. We added it to our Cloudways page: https://cookierocks.com/solutions/cloudways/
Since Cookie Rocks 2.11.6, each geo.php request uses a unique address, so Varnish’s standard setup never serves one visitor’s country to another. We still recommend your URL exclusion for Cloudways sites, as a precaution.
Keep rolling,
Ben, Cookie Rocks
Forum: Plugins
In reply to: [Statify] statify__skip_tracking and visitors who refuseThanks, Stefan, that’s clear. Good to know statify__skip_tracking runs before every count, and that in JavaScript mode the request still goes out but nothing is stored. On our side, Cookie Rocks holds the statify-js script until the visitor accepts statistics, as our page says: https://cookierocks.com/solutions/statify/
Keep rocking,
Ben, Cookie Rocks
Forum: Plugins
In reply to: [Joinchat - Enhanced "click to chat"] Click events and Google or Meta tagsThanks a lot, that confirms what our test showed and matches our page: https://cookierocks.com/solutions/joinchat/ . Good to know the events only go through tags already on the page, when the visitor opens WhatsApp.
Rock on,
Ben, Cookie Rocks
Forum: Plugins
In reply to: [LiteSpeed Cache] QUIC.cloud: visitor country header to the originHi @qtwrk,
Thanks, that’s helpful. Today we don’t read any QUIC.cloud header: on a LiteSpeed server, Cookie Rocks reads the country set by the server’s own GeoIP module (GEOIP_COUNTRY_CODE). Our page: https://cookierocks.com/solutions/litespeed-cache/
Could you tell us the exact name of the country header the node sends? Is it the visitor’s country or the node’s? And can the origin check that it really comes from QUIC.cloud, for example with your published IP ranges?
Thanks for rocking with us,
Ben, Cookie Rocks