Widget Selection Behavior makes it almost unusable

Ran into this before…

Solving it is just a little change in behavior:

While fiddling about I found that it will work, when you do it like click & drag. So click the dropdown arrow and keep the mousebutton pressed and then release it after the desired option is highlighted.

The dropdown for “Order By” (title, parent, etc.) does not need this behavior.. there you can just click and then click again to select. In fact after clicking to open the dropdown, it will show you the list and does not close until you click it again (or anywhere next to it).

@nick have you abandoned this plugin? as there are never replies or updates…

Thanks, Webtauras. That site launched months ago. I couldn’t wait to find out if Nick was still supporting it.

If the development had had a larger budget, I would have dived into the code and fixed it myself but the customer didn’t want to pay for that level of service and was willing to work with it as-is.

This issue was reported various time and I think was never took in charge from the developer. It’s really a pain, since it makes the plugin almost unusable. :/

At the time this issue came to light for me (March), I opened a ticket at Genesis, and they told me to report the issue to the WordPress forum. It seems clear to me that this plugin is no longer being supported and I do not recommend its use anymore because it is not usable.

In the next weeks we will try to fix it on github, since the original author seems completely dropped support.

Bless your heart! I was in too much of a hurry to write my own plugin at the time the StudioPress support people suggested this one.

I think it failed with one of the WordPress upgrades, the one that affected how plugins interacted with the database, if that makes any sense to you.

@franceso Hope you can fix it. I would be very grateful!

The issue is caused by a conflict on the class widget-control-save which is used also by WP code. I suppose this was intentional in the beginning but probably the WP behavior has changed in the recent versions, causing the issue.

Quick fix:
Edit the plugin’s widget.php file and perform a search / replace:

Find: widget-control-save

Replace: widget-control-save-custom (or whatever you prefer)

(it appears twice in the code)

Hi Marco, thanks for the fix. Just tested on one site and it looks like it works now..

Thanks Marco! I requested to implement the fix to the original author via Twitter. Hope he would consider it. Elsewere I second the option to fork the plugin.

Marco, thanks for the fix.

Thank you so much for this fix. This has been driving me nuts!

Actually that was a bust because the plugin now affects the CSS on my homepage. Back to the drawing board.

@marco – Thanks! This has been driving me insane forever!