Modify ↓
Opened 17 years ago
Closed 15 years ago
#4737 closed defect (worksforme)
searching with the sensitive tickets plugin in version 0.11 creates a
| Reported by: | anonymous | Owned by: | obs |
|---|---|---|---|
| Priority: | normal | Component: | SensitiveTicketsPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Jeff Hammel, m.a.swertz@… | Trac Release: | 0.11 |
Description
Trac detected an internal error:
RuntimeError: maximum recursion depth exceeded
see attached for traceback (only the first part is included) The error directly points to sensitivetickets
Attachments (1)
Change History (6)
Changed 17 years ago by
| Attachment: | tracbug.txt added |
|---|
comment:1 Changed 17 years ago by
| Cc: | Jeff Hammel added; anonymous removed |
|---|
comment:2 Changed 17 years ago by
this is hard to debug with so little information. what were you doing to get this error? did you have the SENSITIVE_VIEW permission? verbose reproduction steps needed
comment:3 Changed 16 years ago by
| Owner: | changed from Sebastian Benthall to obs |
|---|
comment:4 Changed 16 years ago by
| Cc: | m.a.swertz@… added |
|---|
I have the same problem, caused by the combined use of SensitiveTicketsPlugin with PrivateTicketsPlugin. It seems the PrivateTicketsPolicy and SensitiveTicketsPolicy recursively call each other.
Why both?
- I want to hide sensitive tickets in anonymous view and
- limit the visibility of these tickets to particular groups in authenticated view
A solution seems to merge the two plugins but that is not trivial (for a non python programmer at least).
comment:5 Changed 15 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Cannot replicate issue.
Note: See
TracTickets for help on using
tickets.
traceback for sensitive tickets bug in if 'SENSITIVE_VIEW' not in perm