Ticket #2140 (closed defect: fixed)
Opened 6 years ago
Last modified 6 years ago
"trac-admin <env> upgrade" does not upgrade old global macros
| Reported by: | trac-form@… | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | lowest | Milestone: | 0.9 |
| Component: | wiki system | Version: | 0.9b2 |
| Severity: | normal | Keywords: | |
| Cc: | trac-form@… | ||
| Release Notes: | |||
| API 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
Change History
comment:1 Changed 6 years ago by trac-form@…
comment:2 Changed 6 years ago by cmlenz
- Milestone set to 0.9
- Owner changed from jonas to cmlenz
- Status changed from new to 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:3 Changed 6 years ago by trac-form@…
- Cc trac-form@… added
That sounds like an excellent idea.
comment:4 Changed 6 years ago by cmlenz
- Resolution set to fixed
- Status changed from assigned to 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.