Fortunately to me, I found this plugin (https://ww.wp.xz.cn/plugins/widget-settings-importexport/) which exported and imported everything like a breeze. No errors, no worries.
I share this to others who could have the same problem.
Thanks!
Hi Marcelo,
Does anything unusual turn up in your debug.log file when importing and/or when accessing the Widgets screen?
Does the Widgets screen work again when deactivating all other plugins?
It sounds like there is a conflict either with one plugin or a combination of plugins and/or the settings of a specific widget or widgets. That’s a big list of suspects so if you can provide steps for me to recreate the issue on a fresh WordPress install then I should be able to figure out where the breakdown is.
Thank you.
Hi! sorry for the delay.
The other day I was really pissed off to migrate a website from staging to production ASAP. So, I couldnt mind enable debug.log to test; I needed a reliable solution, fast. Anyway, I’ll need to make a copy from production to staging and before trying to copy the entire database, I’ll give it a try to your plugin to let you know.
There are a lot of plugins used as widgets, so I would be wary on deactivate EVERYTHING just to try. And as I said originally, the problem is indeed the complexity of the widget list for this site. Almost 80 widgets, each one using almost 30 conditional rules from JetPack’s Widget Visibility.
I know it’s a hard to reproduce scenario because you should use woocommerce, load 2k products with an assigned preset of almost 300 categories, and then insert the dozens of layered filter widgets and add every visibility condition to show the correct filters in the correct categories. This thing with filters and conditions took me 2 days to accomplish. In fact, the WP Widgets Screen becomes super slow and switching positions of widgets by drag and drop may take up to 5 seconds in my 8 GB RAM computer… Yep, that complicated.
Probably your plugin is hitting some kind of limit in the way it export or import the data. Maybe a hardcoded limit in the amount of items to be queried? I don’t know. You should analyze the abovementioned plugin to see how they did it. It exported everything in seconds, and the json was imported incredibly fast. So fast that I thought it just failed 🙂
Hope you can find a solution. Best regards!
There are no hard-coded limits. If it’s a memory issue then debug.log may turn something up. Otherwise, I cannot efficiently debug something with such a complex configuration. If you can provide a reduced test case then I’ll see if I can confirm the issue and work on a fix.
ok, I’ll try to provide you a debug.log or access to a test setup.
best regards!
Hi Marcelo,
Could you test this issue with version 1.2? The newest version supports settings stored in multidimensional arrays which is how Jetpack’s Widget Visibility works.
I am going to consider this resolved as I have not had other reports of this since the update. Let me know if you do test this and find otherwise.
Hello Steven, I had no opportunities to test it again. So, I don’t know if it worked. If I find enought time to test it, I’ll let you know. 🙂
