Opened 14 years ago
Last modified 14 years ago
#10150 new enhancement
Plugin installation errors should be shown on admin page
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | admin/web | Version: | |
Severity: | normal | Keywords: | bitesized |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
The last few times I've tried to install a plugin, I've made some sort of stupid mistake. Either I got an egg for the wrong version of Python, or I've right-click copied what I thought was the url from trac-hacks, but was actually the html page with the link to the attached egg. (Then I wget the "egg" and I'm none the wiser until I investigate it).
And when I put it in the plugins directory and reload trac… nothing happens. I have to do the investigation myself. It would be nice if, whatever it is that makes trac decide to reject the egg, would be displayed in the same screen as the list of plugins.
Thanks!
Attachments (0)
Change History (3)
comment:1 by , 14 years ago
Keywords: | bitesized added |
---|---|
Milestone: | → next-major-0.1X |
comment:2 by , 14 years ago
Interestingly, I have logging set to DEBUG and I don't see anything about it, at least searching by the name of the egg file. In this case, the error was that it was an html file instead of an actual egg.
comment:3 by , 14 years ago
Right, we log failures while loading modules from plugins, but we don't seem to even try loading invalid plugins (like a bad egg). Actually, pkg_resources
seems to do some filtering there, so that we don't even get to see them.
So let's say that it's a bit more complicated than expected :)
It should show up in the log, but it would indeed be nicer to show it on the "Plugins" page. It shouldn't be all too complicated either: keep a list of errors when loading plugins, and display that list nicely on the admin page.