- April 30, 2018 at 11:12 am #25379markskoultchiParticipant
I was going nuts trying to figure out why content was having trouble loading on my site’s pages. I’d visit the page and usually it require a hard refresh of the browser to get the page content to load.
I reached out to my hosting provider (Flywheel – they’re awesome), and they narrowed the problem down to what appears to be a caching conflict between their caching system the Quform caching system.
I’m including the email I received from them below, mostly for your benefit since they seem to have resolved the problem for me on my site by adding an exception for your plugin in their own caching system. However, can you tell me if you’ve come across this sort of problem and conflict before, and if there is something in the plugin settings I should be adjusting to avoid this problem on other sites I build when using Quform?
Here’s the note from Flywheel:
Thank you for the video! This is a _very_ odd one, and I can confirm that I’m seeing the same behaviour that you are. What’s odd is that if I visit the homepage using the ‘Back to homepage’ button, I see the following server request:
[30/Apr/2018:07:13:11 +0000] “GET /wp-admin/admin-ajax.php?action=quform_support_page_caching&token=OtOq3pNjHevgprBatkCF5Zp7dMHKNqlrN2yEABIm&forms%5B%5D=879dbc HTTP/1.1” 200 125 “https://www.jeanniebrooks.me/” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36” 6s6ue7x161
And I also see these console errors, which are the reason for the sections of the homepage not loading (jQuery/JS related errors; screenshot http://flywheel.link/2w3G1B1G2W2x):
Uncaught SyntaxError: Unexpected end of input
Uncaught TypeError: $(…).tooltip is not a function
at Object.UNCODE.utils (app.js?ver=1214063984:58)
at Object.UNCODE.init (app.js?ver=1214063984:5147)
Uncaught ReferenceError: Waypoint is not defined
When I visit the homepage directly, I don’t see any jQuery/Js errors (the page loads fine). What I see instead is:
[30/Apr/2018:07:14:42 +0000] “GET / HTTP/1.0” 200 85159 “https://www.jeanniebrooks.me/about-jeannie/” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36” 6s6ue7x161
[30/Apr/2018:07:22:57 +0000] “GET /wp-admin/admin-ajax.php?action=quform_support_page_caching&token=OtOq3pNjHevgprBatkCF5Zp7dMHKNqlrN2yEABIm&forms%5B%5D=879dbc HTTP/1.1” 200 125 “https://www.jeanniebrooks.me/” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36” 6s6ue7x161
The second request – as with the similar one above – is a call to some kind of admin-ajax related cache. It appears to be related to something called
quform_support_page_caching, which is [this](https://codecanyon.net/item/quform-wordpress-form-builder/706149) form builder plugin. What’s missing is the GET request to the homepage (aka
/) itself, so your suspicious that caching is related would appear to be correct — there’s some kind of odd conflict occurring between our caching layer and the theme’s Ajax functionality.
To try to help with that I’ve added a caching exception for the
quform_support_page_cachingstring, and haven’t yet been able to cause a return of the load problems described. Can you please retest and let me know if they persist for you?May 2, 2018 at 4:37 pm #25447
- You must be logged in to reply to this topic.