• osTicket Version = 1.15-git (0f169fef) — 65ca4e6 is available
  • Web Server Software = Apache/2.4.41 (Ubuntu)
  • MySQL Version = 8.0.26
  • PHP Version = 7.4.3

When trying to send emails with accents, OSTicket converts them to be unusual characters. The emails received with said characters included display correctly; the problem only lies when sending.

What I'm trying to send;

Pouvez-vous me montrer des captures d'écran des polices installées, s'il vous plaît ?

What is being sent and what is displayed in OSTicket as being sent;

Pouvez-vous me montrer des captures d'Ãcran des polices installÃes, s'il vous plaÃt ?

I did some searching around and I'm seeing perhaps to add certain lines to php.ini, but the php.ini file and online documentation seems to all list those lines as depreciated in the version of PHP being used, so I'm not sure what to do.

https://www.php.net/manual/en/mbstring.configuration.php#ini.mbstring.internal-encoding
https://www.php.net/manual/en/iconv.configuration.php#ini.iconv.internal-encoding

I've asked the devs to take a look at this thread.

My first thought though is that 1.15-git isn't a real version number. You should really go to the osticket.com/download website and download the current version and re-test to see if you still have the issue.

@TreesAndGrass

I cannot replicate this using osTicket v1.15.3.1, Apache, PHP 7.4, and MySQL 8. It's likely you are missing some extensions for PHP or something is weird with your database tables (ie. wrong character set, wrong collation, etc.). I would suggest what @ntozier said, then reviewing your PHP and database setup. It could also be something with Apache but I doubt it (wouldn't rule it out though).

Cheers.

    9 months later

    KevinTheJedi Hi, sorry for the late reply.

    I've updated to the latest version and this issue cropped up again. It also happens with apostrophe's and the £ sign when we're sending a message.

    "I hope you're well." becomes "I hope you’re well."

    Any other suggestion? I really have no idea where to begin looking for fixing this.

    We found that from our side, this happened when a user pasted text from a document made in Google Docs. It's formatted fine, outside of the character issue.

    I know the easiest suggestion would be to "not do that" but ideally we'd like to see this fixed as it's the software we use which struggles with this.

        TreesAndGrass

        I have no clue either. You can check and unhash the raw email contents (in the mailbox) to see if it's being wonky there.

        Cheers.

          Write a Reply...