Opened 17 years ago
Closed 17 years ago
#7004 closed defect (wontfix)
Mysterious permission error
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | web frontend | Version: | |
Severity: | normal | Keywords: | |
Cc: | allan@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
We regularly encounter a very mysterious problem on our trac installation that unfortunately is hard to replicate. For a certain project we have set all the right permissions and most of the time we can log on without problems. However, occasionally, we suddenly get the following error message after accessing the page again.
"WIKI_VIEW privileges are required to perform this operation on WikiStart"
This problem disappears again after some time again. We haven't figured out exactly what triggers this problem yet, nor do we understand exactly what makes it go away again. These are some possibilities:
- the problem is caused when being logged on, closing the browser window and accessing the page again in a new browser window (still being logged on)?
- the problems seems to go away again when an administrator logs on to another project of our trac installation (although this could be coincidental)?
I am just asking to see if anyone encountered similar problems. More info will follow later, as we investigate further.
Attachments (0)
Change History (7)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Without more info, this is going to be tough to debug or move forward. It might be worthwhile to ask on the MailingList to see if anyone else has a similar problem.
comment:3 by , 17 years ago
Hi, you are right. We are planning to break down the page to see if it there is some element in particular that is causing the permission error. We will let you know what we discover…
comment:4 by , 17 years ago
Keywords: | needinfo added |
---|---|
Milestone: | → 0.11.1 |
Well, no idea about what's going on here. You may want to add some more information here:
- the Trac version you're using
- whether you're using plugins and which ones
comment:5 by , 17 years ago
We localized the likely cause of the problem.
In the trac.ini file for the project where the problem occurs there were the following lines:
[components] permredirect.filter.<something>.* = enabled
This was the only difference with the trac.ini file of the other project. We removed these two lines and the problem did not come back again (yet). There was a string of <something> in the line that we forgot now that it is erased.
Does this gives some clues?
comment:6 by , 17 years ago
BTW That last comment was mine.
We use the latest version of track and have several plugins installed. I will ask my colleagues which ones.
comment:7 by , 17 years ago
Keywords: | needinfo removed |
---|---|
Milestone: | 0.11.1 |
Resolution: | → wontfix |
Status: | new → closed |
You've given enough information.
No clue what this permredirect plugin is or does, but you should report to problem to the plugin maintainer, thanks!
Just wanted to confirm that logging on as admin to another project of our Trac installation makes the problem go away again for the project in question…