On Mar 13, 1:41 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> On Mar 12, 2:32 am, Christian Boos <[EMAIL PROTECTED]> wrote:
>
>
>
> > [EMAIL PROTECTED] wrote:
> > > ...
> > >>> traccc/traccc.py", line 229, in process_request
>
> > >> I haven't looked at the TracCC code, but most probably there's a
> > >> "Markup(something)" in there, with "something" being a string with
> > >> non-ascii content. This code should be modified to read
> > >> "Markup(to_unicode(something))", with "to_unicode" being our generic,
> > >> robust, anything to unicode converter ;-)
> > >> (add "from trac.util.text import to_unicode" at the top of the traccc.py
> > >> file).
>
> > > Thanks. I take a look at the file traccc.py: Here is the 2 lines with
> > > Markup(something)"
> > > ...
>
> > > 2.   req.hdf['cc.html_result'] =
> > > Markup(style.saveResultToString(result))
>
> > > Both seem to be ascii content, so which lines need to be modified?
>
> > The one which is at line 229, most probably the second :-)
>
> > > And CruiseControl plugin is 1 egg file. How can I modify the source
> > > traccc.py (which is inside the egg file)?
>
> > An egg file is simply a zip file, so unzip it, modify the .py file,
> > re-zip it.
> > Better yet, inform the plugin author about the issue :-)
>
> I fix per your idea. But it still crashes. Now it is from '/usr/lib/
> python2.4/site-packages/trac/web/clearsilver.py'.
...snip...
> HTMLParseError: malformed start tag, at line 44, column 1

The plugin seems to be generating malformed HTML.  Trac parses the
output in order to inject some HTML for CSRF protection, so the output
needs to be well-formed.

-- Matt Good


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to