Closed poguez closed 10 years ago
IMHO, the requirement should not be "latin chars" but UTF-8 support
@poguez Looks like it was just a debug message that was not properly encoded. Could you pull latest master, restart the harvester processes and see if that fixes the issue?
As an aside, on my experience using special (non-ascii) characters for identifiers ends up causing trouble sooner or later so my recommendation is always to avoid them. But this should fix your issue anyway.
@poguez did the patch fix the issue?
Genial!
Works great!
Is there support for latin characters? I had some issues while working with texts in spanish that contain áéíóúÁÉÍÓÚ.
The error happens with this two occurrences in the same order as the errors in the log
Error Log