The code that powers the plugin was not written to take direct action over content in the website, so saying that it is “deleting” the widget is probably wrong, I believe you wanted to say “blocking” it which means that the widget is still there but the plugin is blocking its execution, if what you are saying that the plugin is in fact “deleting” the widget from the database then I am completely sure that it is not the plugin that is causing that because I know almost by memory all the code that is shipped with the public releases and there is nothing there that takes direct action to delete content from the database.
If you disable the plugin while you are adding the widget, then verify that it is working in the front site, then enable the plugin once again we will be sure of what is actually happening here. If the widget disappears after you re-enable the plugin then I suggest you to keep it disabled until a new public version is released with a patch that fixes the issue.
Sorry for that choice of syntax. “Blocking” is what I meant.
I will investigate the issue and mark this as resolved once is fixed, as you created this ticket you will be notified immediately when the patch is applied to the code, hopefully soon.
Marking as resolved; issue fixed with latest version of the code.
