Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
ZMI: lines propery type does not render correctly #271
In #206 lines property types where switched to always store bytes. Since that change they are rendered no longer correctly in the ZMI:
Saving again adds a new layer of
I checked this against Zope 4.0b3 (before #206 landed on master): there
That values in lines-fields are bytes is the reason why creating a plone-instance fails at the moment.
I'd like to know how I should deal with the issue that all values from lines fields are bytes. Should I
Before the revert in zopefoundation/Products.GenericSetup@0f131a7 it was possible to creata a Plone instacne and work with it.
This was referenced
Apr 18, 2019
Some data points:
When submitting a value for a string (or lines) property, the converters are applied and at least in manual testing what ends up in the ZODB is correct if bytes is the desired outcome.
Going "the other way", to show the values the DTML-based form calls
This is a DTML rendering issue (the Properties tab is DTML-rendered). I have added issue zopefoundation/DocumentTemplate#43 to track it.
The culprit is here (and in the C-based equivalent) where the list of rendered values is joined into a single rendered string for serving. It uses Latin-1 as hardcoded character set for decoding strings:
Malthe Borch has a PR open at zopefoundation/DocumentTemplate#23, I'll see if I can massage to fit the current