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.
Notes and comments on 3.0
Moderator: mkoch227
Re: Notes and comments on 3.0
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

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
Klemen, creator of HESK and PHPJunkyardWas this helpful? You can buy me a drink here 
You should follow me on Twitter here
Help desk software | Cloud help desk | Guestbook | Link manager | Click counter | more PHP Scripts ...
Also browse for php hosting companies, read php books, find php resources and use webmaster tools


Help desk software | Cloud help desk | Guestbook | Link manager | Click counter | more PHP Scripts ...
Also browse for php hosting companies, read php books, find php resources and use webmaster tools
Re: Notes and comments on 3.0
For 1) what if I turned off the rich text feature before uninstalling?
Re: Notes and comments on 3.0
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
)
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

Mike, Lead Developer of
HESK: A surprisingly simple, user-friendly and FREE help desk software with integrated knowledgebase.
Re: Notes and comments on 3.0
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.