On Feb 1, 1:12 pm, Christian Boos <[EMAIL PROTECTED]> wrote: > No, but what revision are you using? > What do you see in the logs? > Does updating to the latest fix the issue? > Does going back to the "last known working revision" fix the issue? > > If there's no quick resolution for your issue, the best thing to do is > probably to create a new ticket containing the information requested above.
Apologies for the noise, this was in fact my bad. It was caused by faulty Apache access rules. I didn't see the connection since I didn't expect a Trac error message to an Apache problem (I expected the request to either succeed entirely or produce an Apache error message). I still don't quite understand it, but at least it had nothing to do with Trac. Thanks for the effort, anyway. -- Stian Grytøyr --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
