On 02/12/2018 09:02 AM, Henrik Rasmussen wrote:
It seems that this issue is still unsolved. Is there any estimated date for a fix? https://gitlab.com/mailman/hyperkitty/issues/155 .
Thanks.
Henrik I commented on the issue, here is my comment for the lazy:
That's actually an issue with the Postgresql backend. They don't allow storing null characters in strings.
More information can be found in this bug report https://code.djangoproject.com/ticket/28201 and this discussion https://groups.google.com/forum/#!topic/django-developers/D1gvXYCezEc/discus...
TLDR: Saving such values is currently not supported, it's highly unlikely you want to store the null character in the first place, so you should clean your inputs (in this case the file) to strip them out.
I'm not sure Hyperkitty should actually do anything about that. Checking all inputs to strip null characters doesn't sound like a practical idea. If you import the values in any other way (loaddata for instace) you'd still run into this issue and there's nothing we can do about that.
So I guess the sane thing to do, is to say that your input file has errors that you should fix. But then again, I don't really have anything to say. It's up to @maxking and @abompard to decide that.