Modify ↓
#1184 closed defect (wontfix)
Crash while attempting to access a restricted area
Reported by: | Owned by: | Christian Spurk | |
---|---|---|---|
Priority: | normal | Component: | RestrictedAreaPlugin |
Severity: | critical | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
Trying to load the page /wiki/restricted gets me this error:
AttributeError: 'NoneType' object has no attribute 'has_permission'
Error Log reports:
2007-02-06 14:13:23,076 Trac[main] ERROR: 'NoneType' object has no attribute 'has_permission' Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 387, in dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 176, in dispatch chosen_handler = self._pre_process_request(req, chosen_handler) File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 264, in _pre_process_request chosen_handler = f.pre_process_request(req, chosen_handler) File "build/bdist.linux-i686/egg/restrictedarea/filter.py", line 26, in pre_process_request AttributeError: 'NoneType' object has no attribute 'has_permission'
Using Trac 0.10.2
Attachments (0)
Change History (3)
comment:1 Changed 18 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 Changed 18 years ago by
I've added a clear error message in r1928 for users that have this problem.
comment:3 Changed 17 years ago by
Had this in trac 0.10.3, fixed it by upgrading the Web Admin plugin to 0.1.2.4429 (current freebsd port version)
Note: See
TracTickets for help on using
tickets.
Thanks for your bug report. Unfortunately I can only recommend you to upgrade to the latest Trac version 0.10.3.
I've looked into the problem but can't find the actual cause for it. Obviously in Trac 0.10.2 the
Request
objectreq
which is being passed to myIRequestFilter
methodpre_process_request
doesn't have theperm
field set appropriately. As I'm using thehas_permission
method ofperm
, the reported error occurs. I'm not really sure wether this was a Trac bug in 0.10.2 that somehow got fixed in 0.10.3 or wether I'm doing something wrong in the plugin. For the moment I'm assuming the former. If somebody reading this knows the cause, then I'd appreciate to hear it!