Opened 19 years ago
Closed 12 years ago
#110 closed defect (wontfix)
Plugin does not show
Reported by: | Owned by: | brucec | |
---|---|---|---|
Priority: | normal | Component: | GalleryPlugin |
Severity: | normal | Keywords: | |
Cc: | webkontakt@… | Trac Release: | 0.8 |
Description
Maybe I am lacking some configuration (there is no documentation yet), but after checking out the sources, doing "python setup.py install" and having the egg included, the plugin does not show itself in my trac environment, neither in the menu nor within the WebAdmin plugin list.
Maybe it's just a matter of documentation...
Attachments (0)
Change History (14)
comment:1 Changed 19 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 Changed 19 years ago by
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Closing this ticket as invalid with a RTFM is a bit too easy, IHMO. I would love to write an email to the author (if any mail address was given), but actually creating tickets is the only way to give the feedback, which is said to be welcome.
What is definitely missing is the name of the component to enable. Without that information, it is practically impossible to use the plugin. And, as I understood it, any plugin egg included in the site-packages directory should show up in WebAdmin - but the gallery does not. What I am experiencing is that the plugin does not work.
I would very much appreciate if you could give me any mail address for further inquiries. I don't need an open ticket.
comment:3 Changed 19 years ago by
From the documentation i referred to, "The name of the option is the Python package of the plugin.". After looking at the gallery plugin source I see the package is named "gallery", so putting the following in your trac.ini should enable it:
[components] gallery.* = enabled
The documentation also states that global plugins are not picked up automatically: "Unlike plugins installed per-environment, you'll have to explicitly enable globally installed plugins via trac.ini.".
This should probably be in the documentation for the plugin, but the Trac documentation does mention how to find the package name without the documentation.
Also, I do not have the author's E-Mail address and so can not provide it. Tickets are fine.
comment:4 Changed 19 years ago by
Of course I tried to guess the package name before, from my trac.ini:
gallery.* = enabled
No typo. However, there is no effect.
My box is a Debian stable, with Trac 0.9.2 and Python 2.3.
comment:5 Changed 19 years ago by
Furthermore, it does not seem to be true that per-environment installed plugins don't appear in WebAdmin. I installed another one just now, and it appears without any changes in trac.ini.
Does it help to upload the generated gallery admin python egg?
comment:6 Changed 19 years ago by
I tried this myself and the reason it was not working for me is that it requires the PIL module. After installing this it still had issues but YMMV. I had to enable Trac logging in order to find this out.
Quoting from the documentation: you'll have to explicitly enable globally installed plugins via trac.ini. This does not mention per-environment plugins.
BTW, the author's E-Mail address is in the source code, as it seems he is not looking at the tickets.
comment:7 Changed 19 years ago by
Oops, I wrote nonsense above. I wanted to say: "Furthermore, it does not seem to be true that globally installed plugins don't appear in WebAdmin".
comment:8 Changed 19 years ago by
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
I'll close this ticket, assuming you chase it up with the author via E-Mail. Maybe you could ask him to subscribe to the RSS feed for his tickets? ;)
comment:9 Changed 19 years ago by
Alternatively you could tell him about this ticket, and re-open it. I think the issues are:
- Dependency on PIL is not documented
trac-admin <env> upgrade
does not work? It did not seem to write the schema version to the system table?
comment:10 Changed 19 years ago by
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
I'll reopen this ticket so the issues stay tracked.
comment:11 Changed 19 years ago by
making a somewhat complex plugin without documentation is nonsense. seriously.
comment:12 Changed 18 years ago by
Trac Release: | → 0.8 |
---|
I'm running into a similar problem... I built the egg from svn, installed it into my project, and Trac doesn't seem to say anything about it... However, there is some interesting output in my Trac logs:
11:53:53 Trac[loader] DEBUG: Loading plugin galleryplugin from /var/trac/precursors/plugins/GalleryPlugin-0.1-py2.4.egg 11:53:53 Trac[loader] ERROR: Component module gallery not found Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/trac/loader.py", line 42, in load_module module = __import__(name) File "build/bdist.linux-i686/egg/gallery/__init__.py", line 1, in ? File "build/bdist.linux-i686/egg/gallery/web_ui.py", line 26, in ? File "build/bdist.linux-i686/egg/gallery/api.py", line 20, in ? ImportError: No module named Image 11:53:53 Trac[loader] ERROR: Component module gallery.source.dir not found Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/trac/loader.py", line 42, in load_module module = __import__(name) File "build/bdist.linux-i686/egg/gallery/__init__.py", line 1, in ? File "build/bdist.linux-i686/egg/gallery/web_ui.py", line 26, in ? File "build/bdist.linux-i686/egg/gallery/api.py", line 20, in ? ImportError: No module named Image
I agree that some more documentation would be helpful... there is no mention of how you should install or set up the plugin, and no mention of possible prerequisites.
comment:13 Changed 18 years ago by
Similarly I have seen some bizaar errors that are intermittent after I installed this plugin (Trac 0.9.6, Python 2.3.5). I don't see the plugin, even in webadmin which is active, and this fault is intermittent resulting in a 500 internal server error with the following in the logs.
I contacted the plugin author, but have not had a response yet.
trac.log for the project environment
17:08:38 Trac[__init__] ERROR: Component module gallery not found Traceback (most recent call last): File "/opt/local/lib/python2.3/site-packages/trac/loader.py", line 42, in load_module module = __import__(name) File "build/bdist.solaris-2.9-sun4u/egg/gallery/__init__.py", line 1, in ? # File "build/bdist.solaris-2.9-sun4u/egg/gallery/web_ui.py", line 26, in ? File "build/bdist.solaris-2.9-sun4u/egg/gallery/api.py", line 25, in ? ImportError: cannot import name DatabaseManager
Apache 2 log
[Mon Oct 30 17:08:38 2006] [error] [client aa.xx.yy.zz] PythonHandler trac.web.modpython_frontend: File "build/bdist.solaris-2.9-sun4u/egg/gallery/source/dir.py", line 25, in DirectoryGallerySource, referer: http://removed [Mon Oct 30 17:08:38 2006] [error] [client aa.xx.yy.zz] PythonHandler trac.web.modpython_frontend: NameError: name 'IGallerySource' is not defined
I installed PIL after seeing error messages in the logs. The creation/installation of the egg from the source seemed to go fine.
Yes, documentation could be better for this plugin.
comment:14 Changed 12 years ago by
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
I'd suggest taking a look at the ScreenshotsPlugin.
Please refer to the Trac documentation on how to enable plugins.