Unicode Fields not stored when replying to ticket

  • Resolved customer99

    (@customer99)


    7 years, 2 months ago

    Hello,

    I’m testing out the functionality of this plugin before purchasing an additional pack, and I encountered an error with the support of Unicode values for the department, product and priority fields.

    So I entered Unicode (Cyrillic) values for the department, product and priority fields for the ticket.

    The issue is that the user can see those fields just fine after he submits the tickets and the fields are displayed correctly in the list of tickets in admin panel.

    image of ticket displayed fine

    However, when you try to reply to a ticket with Unicode (Cyrillic) value for a field (department, priority, etc), the fields are not set and you have to set each field that contained Unicode value manually.

    image of fields not set

    And when I tried with latin values for those ticket fields the tickets are also stored in the reply form so I can just simply reply.

    I would really appreciate if someone can provide suggestions on how to solve this, I’ve tried changing the database encoding and collation to unicode, but that did not work.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author melliesou

    (@melliesou)

    7 years, 2 months ago

    Hi @customer99,

    Thanks for reporting this issue with using these Unicode values for the product and priority fields. Can you provide some examples of what you have for the “Options” in the settings for the custom fields? (Both Option ID and option Label)?

    Thread Starter customer99

    (@customer99)

    7 years, 2 months ago

    So I have enabled all department, product and priority fields and made them mandatory for the ticket form.

    I have the following options (left) with the test values (right):
    Department: тест; маркетинг;
    Priority: приоритетно; нормално;
    Product: сајт; панел;

    Thank you very much for the quick response

    Plugin Author melliesou

    (@melliesou)

    7 years, 2 months ago

    Hello @customer99,

    In this case, if you try setting the option ID (first field) to a number and then the value field to a simple number does that work ok? (So your user should still see the text properly, and the fields should still be selected by default on the ticket page)

    Let me know if the above doesn’t solve the issue. (I’ll mark this thread as resolved for now, but please add more notes or questions if anything doesn’t work and I’ll follow up)

    Thread Starter customer99

    (@customer99)

    7 years, 2 months ago

    Thank you @melliesou

    Setting the option ID (first field) to a number has solved my issue.

    Plugin Author melliesou

    (@melliesou)

    7 years, 2 months ago

    That’s great, glad that your issue is solved @customer99

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Unicode Fields not stored when replying to ticket’ is closed to new replies.