On Thu, Jun 27, 2013 at 1:49 AM, Olemis Lang <[email protected]> wrote: [...] > Even if you are right in your reasoning about config it seems to me > that the problem is more complicated than that . I've been looking > into this for a while . Like I mentioned before a similar error > happens (running apache2) after renaming wiki pages using trac-admin . > There's no associated config value in that particular case afaict .
I just fired up a debugger and stepped through a request to see why the component is still enabled. It turned out, that is_component_enabled checks the config which only looks at the value in cache. Is the other error you mention also present when run with tracd or just when installed with apache?
