Zope 3

&#lsquo; in TAL produces misleading error message

Bug #54229 reported by Matthew Paul Thomas
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zope 3
Won't Fix
Undecided
Unassigned
zope.tal
Invalid
Undecided
Unassigned

Bug Description

I accidentally typed &#lsquo; instead of ‘ in a page template.

This caused Zope to produce an error message: "TAL attributes on <tal:registered> require explicit </tal:registered>, at line 52, column 11" -- where <tal:registered> was one of the elements, but not even the innermost element, surrounding the bad entity.

When I fixed the entity, the error went away, so the former caused the latter, but the error message is wrong.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

I think this bug probably should be forward to Zope upstream.

Changed in launchpad:
status: Unconfirmed → Confirmed
Curtis Hovey (sinzui)
affects: launchpad-foundations → zope3
Tres Seaver (tseaver)
Changed in zope.tal:
status: New → Confirmed
Changed in zope3:
status: Confirmed → Won't Fix
Revision history for this message
Colin Watson (cjwatson) wrote :

The zope.tal project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope.tal.

Changed in zope.tal:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.