Opened 6 years ago

Closed 6 years ago

# Problem with using this plugin in multi-trac environment

Reported by: Owned by: l0co@… Steffen Hoffmann normal CcSelectorPlugin normal plugin concurrent interference Ryan J Ollos 0.12

### Description

I have a multiple trac 0.12.2 envs working under apache.

I use the cc_selector plugin in each of them, and until now I've got separate plugin eggs loaded into plugins directory of particular env. In this config I've noticed that the cc_selector works only for one of the envs at the time, and exactly for the one that is firstly invoked after /etc/init.d/apache restart. For other envs I cannot see the selector field.

Tommorow I've changed the config so that I have only one shared plugins directory and now I can see the cc_selector in all envs. The problem for separated plugins dir exists, though.

### comment:1 Changed 6 years ago by l0co@…

Of course not tommorow, but today ;)

### comment:2 in reply to:  description Changed 6 years ago by Steffen Hoffmann

Cc: Ryan J Ollos added; anonymous removed plugin concurrent interference added → wontfix new → closed

I have a multiple trac 0.12.2 envs working under apache.

I use the cc_selector plugin in each of them, and until now I've got separate plugin eggs loaded into plugins directory of particular env. In this config I've noticed

![...]

Well, been there done that. Simply put, this is just a mess. You can't have multiple instances of Trac plugins without name space clashes and nasty side-effects. Stop it, at least as soon as you notice problems.

Tommorow Today I've changed the config so that I have only one shared plugins directory and now I can see the cc_selector in all envs. The problem for separated plugins dir exists, though.

I think I had the same issues, and working with one shared plugin directory helped here too. And a major headache, plugin upgrades, was gone as well. Do nothing else. Note, that this wontfix is largely a cantfix.

### Modify Ticket

Change Properties