Opened 4 years ago

# Plugins don't appear in Webadmin

Reported by: Owned by: siddharth.umrani@… jetheis normal CustomSelectAdminPlugin blocker 0.12

### Description

Hi,

Am running Trac with the following:
Debian (5.0.4), Apache (2.2.9), Python (2.5.2), python-apache binding (3.3.1) and Trac (0.11.1).
And trying to add the following plugins to my installation:
CondFields r7848 (http://trac-hacks.org/wiki/CondFieldsPlugin) and
TracTicketChainedFields r7863 (http://trac-hacks.org/wiki/TracTicketChainedFieldsPlugin)

Followed these steps:
(1) I created eggs for all of the above on the debain machine (where Trac is running) and put them in the plugins directory of my project (eggs attached).

(2) Then in the [components] sections of trac.ini added
condfields.* = enabled
tcf.* = enabled

(3) Also added (FIELDNAME).panel = (PANELTITLE) to ticket field with type 'select' in the [ticket-custom] section of trac.ini (for the CustomSelectAdmin plugin).

(4) Then restarted Apache.

But cannot see those plugins under the 'Plugins' section of the 'Admin' tab of my Trac installation (Logged in as user who has TRAC-ADMIN permissions).
Also the log files of either Apache or Trac (with log level = DEBUG) do not show any error messages.

Could anyone please suggest any fix or alternative to this issue, since i have tried all i could using documentation on the web.
Thanks !

### Changed 4 years ago by siddharth.umrani@…

Egg for CondFields plugin

### Changed 4 years ago by siddharth.umrani@…

Egg for TracTicketChainedFields plugin

### comment:1 Changed 4 years ago by siddharth.umrani@…

Just checked the trac.log file and found the following entries:

2010-04-20 11:43:29,336 Trac[loader] DEBUG: Loading CustomSelectAdmin from /usr/lib/python2.5/site-packages/trac/projects/development/plugins/CustomSelectAdmin-0.5-py2.5.egg


### comment:2 Changed 4 years ago by anonymous

• Severity changed from major to blocker

### comment:3 Changed 4 years ago by dmcr@…

• Trac Release changed from 0.11 to 0.12

The plugin now works, but there are a few shortcomings with it:

2) You can't do everything from the Admin panels: setting the <name>.panel value still has to be done from trac.ini, so Trac Admins have to have login access to the Trac server to use this plugin, and this is not always desirable or possible.

3) This plugin insists on setting a default value for the custom field, even if you have not set one, or you remove the one it sets for you.

It is otherwise a nice feature to have.

Dennis McRitchie

### Modify Ticket

Change Properties