IDN: convert_to_punycode=1 attempt to convert iso-8859-1 to utf8 internally

Version 1.62.0

Bugfix
Finished

The Evolution skin will automatically convert a newly created domain to punycode piror to submitting it to DA. If you're using Enhanced skin with iso-8859-1 charset: eg, you've not run this: https://help.directadmin.com/item.php?id=364 OR you're using WHMCS which is not passing a UTF-8 encoded string then in order for the convert_to_punycode=1 auto-encoding to work, it must be first be converted from iso-8859-1 to UTF-8 internally for the punycode conversion to work. This fix adds this convertor to the punycode encoder if chunk encoding fails (it will attempt the 8859-to-utf8 conversion and try the encoding again). This is really only meant as a fallback, as it's far safer to pass things either in UTF-8 in the first place, or even better in punycode, however we understand that this is not always the case. Note that convert_to_punycode=1 is NOT enabled by default. This change only happens if you do have it enabled by default. ---- T29847

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