Traceback visiting a wiki page from search results

[richbodo@…]

Summary:

Pretty normal op, really. I can visit a wiki page via link on another wiki page, but not from the search results

Environment/Build:

Trac 0.10.4 on debian stable - pretty vanilla

Steps to Reproduce:

• 1) Sorry, reproducible in our trac wiki on at least one search
• 2) ask me for more data
• 3)

Expected Behavior:

page opens

Observed Behavior:

traceback below

Additional Notes:

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 244, in dispatch
    req.display(template, content_type or 'text/html')
  File "/usr/lib/python2.3/site-packages/trac/web/api.py", line 358, in display
    data = self.hdf.render(template, form_token)
  File "/usr/lib/python2.3/site-packages/trac/web/clearsilver.py", line 296, in render
    injector.feed(template.render())
  File "/usr/lib/python2.3/HTMLParser.py", line 108, in feed
    self.goahead(0)
  File "/usr/lib/python2.3/HTMLParser.py", line 148, in goahead
    k = self.parse_starttag(i)
  File "/usr/lib/python2.3/HTMLParser.py", line 239, in parse_starttag
    endpos = self.check_for_whole_start_tag(i)
  File "/usr/lib/python2.3/HTMLParser.py", line 314, in check_for_whole_start_tag
    self.error("malformed start tag")
  File "/usr/lib/python2.3/HTMLParser.py", line 115, in error
    raise HTMLParseError(message, self.getpos())
HTMLParseError: malformed start tag, at line 1493, column 99

[Christian Boos]

I can visit a wiki page via link on another wiki page, but not from the search results

It would be surprising that you could successfully access that page by another way. If it fails like that (malformed start tag, at line 1493, column 99) it must fail all the time when rendered to HTML.

Can you provide us with the text content of that page? (use .../wiki/ThePage?format=txt)

It's probably a duplicate of #3461 or #4365.

[Christian Boos]

This is a known defect of 0.10, it can't cope with malformed HTML produced by content renderers and/or macros.

See #4365.

(we won't fix it for 0.10, but 0.11 doesn't suffer from this problem)