Jetpack Widget Visibility causing conflicts w/ 500 error

Thanks for the report!

I imported the widgets (with visibility settings in place) from another site (I’m replicating it locally) and then activated Jetpack afterward.

Could you give me more details as to how you imported the widgets from your other site, so I can try to reproduce the problem?

Thanks!

Hi Jeremy,

OK… I used this plugin to do my widget exporting/importing: https://www.ads-software.com/plugins/widget-importer-exporter/.

I can offer the widget export file for you to review, but we’ll need to chat away from the public support channel for this.

Thanks for the response!
-Robert

I’m not sure if this would be the issue but be aware that Widget Importer & Exporter had an issue in 1.0 relating to how data was imported. It was fixed in 1.0.1 so if you haven’t tried deleting the widgets, updating the plugin to 1.0.1, then re-importing the widgets with that version, it might be worth a shot. The data going in will be different even though the file you are importing is the same.

https://www.ads-software.com/plugins/widget-importer-exporter/
https://github.com/stevengliebe/widget-importer-exporter/releases

Hi Steven,

Thanks for this. I am running 1.0.1 already with the WI&E plugin, so I think it’s related to another issue.

I wonder if this has something to do with arrays of info on widget visibility already existing when Jetpack is activated, thus causing the errors. I can run Jetpack, but only with Widget Visibility disabled.

My next steps are to:

1. delete all the widgets,
2. activate widget visibility with no widgets in place
3. if no errors, rebuild all the widgets manually
4. test, and report back

I wish I knew more about where the widget visibility settings are being stored to do deeper, more specific troubleshooting on this.

Thanks again. I realize I’m probably an edge case on this stuff (importing widget data before activating Jetpack from a Jetpack-enabled blog).

-R

I wish I knew more about where the widget visibility settings are being stored to do deeper, more specific troubleshooting on this.

The widget conditions are stored in the wp_options table, within each widget’s settings. I’m afraid that creates some issues when using the Widget importer plugin, since the importer probably cannot recognize the additional information stored in the widget setting array. To solve the issue, I’m afraid you’ll have to delete the “conditions” values from all your widget settings arrays, in your database.