Page 1 of 1
Using the WYSIWYG Editor for Replies
Posted: Wed Aug 17, 2022 6:30 am
by shddcit
HESK version: 3.3.2
HESK license: Licensed
PHP version: 7.4.21 (MySQLi)
MySQL version: 10.5.12-MariaDB-0+deb11u1-log
/hesk_settings.inc.php: Exists, Writable
/attachments: Exists, Writable
/cache: Exists, Writable
Good afternoon, Klemen.
Question.
What needs to be enabled on the php server to be able to use "Formatted Text (HTML)". On the server configured by our admins, after enabling "Formatted Text (HTML)", when sending a message, it falls on the 404 page.
Best regards, Denis
Re: Using the WYSIWYG Editor for Replies
Posted: Wed Aug 17, 2022 7:23 pm
by Klemen
It's hard to say what went wrong with the generic error - do you see anything in the server error logs? Perhaps mod_security or something similar is blocking the request? Any changes if you turn Debug mode on in Settings > Help desk?
Re: Using the WYSIWYG Editor for Replies
Posted: Thu Aug 18, 2022 7:27 am
by shddcit
Good afternoon.
In debugging mode, everything happens the same way. I made a little mistake. Goes to the html error 500.
There is a suspicion that some folders in the UNIX system do not have the necessary permissions set via chmod.
Translation in the screenshot:
The page is unavailable.
The site 10.84.0.46 cannot process this request yet

Re: Using the WYSIWYG Editor for Replies
Posted: Thu Aug 18, 2022 1:28 pm
by Klemen
This means the server stops script execution before Hesk output can be generated.
It's really hard to say what is going on without any errors. Are you able to give me access to your server to test this (in a private message)?
Re: Using the WYSIWYG Editor for Replies
Posted: Thu Aug 18, 2022 2:57 pm
by shddcit
Unfortunately no. Our support team does not go outside. It is located only within the corporate network.
But, in any case, thanks for the help, we will try to do without this editor. The topic can be closed.
Re: Using the WYSIWYG Editor for Replies
Posted: Fri Aug 19, 2022 7:47 am
by Klemen
No problem. What I would do is check all the server logs to try to determine what is causing the 500 error on this specific page.