-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
zope.traversing.interfaces.ITraversable violation #59
Comments
Heya,
While I could get everything working with some changes, even commit the changes, I'd prefer to if somebody would review any changes. |
Hi, I'm affraid the issue is still there. I've run into it while using five.pt-2.2.1 with Plone 4.2.6 and plone.app.imaging-1.0.9. plone.app.imaging expects to get a list as furtherPath but it gets a tuple instead. I didn't dig into it much, but when using this in ZPT template:
I'm getting a traceback:
I'm happy to provide some more info or to do some debugging when pointed in the right direction. Regards, |
Good question. I would need to look closer at this to know what's the solution. I don't really have a Plone stack handy though hmmm ... |
This is a bug in |
The
ITraversable
interface defines the thetraverse
method'sfurtherPath
parameter as "a list of names still to be traversed. This method is allowed to change the contents of furtherPath."However, when used in Plone 4.1 the
furtherPath
parameter is a tuple instead of a list which makes it impossible for the ITraversable implementation to modify it.I noticed this when writing a view template for a Dexterity type that uses path traversal to render an image tag by traversing to a plone.namedfile image (e.g. @@images/image/thumb). The
ITraversable
implementation inplone.namedfile.scaling.ImageScaling
attempts to .pop() the furtherPath which fails because it is a tuple.Components used: Chameleon 2.4.4, z3c.pt 2.1.4, five.pt 2.1.5, Plone 4.1, plone.namedfile 1.0.4
The text was updated successfully, but these errors were encountered: