
Awesome work!!
iPhone user btw :-)
//M
On Oct 27, 2011, at 9:50 PM, Pavel Titov
On Thu, Oct 27, 2011 at 3:03 PM, Michiel Beijen
wrote: You'll see a ticket with some Cyrillic that is displayed as gibberish in the Android client. In the web client it is correctly displayed. This system is running as Unicode with a utf-8 MySQL database.
Thank you Michiel, I fixed it and uploaded updated version 1.1 on Market, it should become available soon.
Now response from servers that do not report charset in HTTP headers is assumed to be in UTF-8 by default.
- Crash on loading Dashboard
I *think* this is caused due to the fact that on this system the iPhone Handle was not installed.
You're right. And another reason may have been omitting http/https prefix from server name, I implemented proper handling of this situation as well.
Also I noticed a different issue, you can't set the new state when creating a ticket. I did have a field where I could set the pending date but this field was empty.
Also there is no auto-complete on customers for creating new tickets, but you can fill the CustomerID manually. I would then prefer not to have a CustomerID at all.
The issue here is that OTRS requests to fill in CustomerID and auto-complete is a bit tricky to implement. Though, it's on my TODO list.
As a remark, I think the errors that you get when you create a ticket if you submit without setting a queue are pretty rough. They are not
This one is much easier, I added validation of mandatory fields in 1.1 update.
Regards, Pavel --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs