Messages: "E-Mail Only" to use same encoding as skin (SKINS)

Version 1.61.0


If you've got a UTF-8 skin, and are sending an "email only" message to one or more Users, unless you were to specify: |?HEADER=Content-Type: text/plain; charset=UTF-8| the message would not get the UTF-8 encoding, and the resulting email might be garbled if you were using special characters. This changes does 2 things: 1) Includes: <input type=hidden name=encoding value="|LANG_ENCODING|"> where |LANG_ENCODING| is replaced with the encoding, we'll use UTF-8 in the examples below, in all email-only messaging forms, so DA knows what the encoding it. Unfortunately, the POST does not include sufficient encoding information from the form to do this automatically, hence changes are needed. With that, should the Content-Type header not already be set (via |?HEADER=), then DA will add headers Content-Type: text/plain; charset=UTF-8 MIME-Version: 1.0 2) The E-Mail only form now supports up to 4 headers: HEADER, HEADER2, HEADER3, HEADER4 which you can set with, eg: |?HEADER3=Your: header| in the message. ---- Note that these e-mail only messages continue to support <html> formatting, as before, simply by starting the message with: <html> which will now also include the UTF-8 charset, eg: Content-Type: text/html; charset=UTF-8 ============== (SKINS) Enhanced skins changes in: data/users/ticket/* create.html create_multiple.html reply.html which includes: <input type=hidden name=encoding value="|LANG_ENCODING|"> in the submission form. ---- T25379 EVO1854

Interested to try DirectAdmin? Get a 30-day Free Trial!