zeichner8

Thanks for the quick response!

I tried to activate different third-party themes (aThemes Sydney Pro ver 1.37, to be specific), along with the default WP themes with no luck, so it doesn’t appear to be a theme issue. I also deactivated some of the recent plugins that were widget-related to see if that made a difference, but still no change and it remained looking like a jQuery issue since the widgets still couldn’t be dragged nor opened.

So, I figured it had to be in the database somewhere since that was the only area unchecked. After uninstalling the plugin and deleting it, I found a record related to it in the database that contained some serialization code. I didn’t delete the record, but I did revert the database to a backup version that I had just before the plugin installation and everything came back to normal (a good reminder to everyone to backup the database before any plugin installation… the 30 seconds of time with phpMyAdmin can save hours of work). I can’t remember what the value was, unfortunately, but after the uninstallation and deletion of the plugin, I searched for “amr” in the database and found the lingering record. Hopefully, it’s something that you can dig into a little bit and find a solution for, as well, since the plugin looks pretty awesome and could definitely a lot of folks like myself in the future.

Thank you again!

Hi Anmari,

Thank you for the quick reply, but I’m thinking that is has to do with something related to the installation and activation of the plugin. The widget area was working perfectly immediately prior to the installation and activation of the plugin, so it almost seems to be related. I’ve deactivated and uninstalled the plugin to no avail, so I’m kind of at a loss as to what happened. I do believe that it had something to do with a jQuery conflict, so maybe it has to do with another plugin that currently active, but I didn’t have any issues until the shortcode any widget plugin was installed. Regardless, I’ll deactivate the other installed plugins one by one to see if I can pinpoint the problem, but if it persists, I’ll let you know.

Thanks again!