#114
  • Created on
    2010-02-11 14:33
  • Reported by
    nick_ramsay
  • Status
    Fixed
  • Priority
    Low (4)
  • Assigned to
    nick_ramsay
  • Milestone
    1.5 - current
  • Plan Level
    -
  • Due Date
    -

Attachments

Widgets don't get re-enabled when plugin reactivated

When you deactivate and reactivate (or upgrade) a plugin, it’s widget is disabled so you have to go to Widgets and re-enable it.

Rather than the Widget class disable a widget when its plugin is deactivated, it might be better to "gray it out" and hide it from view, but otherwise keep its "enabled" status as true. Then when the plugin is active again, the widget is shown again. Note that this is different to uninstalling a plugin, which completely removes the widget.... which leads to another problem: Upgrading a plugin won't re-enable its widget because the upgrade process first uninstalls the plugin.
User picture
  on 2010-02-11 14:34 *
By nick_ramsay
Related association with ticket #103 was added
User picture
  on 2010-02-17 14:40 *
By nick_ramsay
Milestone changed from RC1 to 1.1
Updating tickets (#96, #98, #104, #110, #113, #114, #115, #99)
User picture
  on 2010-02-22 02:54 *
By nick_ramsay
Milestone changed from 1.1 to 1.2
Updating tickets (#114, #96, #98, #121)
User picture
  on 2010-03-07 13:26 *
By nick_ramsay
Status changed from New to Accepted
I gave this a really good go, but to no avail. The biggest problem is that when you turn off all the plugins, the Widgets plugin itself gets turned off. That, combined with cached data about which plugins are enabled or not, makes it all very tricky.

The best solution would be to include Widget Management by default in Hotaru, just like Plugin Management, so that's the new plan if there are no objections. I'll aim for Hotaru 1.2 to do it.
User picture
  on 2010-05-31 00:17 *
By nick_ramsay
Status changed from Accepted to Test
This appears to be magically fixed in Hotaru 1.3. There were some issues with detecting whether a widget's plugin was active or not after reactivating because of caching. Fixing that seems to have solved this problem. Marked as "ready to test".
User picture
  on 2010-11-26 11:06 *
By
Are we done with testing this ?
User picture
  on 2010-11-26 11:21 *
By
Milestone changed from 1.2 to 1.5
User picture
  on 2010-11-26 11:30 *
By nick_ramsay
Status changed from Test to Fixed