#3037: Multiple bugs in trac.config
---------------------------+------------------------------------------------
Reporter: athomas | Owner: athomas
Type: defect | Status: assigned
Priority: high | Milestone: 0.10
Component: general | Version: devel
Severity: major | Resolution:
Keywords: global config |
---------------------------+------------------------------------------------
Comment (by athomas):
This is tricky when the global config has an option set but the in-memory
option is `remove()`ed. All is fine until the config is saved and
reloaded. The environments config will ''not'' have an entry for the
option, so the global default will be used, consequently ignoring the
`remove()`.
Saving the list of options that have been removed to a special
`[removed_options]` section in the environment's config would solve this,
but is spectacularly ugly.
I propose we simply remove the `Configuration.remove()` method for
[milestone:0.10]. It is not used at all in Trac core, but is used by
WebAdmin and two plugins on TracHacks (!HackInstallPlugin and
!GeneralLinkSyntaxPlugin). From a cursory examination I suspect all of
these can be changed to use sentinel values or defaults.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3037>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
