Crash with Genesis 2.2.7 update with Genesis Sandbox Featured Content Widget

I resolved this by deactivating the plugin, updating to Genesis 2.2.7 and then reactivating the plugin. I also plan to stop using it shortly anyway…

Thanks for this! Was having this same issue.

Hi @metaliz

I reached out to Genesis creators CopyBlogger via their support form and they tested it with (probably a Vanilla 2.2.X + Dynamik + this plugin) and said they had no issues. I re-downloaded the latest version of this plugin and then tried the upgrade and again it crashed. I then deactivated this and then upgraded but I then had a crash with an upgrade of a very standard plugin a few days later (think it was Yoast but no longer 100% sure). I reverted (thank god for backups) this then crashed the whole back-end so I reverted back to a pre Genesis 2.2.7 and have NOT upgraded since and have been staying at 2.2.6 after several crashes on updates of plugins.
It may well be an issue on my set-up each of us has modified small things at a minimum, but I felt that Copyblogger were very hasty to dismiss this issue…
(You can tell I’m not too impressed ??

Good to know! That information is very helpful. I am working on a multisite setup with about 200 sites and a good number of plugins. I deactivated sandbox plugin then updated Genesis to 2.2.7 and it worked fine, but now just noticed that clicking the “Customize” link from the WP Admin bar throws an error related to the featured content widget again – specifically, Call to undefined function genesis_get_option().

Anyway, I’m not too impressed either, back to Genesis 2.2.6 I go!

Damn, what you just said made me realise that I am not sure that I told them that it was a multisite set-up so this may be one of the factors that differentiates us and may not have allowed them to replicate the error when they tested it. I’ll respond to them and ask them to make sure that they did use a multisite and in my case with different languages…

Also multisite, and just upgraded to Genesis 2.2.7 and also had to deactivate this plugin ??

Yes it’s such a pity because the plugin has been awesome over the years and I think it may only need a slight update of the code but I don’t think it is monitored much any more…