ccbackus
Forum Replies Created
-
Forum: Plugins
In reply to: [Twenty20 Image Before-After] Critical Error in 1.7.4Success in my website as well. I updated to the latest version and the website is operating as expected. Thank you.
Forum: Plugins
In reply to: [Twenty20 Image Before-After] Critical Error in 1.7.4same problem for me. I turned off auto-update and will wait to see if another revision comes out.
Forum: Plugins
In reply to: [Contact Form 7] Everything is SPAMAs I enumerated my list, I realized I had two honeypot Plugins, and this evidently created a conflict.
I had:
Contact Form 7 Honeypot Plus
Honeypot for Contact Form 7.I removed Contact Form 7 Honeypot Plus, and forms are now being sent as expected.
I guess too much honey can be a bad thing…
Forum: Plugins
In reply to: [Easing Slider] Conflict with AutoptimizeThanks for your insight into this.
Forum: Plugins
In reply to: [Easing Slider] Conflict with AutoptimizeSure. I removed the exclusion. You’ll notice that the slider is gone, and the drop down menu which normally expands on hover no longer functions.
Forum: Plugins
In reply to: [Easing Slider] Conflict with AutoptimizeHere’s a screen shot to validate I pulled the right field:
Forum: Plugins
In reply to: [Easing Slider] Conflict with Autoptimizejs/jquery/jquery.js
Forum: Plugins
In reply to: [Easing Slider] Conflict with AutoptimizeYes, it’s https://www.unitedcarpetclean.com/
Forum: Plugins
In reply to: [Easing Slider] Conflict with AutoptimizeI was able to eliminate the conflict with the Revolution Slider, and Avada menu by adding “js/jquery/jquery.js” to the JS optimization exclusion list.
However, this allowed 100 blocking script resources, and 5 more blocking CSS resources. It dropped the PageSpeed score from 84 to 48 for mobile, and from 90 to 79 for desktop.
Is there some middle ground I can try to gain a speed advantage while still being able to use the Revolution slider and Avada menu tree?
I followed the directions on the support page referenced above for Comet Cache, and then I typed in Googlebot as an additional line item in the User-Agent Exclusions. This seemed to do the trick for me as it bypasses the cache for the Googlebot and has it pull a fresh image. Now the website looks right on my mobile phone (iPhone) and it passes the Google Mobile Friendly test.
Just realized this happened! Had to deactivate the Plug-In, and look for a new solution. bummer.