I've been informed by a couple users that this plugin clashes with one of mine, the Custom Meta Widget. Your plugin inserts HTML inputs using the namespace of whatever widget it is modifying instead of using its own namespace. With a large number of very simply titled options names, this plugin has a huge potential for breaking a large number of widget based plugins.
It would be a best practice for you to append your own plugin's namespace to these HTML input's names and would probably fix half the support questions here. When you're modifying other authors' widgets in ways they can't predict, it's up to you to make sure those changes aren't breaking things. Using '
displaywidgets-login' instead of '
login' as an option name means you won't break every single widget that happens to have a login option.
I'd be happy to help you make the necessary changes if you'd like. Thanks.