Archived topic
Blog setting not working
7 replies · Started by Brian on June 26, 2021
Hi,
I'm not sure if I have multiple issues or one thing is causing all the problems.
Firstly it's on all the blog (archive) style pages. The main issue is infinite scroll isn't triggering. But side issues are the boxes that contain the posts information seem to be different sizes which is causing display issues (sometimes there are 2 columns and other times 1). And the featured post should also have the text displayed on the side of the image and not under it.
Thanks for any help
Hi there,
if you right click and inspect the site where the infinite scroll is not working you will see there are a few Red errors in the Console tab.
Two of which are named: Uncaught SyntaxError: Unexpected token '<'
Generally that means there is either a broken scripts somewhere or a 400 error where an essential script cannot be loaded.
Which leads to the next errors in the console which is a failed requests to the amazon servers and then google servers.
It could be a simple caching issue - ie. clear and plugin or server caches - OR it could mean a bad script somewhere
Thanks. Clearing the server cache didn't fix the issue.
I guess there is no easy way to know where the bad script is. Is it a case of having to delete and reinstall all my plugins? I have WP Rocket which I had set to minify JavaScript files, do you think this could be the problem.
I would begin by disabling WP Rocket - as yes minifying JS can cause this kind of issue.
With it disabled re-test the the site. If it works then try re-enabling it with the minify disabled.
Hi, I've still not been able to get this to work. I have even set up a staging environment (sent in private info) and deleted all plugins (except GP Premium), all custom CSS and elements and still the infinite scroll and equal-sized blog boxes don't work. Could you please have another look?
Are all plugins except GP Premium disabled currently?
I'm still seeing some console errors here:
https://www.screencast.com/t/RWUYNlr6Y
Any chance you can check with Kinsta's support team to see if they have any ideas?
Yeah, on staging I have deleted all plugins other than GP Premium. I am guessing the console error with /?var=2.0.2 is cos the edition of GP Premium I have is 2.0.2 (I know nothing of this kind of thing) but it seems like the css file located at https://staging-goshindigcom.kinsta.cloud/wp-content/plugins/gp-premium/blog/functions/css/style.min.css?ver=2.0.2 is getting redirected to the location in the console error.
I'll ask Kinsta support also if they have any ideas. Thanks
...but it seems like the css file located at https://staging-goshindigcom.kinsta.cloud/wp-content/plugins/gp-premium/blog/functions/css/style.min.css?ver=2.0.2 is getting redirected to the location in the console error.
Yeah this one is particularly strange. When we go to that URL, what we should see is the contents of the stylesheet instead of getting redirected to /?ver=2.0.2
If you have one, it may be worth checking for any child theme's functions.php if they have any php snippets that does this.
Let us know how it goes. :D
