Modify ↓
      
#439 closed enhancement (fixed)
Pluggable modules
| Reported by: | anonymous | Owned by: | Christopher Lenz | 
|---|---|---|---|
| Priority: | high | Milestone: | 0.9 | 
| Component: | general | Version: | 0.7 | 
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Right now each area is hardcoded in multiple places in the code making it hard to customize trac without breaking things every upgrade.
It would be nice if there was a module.conf or some file that let you define custom modules to run.
Attachments (0)
Change History (5)
comment:1 by , 21 years ago
| Summary: | Module Support → Module configuration support | 
|---|
comment:3 by , 21 years ago
| Owner: | changed from to | 
|---|---|
| Summary: | Module configuration support → Pluggable modules | 
comment:4 by , 21 years ago
| Resolution: | → fixed | 
|---|---|
| Status: | new → closed | 
The basic infrastructure is now in place since [1586].
comment:5 by , 20 years ago
| Milestone: | 2.0 → 0.9 | 
|---|
  Note:
 See   TracTickets
 for help on using tickets.
    


  
Configure/(de)activate modules in the configuration file.