[Zope] Zope 2.6.4 -> 2.10.0 Migration (PageTemplates, Unicode, etc.)
So... We decided to move from Zope 2.6.4 to something newer (currently targetting Zope 2.10.0). I immediately found that none of our PageTemplates work we get an error on PageTemplates/Expressions.py line 92 that call_with_ns is not defined. ob = call_with_ns(ob, ns, 2) Changing it as follows fixes the problem, I think this is a bug. ob = ZRPythonExpr.call_with_ns(ob, ns, 2) Next... we have lots of PageTemplates which raise the following exception: Module zope.pagetemplate.pagetemplate, line 118, in pt_render Module StringIO, line 271, in getvalue UnicodeDecodeError: 'ascii' codec can't decode byte 0xb9 in position 93: ordinal not in range(128) I suspect there are non-ascii characters in the file, but I'm not sure how to fix this, or how I would know what to replace it with. Is there a way to turn off Unicode support? Any other issues I might run into during this upgrade? Should we move to an older version (2.8? 2.9?) first and then onto 2.10? Thanks, -- Brian Brinegar Web Systems Developer Engineering Computer Network
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Brinegar wrote:
So... We decided to move from Zope 2.6.4 to something newer (currently targetting Zope 2.10.0). I immediately found that none of our PageTemplates work we get an error on
PageTemplates/Expressions.py line 92 that call_with_ns is not defined.
ob = call_with_ns(ob, ns, 2)
Changing it as follows fixes the problem, I think this is a bug.
ob = ZRPythonExpr.call_with_ns(ob, ns, 2)
The released version of that module does not have that bug: http://svn.zope.org/Zope/tags/2.10.0/lib/python/Products/PageTemplates/Expre... Are you sure you are running 2.10.0?
Next... we have lots of PageTemplates which raise the following exception:
Module zope.pagetemplate.pagetemplate, line 118, in pt_render Module StringIO, line 271, in getvalue UnicodeDecodeError: 'ascii' codec can't decode byte 0xb9 in position 93: ordinal not in range(128)
I suspect there are non-ascii characters in the file, but I'm not sure how to fix this, or how I would know what to replace it with. Is there a way to turn off Unicode support?
I would probably just bring the affected templates up in the 2.6 ZMI and cut and paste their text across into the 2.10 site (to get the charset right).
Any other issues I might run into during this upgrade? Should we move to an older version (2.8? 2.9?) first and then onto 2.10?
Maybe. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFSNdo+gerLs4ltQ4RAptUAKCnv3uwlbCcWBbZVltj2MlFKyA3JACeMbvV QbB+jn14ymVTpKJoUcBfgnA= =Soon -----END PGP SIGNATURE-----
participants (2)
-
Brian Brinegar -
Tres Seaver