plugins that cannot be enabled should say the missing dependancy
Bug #406757 reported by
Lionel Dricot
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GTG |
Fix Released
|
High
|
Paulo Cabido | ||
Bug Description
Sometimes, a dependancy is not met to run a particular plugin.
In that case :
1) The plugin should be listed in the plugin preferences but disabled.
2) When the user try to enable it, he should receive a warning saying what are the missing dependancies.
Another solution would be to grey out the plugin so it cannot be enabled and add, in the description page of the plugin, a bold statement listing the missing dependancies.
| Changed in gtg: | |
| assignee: | nobody → Paulo Cabido (pcabido) |
| importance: | Undecided → High |
| milestone: | none → 0.2 |
| status: | New → Confirmed |
| tags: | added: plugins |
| Changed in gtg: | |
| status: | Confirmed → In Progress |
| Changed in gtg: | |
| status: | In Progress → Fix Committed |
| Changed in gtg: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
