-
Posts
-
Hi,
Pretty much what the topic says. For some reason I have to update Enfold every time using SFTP, it’s a pain but it works.
Today I downloaded/uploaded the latest update and it caused a Critical Error on the site. After disabling plugins and not solving the problem I had to put back V4.8.8.1 which brought the site back. I usually save the previous version in case of situations like this.The homepage loaded fine, but when clicking any of the links in the main menu took me to the “There has been a critical error…” message.
I am using a child theme, which has some custom PHP. You can see this history of that here, would anything that thread refers to be causing it?I’ve included the URL in the private content, but I’m not sure it will be of any use to you.
Cheers
JHey jonrouse,
Your site is blocking access on my end, but I’m assuming that you have restored a backup and that your site is working as it should now? Do you have server error logs which we could have a look at?
If you want to rule out your custom code, then you can simply activate the parent theme to see what happens then.
Best regards,
RikardHi Rikard,
Thanks for getting back to me. I’m not sure why you’re blocked, but hopefully I can explain the situation.There is a functions.php in the child theme folder along with a JS and Shortcodes folder. Inside the shortcodes folder is “av-helper-slideshow.php”.
I noticed on your latest release notes it says:deprecated: renamed ../framework/avia_shortcodes to ../framework/legacy_avia_shortcodes – files no longer loaded
And wonder if this is why I am seeing the problem.
There’s a lot to read on the link I sent, but the function basically changes the size of a full width slider when the browser is 1500px wide and wider.
I built this site a lot time ago, and there are new features within enfold which would do the same job. For example, to place the image in a colour section and set it to be 50% browser height.As this is the second time this had happened, I get the feeling you’re constantly improving the theme and it would be a mistake to rely on legacy code.
So rebuilding these elements seems like the best way forward for the long term.I just need to know what to remove from the child theme to disable this functionality!
Hi,
Thanks for the update and info. Would you be able to copy the site to a staging area first of all? It would be the safest option, unless you want to experiment with your live site. If you want to use your site live site, then you can simply remove all your customisations, then add them back one by one, to see which one you need, and what is causing problems on the site. Your child theme files might have to be updated as well, you can do that by copying the content of the parent theme files to the same file in the child, then add your customisations back in after that.
Best regards,
RikardThanks Rikard.
I’m currently replacing the full width sliders with 50%vh colour sections.
We designed and built the site, then it was given to another company to maintain, and a year later the maintenance came back to us. In that time the other company made some changes, like adding ACF – which I have limited experience with. Nikko helped me out last year and added “function_parallel_custom_theme_scripts”. Plus some secure php. So there is quite a lot of stuff in the child theme!I’ll make the changes and report back to you.
- You must be logged in to reply to this topic.