Nasty error message with obscure bug
Hi All, Got this weird error message: Module TAL.TALInterpreter, line 701, in translate Module Products.PageTemplates.TALES, line 261, in translate Module Products.Five.i18n, line 51, in translate Module Products.PageTemplates.GlobalTranslationService, line 33, in translate TypeError: expected string or buffer ...and eventually tracked it down to this code: <meta name="description" content="blah" i18n:attributes="description"/> The bug, of course, is that the i18:attributes should be content, not description, which doesn't exist. This results in a None msgid, which PTS used to do something (I don't know whether it was sane or not, no errors) with but which raises the rather obscure error above. I don't know if anything should be done here. Obviously it'd be nice if the error message was a bit nicer ("i18:attributes specified attribute 'description', which did not exist on tag 'meta' in /standard_template.pt") but it's a pretty obscure error. If anyone with greater knowledge could implement the above without much pain, that'd be great. In any case, hopefully Google will catch this some time and save the next weary traveller who bumps into it a couple of hours ;-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Chris Withers wrote:
Got this weird error message: Module TAL.TALInterpreter, line 701, in translate Module Products.PageTemplates.TALES, line 261, in translate Module Products.Five.i18n, line 51, in translate Module Products.PageTemplates.GlobalTranslationService, line 33, in translate TypeError: expected string or buffer
...and eventually tracked it down to this code:
<meta name="description" content="blah" i18n:attributes="description"/>
The bug, of course, is that the i18:attributes should be content, not description, which doesn't exist.
This results in a None msgid, which PTS used to do something (I don't know whether it was sane or not, no errors) with but which raises the rather obscure error above.
I don't know if anything should be done here. Obviously it'd be nice if the error message was a bit nicer ("i18:attributes specified attribute 'description', which did not exist on tag 'meta' in /standard_template.pt") but it's a pretty obscure error.
If anyone with greater knowledge could implement the above without much pain, that'd be great. In any case, hopefully Google will catch this some time and save the next weary traveller who bumps into it a couple of hours ;-)
How about opening a ticket in the collector? Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg@nuxeo.com
Florent Guillaume wrote:
If anyone with greater knowledge could implement the above without much pain, that'd be great. In any case, hopefully Google will catch this some time and save the next weary traveller who bumps into it a couple of hours ;-)
How about opening a ticket in the collector?
Is that the right thing to do here? I'm loath to open any another collector entry that will just sit there gathering dust. Hopefully the google archive trail will be enough for this issue... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On 19 Jun 2006, at 14:59, Chris Withers wrote:
Florent Guillaume wrote:
If anyone with greater knowledge could implement the above without much pain, that'd be great. In any case, hopefully Google will catch this some time and save the next weary traveller who bumps into it a couple of hours ;-) How about opening a ticket in the collector?
Is that the right thing to do here? I'm loath to open any another collector entry that will just sit there gathering dust.
Hopefully the google archive trail will be enough for this issue...
When I look for bugs to fix I don't read the mailing list archives for the past two years, I use the collector. Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg@nuxeo.com
Florent Guillaume wrote:
Hopefully the google archive trail will be enough for this issue...
When I look for bugs to fix I don't read the mailing list archives for the past two years, I use the collector.
Funny, I usually start by googling... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19 Jun 2006, at 15:51, Chris Withers wrote:
Florent Guillaume wrote:
Hopefully the google archive trail will be enough for this issue... When I look for bugs to fix I don't read the mailing list archives for the past two years, I use the collector.
Funny, I usually start by googling...
+1 for Florent. Use the collector. It is *the* place where people go to look for things to fix. What length of time it takes to fix is a totally separate issue. Bugs that get posted on mailing lists get ignored unless they are "the world is coming to an end" type bugs. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFElq8ZRAx5nvEhZLIRAmX7AJ99nlMnukRVaQ3Nx1Uj41yo8pZzdQCfWliU MuWlvpQuNG1BpdSzARcmG78= =nu3y -----END PGP SIGNATURE-----
Jens Vagelpohl wrote:
Use the collector. It is *the* place where people go to look for things to fix. What length of time it takes to fix is a totally separate issue. Bugs that get posted on mailing lists get ignored unless they are "the world is coming to an end" type bugs.
Read the thread, I'm not even convinced this _is_ a bug ;-) If, after reading the thread, you feel it is a bug, by all means open a collector entry... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Chris Withers wrote:
Jens Vagelpohl wrote:
Use the collector. It is *the* place where people go to look for things to fix. What length of time it takes to fix is a totally separate issue. Bugs that get posted on mailing lists get ignored unless they are "the world is coming to an end" type bugs.
Read the thread, I'm not even convinced this _is_ a bug ;-)
If, after reading the thread, you feel it is a bug, by all means open a collector entry...
Collector entries can always be rejected if it turns out there is no bug. This mailinglist thread will be forgotten next week, though. So, pretty please open a collector issue. Furthermore, I suggest you wrap this "bug" into a nice reproducible unit test demonstrating the behaviour you would *like* to see. Then this discussion can be much more fruitful. Philipp
Philipp von Weitershausen wrote:
Collector entries can always be rejected if it turns out there is no bug. This mailinglist thread will be forgotten next week, though. So, pretty please open a collector issue.
Fine: http://www.zope.org/Collectors/Zope/2135
Furthermore, I suggest you wrap this "bug" into a nice reproducible unit test demonstrating the behaviour you would *like* to see. Then this discussion can be much more fruitful.
Both are in the issue and were in the original mailing list post. Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (4)
-
Chris Withers -
Florent Guillaume -
Jens Vagelpohl -
Philipp von Weitershausen