On Thursday, March 10, 2016 at 1:51:59 PM UTC-8, Florian Berger wrote: > > On 10.03.2016 21:49, Olemis Lang wrote: > > Yes . Both Trac and plugins may modify it . > > Given that `env` variable contain a reference to an instance of > > `trac.env.Environment` class then every invocation of > > `env.config.save()` will overwrite it . > > Okay, I see. > > But shouldn't the current on-disk state of trac.ini be preserved then, > for all sections not affected? > > I.e. is the loss of [ticket-workflow] on overwrite a bug or a feature? :-) >
The loss of [ticket-workflow] is not expected behavior. What is expected behavior: when ticket-workflow is missing, Trac will prompt you to upgrade the environment, which then restores the default ticket-workflow section. Trac normally changes trac.ini when an update is applied from the Admin pages, and that update needs to be stored in trac.ini rather than the database. Otherwise, Trac won't modify trac.ini. As Olemis said, plugins have access to trac.ini, so a plugin could inadvertently do something bad. I would first suspect a plugin is removing your [ticket-workflow] section, but nothing you have installed looks too suspicious. - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
