Community
Participate
Working Groups
1. Go to the Plugins page 2. Install some plugin that provides one or more services, and is hosted at some URL you control. (I used a plugin hosted from an inner site). 3. Make a change to the plugin -- eg. add some additional service properties. 4. Go back to the plugins page, click the "Reload" link on the Orion toolbar. 5. Expected to see the changed version of the plugin, but it remains the same. If you Refresh the page in your browser after step 3, it works as expected.
Jeez a feature is not even in for one day and people are already complaining ;) I think this usecase is important at dev time but not typical in production so think hitting F5 is ok for 0.2. What's happening here is our call to load the plugin is being ignored the second time because the plugin is marked as loaded already. What we need to do something like a force load command on the plugin.
I also noticed that if you install a plugin that fails (due to a programming error), then fix the error and try to install it again, it will fail again until you reload the page. Sounds like the same issue, so I'll just mention it here rather than open a new bug
This is more an implementation note and reminder to write tests for me: Plugin states -- "uninstalled", "installed", "enabled", "loaded" Plugin event types -- "uninstalled", "installed", enabled", "disabled", "loaded", "unloaded", "updated"
Fixed in Master
