This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.
This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.
Well you have scored a A+ yet again. Turns out that Wordfence Security was blocking the Ajax javascript from saving an iFrame in a widget as “potentially dangerous” which was revealed on the Firebug console when trying to save that widget. I set the Firewall to “learning mode,” saved the widget, and turned the firewall back on. There’s a better way which is to whitelist the action but I have not figured out how to do that.
This info is here for others who may stumble on this.
Thanks again Jason, as always.
Eric
Thanks for the fast response Jason, and it makes sense.
Eric
Ok, hang on – in my child theme (which is the same folder as before the update, no changes made) I renamed “header.php” to “header2.php” and that seems to have fixed it! Wondering why, but it’s possible there’s another method when doing a manual update with a child theme?
Anyway, false alarm for now…