Page 1 of 1

Notes and comments on 3.0

Posted: Wed Feb 19, 2020 6:03 pm
by plc
I didn't spend much time on it because I had to revert back but I did notice a few things I'd like to bring to your attention (whether they're known or not)

1) when migrating from 2.8.4 with MfH HTML replies in message body contain the HTML code
2) listing multiple emails via comma separated list in any of the email fields while creating a tickets yield an error

I reverted back to 2.8.4 w/MfH do entirely to 1) so if there's a "feature request" I'd give that one the priority.

Thanks again for creating 3.0. It looks great and I'm sure it will be. If there's anything I can do (non-code) to help, by all means don't be shy.

Re: Notes and comments on 3.0

Posted: Wed Feb 19, 2020 8:09 pm
by Klemen
1) I'm sure Mike knows more than I do what this is about :)
2) this is known (blocked by browsers due to type="email" fields) and will be fixed in a bugfix release. A temporary fix is available here: https://hesk.com/extras/hesk3/hesk300-m ... ls-fix.zip

Re: Notes and comments on 3.0

Posted: Thu Feb 20, 2020 4:45 pm
by plc
For 1) what if I turned off the rich text feature before uninstalling?

Re: Notes and comments on 3.0

Posted: Thu Feb 20, 2020 5:49 pm
by mkoch227
Rich text is stored on a per-message/reply basis, so turning off rich text in settings would only affect future messages/replies. It would have no impact on prior messages/replies.

As I mentioned before, I'm planning on either(1) releasing a tool to convert HTML messages to plaintext or (2) have the uninstaller convert all rich-text messages/replies to plaintext as part of the uninstall process. (it'll most likely be option #2 :wink: )

Re: Notes and comments on 3.0

Posted: Thu Feb 20, 2020 6:48 pm
by plc
Understood. As a safeguard moving forward I think I'll disable the setting(as much as I like it). That way if I move to 3 before those options are available at least the recent tickets will be legible. Thanks for responding again btw.