Hello,
after upgrade to 3.3.9, customer can't see own requests opened via web interface.
1. Customer opens new ticket via web (in richtext)
2. Auto-reply is generated (in plaintext)
3. Agent replies (in richtext)
4. customer replies via web (in richtext)
5. customer replies via web (in richtext)
Customer is able to see the content of messages: 2, 3
The content of 1, 4, 5 is not-readable = empty.
If the customer makes another reply (6), then he is able to see the content of it, but only until another message is added. He only sees own last message, but not the previous ones.
The agent messages are always readable.
If we set Core:Web -> Frontend::RichText = no, then all messeges are displayed and are readable.
Agents don't have this problem.
Best regards,
Peter
[SOLVED] Customers can't see own messages in 3.3.9
Moderator: crythias
[SOLVED] Customers can't see own messages in 3.3.9
Last edited by peters on 29 Sep 2014, 13:06, edited 1 time in total.
OTRS 5.0.15 on Centos 6 and Postgresql 9.1
Re: Customers can't see own messages in 3.3.9
Small update:
If I select to "show page source code", the content of the customer messages is there.
Also, if I right-click the empty-message-header, and let it open in new browser tab/window, the content is displayed.
If I select to "show page source code", the content of the customer messages is there.
Also, if I right-click the empty-message-header, and let it open in new browser tab/window, the content is displayed.
OTRS 5.0.15 on Centos 6 and Postgresql 9.1
Re: Customers can't see own messages in 3.3.9
SOLVED: During the upgrade process, the file Kernel/Modules/CustomerTicketZoom.pm was not updated. Instead, new file was saved as CustomerTicketZoom.pm.custom_backup.
After replacing the old file with new one, issue fixed.
After replacing the old file with new one, issue fixed.
OTRS 5.0.15 on Centos 6 and Postgresql 9.1