WordPress.org

1. Shonu
   Member
   Posted 8 months ago #

   4.15:

   I noticed that booking confirmation email using
   #_BOOKINGTICKETPRICE
   was coming back as
   Betrag: � 75.00
   Thought the headers of the email seem to use charset UTF8 in content, it seems to be handled internally possibly as LATIN (8859-1?) and then added in UTF8 context causing this issue ?

   http://wordpress.org/extend/plugins/events-manager/

2. agelonwl
   Member
   Posted 8 months ago #

   does dollar sign works? does viewing it to other browser is still the same and also maybe you can try changing the sign to a more safe html code; it is located at em-functions.php. let us know if its solve the issue

3. agelonwl
   Member
   Posted 8 months ago #

   and also 4.17 is out now

4. Shonu
   Member
   Posted 8 months ago #

   kow, but my dev system to test it was running on poor PHP environment and just got upgraded last night. From the changelog I got scared to just apply it on PROD.
   Question: If an upgrade has an impact on existing events structure and configuration, would that be warned in the changelog ?
   Running 4.15 and going to 4.17, is there anything to consider?

   Thanks

5. Shonu
   Member
   Posted 8 months ago #

   Changing to dollar means changing the locale, but the browser is fine, it is the email.
   I would' have assumed the Euro be encoded as entity €..is it not ?
   I'll check later this week

6. agelonwl
   Member
   Posted 8 months ago #

   you can change that on em-functions.php ~ function em_get_currencies(){ $currencies->true_symbols and give us feedback for the result

7. agelonwl
   Member
   Posted 8 months ago #

   about upgrading to 4.17; it should not affect any existing settings however to be sure you can try it on your local or dev site (and backup first)

8. Shonu
   Member
   Posted 8 months ago #

   Good. I have my on plugin for overridings, so I will hook into filter
   em_get_currencies and reset EUR to € - just hope it does not actually display € in the email.
   But wait, what will happen with plain text emails ?
   for text emails, only true_symbols can work and no HTML entity.
   And I just realised that the email was actually:
   Content-Type: text/plain; charset="utf-8"
   The only way out is to for now use EUR as a symbol as a workaround. So, there is still some charset mapped wrongly..... (e.g. packing 8859-1 into a UTF-8 container)

   Hmmm.

   Thanks anyhow for the location and the workaround hint

Reply

You must log in to post.