[Zope] Zope 2.7.2 breaks Plone 2.0.3 login_form

[Fred Drake]

On Fri, 23 Jul 2004 09:47:25 +1000, Peter Mayne
<petermayne at ap.spherion.com> wrote:
> <script type="text/javascript">
> // <![CDATA[
>     if (cookiesEnabled && !cookiesEnabled()) {
>        document.writeln('<div class="portalMessage"><img
> src="info.gif">Cookies
> are not enabled. You can not log in if they are turned off. <a
> href="enabling_cookies">How to enable cookies</a>.</div>');
>     }
> // ]]>
> </script>
> 
> One workaround was to comment out this chunk of script. Another one was
> to revert back to Zope 2.7.1. :-)

And still another is to split your string literals where they look
like markup, because even CDATA marked sections aren't meant to
protect you from everything.  Try changing the line with the </a> to

href="enabling_cookies">How to enable cookies<' + '/a>.<' + '/div>');

and the problem should go away.

> I have no idea if this is Zope tightening up and rejecting an incorrect
> Plone template, or an introduced bug in Zope which is rejecting a
> correct Plone template.

This is Zope no longer duplicating a module from Python's standard
library, and the Python module is slightly stricter than the version
previously in Zope.  I consider this a bug in Plone's template, and it
can be trivially fixed there.  It is unfortunate that the looser
version of the HTMLParser module was used for so long; that was an
oversight on my part.  It should have been removed from Zope 2 the
minute we required Python 2.3.x.

This is *not* related to the recent hotfix, as Andreas Kaiser
suggests.  The issues related to that were all related to the hotfix
product being loaded after some templates were compiled.


  -Fred

-- 
Fred L. Drake, Jr.    <fdrake at gmail.com>
Zope Corporation