#1322 closed defect (fixed)
Error reporting for wiki processors broken
Reported by: | Christopher Lenz | Owned by: | anonymous |
---|---|---|---|
Priority: | normal | Milestone: | 0.9 |
Component: | wiki system | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Since the WikiProcessor refactoring [1347] error reporting on Wiki processors is broken, so that instead of getting the original error embedded in the page, you get a general Trac error page with the following exception:
Traceback (most recent call last): File "/Users/chris/Projekte/Trac/trunk/trac/web/cgi_frontend.py", line 102, in run dispatch_request(os.getenv('PATH_INFO', ''), req, env) File "/Users/chris/Projekte/Trac/trunk/trac/web/main.py", line 320, in dispatch_request module.run(req) File "/Users/chris/Projekte/Trac/trunk/trac/Module.py", line 49, in run self.render(req) File "/Users/chris/Projekte/Trac/trunk/trac/Wiki.py", line 150, in render self._render_view(req, pagename) File "/Users/chris/Projekte/Trac/trunk/trac/Wiki.py", line 316, in _render_view info = { File "/Users/chris/Projekte/Trac/trunk/trac/WikiFormatter.py", line 637, in wiki_to_html Formatter(hdf, env, db, absurls).format(wikitext, out) File "/Users/chris/Projekte/Trac/trunk/trac/WikiFormatter.py", line 594, in format self.handle_code_block(line) File "/Users/chris/Projekte/Trac/trunk/trac/WikiFormatter.py", line 569, in handle_code_block self.out.write(system_message('Error: Failed to load processor <code>%s</code>' % name, e)) NameError: global name 'e' is not defined
In particular, I'm getting the error on the WikiRestructuredTextLinks when docutils is not installed.
Christian, I'm assigning this to you as you know that particular change much better than I do.
Attachments (2)
Change History (5)
by , 20 years ago
Attachment: | trac-#1322.patch added |
---|
comment:1 by , 20 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Oops, sorry for the error. I'll apply the patch, but, as such, the error message is quite cryptic. I'll see if I can find a better solution later.
Simple patch that probably fixes the problem (untested).