#4971 closed defect (fixed)
NeverNotifyUpdater plugin wrecked my trac!
Reported by: | Chris Carr | Owned by: | Russ Tyndall |
---|---|---|---|
Priority: | normal | Component: | NeverNotifyUpdaterPlugin |
Severity: | critical | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
I downloaded the 0.11 version of the NeverNotifyUpdater plugin. I went to Admin->Plugins on my trac, and attempted to install it by pointing it at the "setup.py" file and clicking Install. I have never installed a plugin before, so I was just doing what seemed obvious.
Now my entire trac is broken - even after restarting apache.
Surely trac should be more resilient than that?
Grateful for any tips. If this really is a vulnerability (to ignorance) in Trac, I will happily file a ticket at trac.edgewall.org
Attachments (0)
Change History (3)
comment:1 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 follow-up: 3 Changed 16 years ago by
Just fyi: as noted in the text near that box, it expects you to point it at a .egg file rather than the setup.py file. You can get an egg from the setup.py by typing something like: python setup.py bdist_egg into a command line.
Also you might want to take a glance at: http://trac.edgewall.org/wiki/TracPlugins
comment:3 Changed 16 years ago by
Replying to bobbysmith007:
Just fyi: as noted in the text near that box, it expects you to point it at a .egg file rather than the setup.py file. You can get an egg from the setup.py by typing something like: python setup.py bdist_egg into a command line.
Also you might want to take a glance at: http://trac.edgewall.org/wiki/TracPlugins
Thanks - yes, I've got it installed and working now. I had never heard of a "python egg" before, so I didn't realise it expected a .egg file.
Btw, is it supposed to show up in Admin->Plugins? There's no trace of it, though it is definitely working! I just wondered.
Never mind. I worked out that all I had to do was remove setup.py and setup.pyc from the plugins dir and then restart apache.