Blogwithben

Thanks so much, Steven! I’ll pass this info along to my clients. You’ve been a huge help once again. Appreciate it!

Awesome! Thanks again for all your help!

Also, let me know if the thumbnail is too much. I’d be happy to change it. ??

Hey Steven,

I created a video tutorial outlining your steps to fix the issue. Feel free to share it with any other customers that come across this issue. Thanks again for all the help!

This is very helpful, Steven. Thanks again! I’m glad you guys like the videos as well. The Kale theme is probably my favorite WordPress theme and I know that it has helped A LOT of people start a food blog. I also appreciate you taking the time to answer my questions. Take care!

Thank you, Steven. Appreciate it! I’ll pass that support email address along. Is there an issue in the PHP that is causing the fatal error? I realize that every error is different and it would be hard to say, but I’m seeing a lot of client errors coming from the /welcome-page/class.welcomepage.php. Thanks again for your help!

Hi,

Me again. Yep, javascript error, but also a subdomain issue on my end. It has been resolved. Thanks!

I’m pretty sure it’s a javascript error, but I wanted to see if you were aware of any bugs before I dug any further. Thanks again!

I’m having the same issue with published pages and posts. If I try to preview the changes, they won’t show up in the preview environment. I either have to unpublish the page/post or revert back to the classic editor.

I’ve tested this on multiple sites using different themes, different web hosts, and different plugins. I’ve also disabled each plugin one by one with no luck. Additionally, my sites are all using the most up-to-date version of PHP.

Hi,

The Frizzly plugin is causing the issue. You can restore your site by renaming the frizzly plugin file to something like “frizzly-temp”.

Here is a video that shows you how to do it if you’re using Cpanel. Hope this helps!

• This reply was modified 7 years, 10 months ago by Blogwithben.

Hi Lindsey,

I recently had the same issue and you can fix it by renaming the frizzly file to something like frizzly-temp. That will deactivate the plugin and you should be able to access your site again. This video shows you how to do it if you’re using Cpanel. Hope this helps!