Closed mgmax closed 8 years ago
I just tested your branch with the conflicting data from the mail thread (it contained umlauts in the comment).
development
crashes with the data and this branch creates the entry. I have tested client list
and client show
, both work still after the fix :-)
The entry in the database looks good and both umlauts in address and comment do work now (and failed in development
)
Booking onto the customer in the GUI works too.
Concerning my first comment about the empty string that should be unicode: I had a look at the code. Since the string gets inserted into a unicode-string with format it is irrelevant whether the empty string is unicode or not. For completeness I would be happy, if you could change the second string to unicode.
[pseudo-patch]
- default_str = u" [{0}]".format(unicode(default_input)) if default_input is not None else ""
+ default_str = u" [{0}]".format(unicode(default_input)) if default_input is not None else u""
Apart from that I would say this fix is ready to merge.
Feel free to edit and merge :-)
merged ;-)
(and deployed)
Current coverage is 28.19% (diff: 0.00%)