Dave

Thanks. Is there a way to do this without needing the pro plugin?

Or, at least test it works with my configuration before committing to the pro edition?

• This reply was modified 2 years, 4 months ago by Dave.

Thank you for a comprehensive answer.

In this instance, I require a solution to work with Google’s built-in consent manager (‘Consent Settings’). The proposed solution above appears to rely on creating on a separate consent event that is triggered. It looks like it would be handy elsewhere, but unfortunately this isn’t workable for my current project.

I’ve added this basic template by Google. From testing, it looks to bridge Complianz and GTM perfectly, except for it requires cookie values of ‘granted’ and ‘denied’. With two minor text changes, the built-in consent triggers inside GTM would work seamlessly.

Are the ‘accept’/’deny’ cookie values in Complianz editable or at least filterable? Can I use something like Say What? to translate these to custom values? Or, more preferably, a custom add_filter function perhaps?

Thanks. I’d rather not disable the validation for all forms, just the one set up like this. Is there a way to disable validation on a specific form id?

Do you know roughly how long that would take?

Thanks. I couldn’t spot anything unusual in the HTML so decided to compare the generated JS files. It turns out, there was a line of inline code that creates a unique hash for each page view, and this triggered the generation of a new JS file for every page view. Excluding inline JS from minification solved my problem here.

I can’t try it on the client’s site but have tried it another of my one with the same configuration (CSS and JS optimised to the max, image optimisations, lazy load, etc.).

V3.6.4 scored 41. V4.1-rc8 scored 42 in web.dev, with Guest Mode enabled.

Nitropack is clearly doing something that Litespeed does not, and all I can see from looking at the source code of an optimised site is that it preloads all internal and external JS, CSS and font requests, and somehow delays the running of all JS until the site is loaded. The reports of a Nitropack-optimised site in GTmetrix don’t show jQuery for example, yet it loads on the front-end. So, by the looks of things, JS is loaded after the page has rendered and after it has been scored by GT and Google.

+1. Logging in Flamingo. Running on a LiteSpeed server. All plugins and WP are up-to-date and not had this problem before. It started in v7 5.4.

Every lead saves between 3 and 6 times, with the same timestamps and data.

@wpmudevsupport12 I’ve set the timeout and max execution time as 30s, and server load at 10. Both ‘Run continuously while the Dashboard is open’ and ‘Run hourly in the background’ is checked, so I wonder if this is spawning multiple instances. I have a habit of opening multiple tabs (dashboard, posts, current post editor, and preview) so would each tab likely trigger multiple instances of the checker?

I checked with the host and they blamed a cURL fault. They fixed it but they said the plugin is using far too many SSL connections and have advised uninstalling it.

Is there a way to throttle the checking process to cap it to a sensible limit? My understanding is that it checked on link at a time in the queue but my host seems to suggest otherwise.

I should add the status listed is ‘Unknown Error’ and the HTTP response code is 0.

Thanks.

It also applies to this line too:

<div class="wpcf7-response-output" role="alert" aria-hidden="true" style=""></div>

@mrhuynhanh The way I’ve got my setup is to disable auto webp generation in Litespeed, and I manually trigger it once I’ve renamed all my images using Renamer.

@tigroumeow I’ve contacted you with subject ‘Broken Images After Renaming’.

Many thanks for your help.

I turned logging on @tigroumeow .

Loading the media library didn’t trigger any logged events.

I uploaded an image. No events logged.

I edited the image title/alt via the Media Library > Edit panel. This triggered a ‘Event: Save Attachment’ log, but the file didn’t rename as expected. It continued to have the same ugly filename as uploaded.

No console errors throughout this process.