Modify ↓
Opened 5 years ago
Closed 5 years ago
#13256 closed defect (invalid)
Permission policies not changed upgrading from Trac < 1.2
| Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
Discussed in gmessage:trac-users:z3nTgHPbBaw/T30q9SKgAgAJ. Instead of comparing permission_policies to the Trac 1.2 default value, we should look at the entries in the list and be more flexible in deciding whether to automatically upgrade.
Attachments (0)
Change History (3)
comment:1 by , 5 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 5 years ago
comment:3 by , 5 years ago
| Milestone: | 1.4.2 |
|---|---|
| Resolution: | → invalid |
| Status: | assigned → closed |
Thanks for investigating, I had forgotten about db30.py. The reporter confirmed that he overwrote trac.ini from 1.4 with trac.ini from 1.0, thereby causing the problem.
I suppose we could handle permission_policies = LegacyAttachmentPolicy,DefaultPermissionPolicy, but not sure that is needed.
Note:
See TracTickets
for help on using tickets.
upgrades/db30.py (#11244) auto-upgrades from the old default:
To:
And upgrades/db43.py (#12719) auto-upgrades from that to:
But the reported case still had:
The upgrades do print information about manually adding the new policies.