Opened 19 years ago
Closed 19 years ago
#2140 closed defect (fixed)
"trac-admin <env> upgrade" does not upgrade old global macros
| Reported by: | Owned by: | Christopher Lenz | |
|---|---|---|---|
| Priority: | lowest | Milestone: | 0.9 |
| Component: | wiki system | Version: | 0.9b2 |
| Severity: | normal | Keywords: | |
| Cc: | trac-form@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
If a global macro has already been installed by trac-admin during a previous upgrade, then subsequently updated, trac-admin will fail to require an upgrade to the latest version.
This is fiddly and the fix may not be obvious, because you then have to manually delete the .py/.pyc from every Trac environment before again initiating an upgrade.
On a related note, it may also not be obvious to many that installing a global macro will require a trac environment upgrade.
Attachments (0)
Change History (4)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
| Milestone: | → 0.9 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
I've found the upgrade stuff for wiki-macros rather annoying/irritating myself.
How about we just make the UserMacroProvider use both the local and the global wiki-macros directory to serve macros? That would probably be a lot more intuitive.
comment:4 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Should be fixed in [2337].
After messing around with this over the last few days, I have found this to be more and more of an annoyance.
The most irritation occurs when you have a mix of global and per-environment macro's, forcing one to manually delete only the global macro's if you wish to upgrade.