On Thursday, March 10, 2016 at 5:01:02 PM UTC-5, RjOllos wrote:
>
>
>
> 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
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
> >
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
On 3/10/16, Florian Berger wrote:
> Hi,
>
Hi !
:)
> are there occasions where trac rewrites / resets trac.ini on its own?
>
Yes . Both Trac and plugins may modify it .
Given that `env` variable contain a reference to an instance of
`trac.env.Environment` class then
Hi,
are there occasions where trac rewrites / resets trac.ini on its own?
During normal operation, I sometimes get the error "The environment
needs to be upgraded."
However I found that this, apparently, is due to trac resetting
trac.ini, with e.g. the [ticket-workflow] section gone missing, as