Tagged: enfold update
March 9, 2020 at 3:04 am #1191355
I’m not very savvy when it comes to code so bare with this explanation. As the title suggests, Updating Enfold has killed code within our site.
To give a rundown, we use code from another company who look after our vehicle inventory & to display our vehicles on our site.
Everything works perfectly on 220.127.116.11. but once updating to 4.7.3 things stop working at all.
It varies from super slow load speeds to not loading at all. sometimes it works but then if you leave the page and go back it stops working.
This is only on our VEHICLES page. NOT the VEHICLES DETAIL page.
The only thing I’ve changed between the working site and the staging site is the update.
The website which works is: https://www.4guys.co.nz/vehicles/
The staging which does not is: https://fearless-berry.flywheelstaging.com/vehicles/
Any ideas at all? This is the code we use inside the ‘Code Block’
config.ID = “75”;
config.Framework = “css-search-percentage”;
config.Theme = “”;
config.PercentageFrame = true;
config.DetailUrl = “vehicle-details/”;
March 9, 2020 at 11:32 am #1191429
- This topic was modified 1 year, 7 months ago by 4Guys Autobarn.
Hey 4Guys Autobarn,
When I check your site I see the error:
Uncaught TypeError: Cannot read property 'insertBefore' of null at a.yepnope.injectJs modernizr.min.js
Search engine failed to load. Refresh page or try again. Cause: Run is not defined
I recommend ensuring that Enfold Theme Options > Performance > Load jQuery in your footer in not enabled and that no other caching or minifying plugins are loading your jQuery in the footer.
Otherwise, it looks like a issue with your script.
MikeMarch 10, 2020 at 4:14 am #1191686
Thanks for the reply Mike,
Do these errors appear on both sites? Sorry, I’m limited in my knowledge of all this.
Load JQuery in the footer was NOT enabled and no other caching plugin is installed.
Again, forgive my limited knowledge. But would there be a reason why the script would work on an older version of Enfold and not the updated version?March 11, 2020 at 1:26 pm #1192261
The error doesn’t seem to be occurring on both sites. The error could be a curly quote in the code, or in a different script.
Please try disabling your plugins and checking that your script was copied correctly from your other vendor.
Otherwise, can we have an admin login to your stagging site and try disabling things to try to isolate the issue.
MikeMarch 11, 2020 at 11:51 pm #1192434
Ok so I’ve redone the staging of our main site and the ONLY thing I’ve changed is updated WordPress.
I’ve added the admin login to the stagging site bellow. Cheers!March 13, 2020 at 10:37 am #1192852
You must be logged in to reply to this topic.