#539: Product-scope TracAdmin commands don't take effect until tracd is
restarted
------------------------+-------------------------------
Reporter: rjollos | Owner: rjollos
Type: defect | Status: review
Priority: major | Milestone: Release 8
Component: dashboard | Version:
Resolution: | Keywords: tracadmin command
------------------------+-------------------------------
Comment (by olemis):
In general I suspect the issues in comment:description are not related to
those mentioned in comment:3 . The former is about product config sync
whereas the later is about a mysterious DB caching , I've not been able to
detect its root cause .
Replying to [comment:17 rjollos]:
[...]
> To reproduce the issue with component enabling/disabling not taking
effect until `tracd` is restarted,
> 1. Open trac-admin:
> {{{#!sh
> $ trac-admin $env
> > product admin prod1 config set components trac.wiki.* disabled
> }}}
> 1. Refresh `/products/prod1/wiki`. The component will not be disabled
until `tracd` is restarted.
>
I'll start from here , and try to reproduce ( ... and fix if a problem is
found )
> All of these issues were seen with TracStandalone (make sure to //not//
pass the `-r` flag to `tracd`).
>
> The `ProductEnvironment` is retrieved from the cache when the page is
refreshed, and I don't see a mechanism by which the cache will be
invalidated when a request is sent and the `ProductEnvironment` is
retrieved from the cache.
The `ProductEnvironment` cache does not need to be invalidated at all ,
just product config cache . Anyway , let me see what's wrong with your
scenario .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/539#comment:20>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
