hades200082
Forum Replies Created
-
Forum: Plugins
In reply to: [jQuery Updater] jQuery Migrate 3.3.2.min.js missing in jQuery Updater 3.6.0Same issue here. Amazed that this wasn’t caught in pre-release testing.
Forum: Plugins
In reply to: [Async JavaScript] jQuery not defined error – WordPress 5.6Could you add native detection of the jQuery updater plugin too?
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Consent banner keeps popping upI’m having this issue also. I don’t have a live site yet as I’m developing locally, but it is really annoying that every page load requires to accept again.
I did notice that the “accept” creates complianz_ cookies with “path” equal to the page that the acceptance was given, rather than just “/” which would accept for the whole site.
This seems to be the main cause of the issue on my end as these extra cookies conflict with the ones set on the homepage and then the banner pops up again.
It’s always through the WordPress plugins screen.
Forum: Plugins
In reply to: [Flamingo] Flamingo makes CF7 submit very slowUpdate: We’ve swapped to using CFDB7 now as it doesn’t have this issue. I suspect the issue is that Flamingo is triggering edge-cache purging on each submission causing the process to be very slow.
Forum: Plugins
In reply to: [Flamingo] Flamingo makes CF7 submit very slow“The only difference between these two is one has Flamingo and one doesn’t.”
The other plugins should be irrelevant.
I’ve seen other threads mention speed issues with Flamingo when used on a host that uses edge-cache like Varnish. This site is hosted on Pantheon who do use edge cache.
Forum: Plugins
In reply to: [Flamingo] Flamingo makes CF7 submit very slowHi
The form in question is at https://www.parcelhub.co.uk/business-enquiry/
You can see it without Flamingo at https://test-parcelhub.pantheonsite.io/business-enquiry/
The only difference between these two is one has Flamingo and one doesn’t.
Forum: Plugins
In reply to: [Autoptimize] Defer CSSThanks for the swift reply… I noticed the subtle naming difference in GPSI just after posting.
One thing to note re your approach though…
using the onload attribute of the <link> tag causes the onload action to fire when the <link> tag has loaded… not when the page has loaded. This can cause it to be fired prior to the page load completing, resulting in a blocking resource still, especially on slower connection like mobile.
Could it be better to do it as follows… ?
1. Continue rendering the preload & noscript, but without an onload
2. Add a small async script tag to the footer, just before the closing body tag that looks for alllink[rel="preload"]
and swaps them torel="stylesheet"