Subject line UTF-8 encoding
-
We have been happy with your plugin for years. But for the past 1-2 months, we have had problems with our subject lines showing, in some cases, complete ‘garbage’ full of question marks and, in other cases, html codes for special chars. We’ve tried turning on UTF-8 and turning it off but can’t find a setting that works for all subjects. Even more concerning is that in our small (3-person) web team, we are getting inconsistent results. So for example, two of us get all the question marks in a topic of no special characters with UTF-8 turned on, while the other gets a good subject line with UTF-8 turned on (even if it has special chars). Any recommendations? We’re staying current with releases on our test system so we’re on 2.11 with WordPress 5.5.1.
-
@matoca, thanks for that information. It helps to validate my theory and try to find a good solution.
Karen,
So the UTF-8 code uses quoted-printable encoding by default. We can try to change that to base64 and see if that’ll work. At this stage, I’m mainly wondering if the server is acting up with any encoding scheme or just quoted-printable.
Please add the following to your
functions.phpfile.function my_subject_base64( $prefs ) { $prefs['scheme'] = 'B'; return $prefs; } add_filter( 'bbpnns_subject_enc_preferences', 'my_subject_base64', 10, 1);The downside is that extensions such as WP Email Logging will have totally unreadable subject lines.
Please let me know if that works.
Here’s another test we can try (again, sorry for asking this but as I cannot replicate the issue locally, I have no other option).
Original code:
if ( true === $do_enc && function_exists( 'iconv_mime_encode' ) ) { /** * Enable UTF-8 characters in subject line * @since 1.9 */ $filtered_subject = iconv_mime_encode( 'Subject', html_entity_decode( $filtered_subject ), $preferences ); $filtered_subject = substr( $filtered_subject, strlen( 'Subject:' ) ); }New code:
if ( true === $do_enc ) { /** * Enable UTF-8 characters in subject line * @since 1.9 */ if ( function_exists('mb_encode_mimeheader') ) { $filtered_subject = mb_encode_mimeheader( html_entity_decode( $filtered_subject ), $preferences['input-charset'], $preferences['scheme'] ); } elseif ( function_exists( 'iconv_mime_encode' ) ) { $filtered_subject = iconv_mime_encode( 'Subject', html_entity_decode( $filtered_subject ), $preferences ); $filtered_subject = substr( $filtered_subject, strlen( 'Subject: ' ) ); } }It tries to use
mb_encode_mimeheader()if that function is available. It is a bit different from whaticonv_mime_encode()does and I’m not sure if it’ll work or not.Please let me know how it goes.
Cheers,
VinnyHi Karen,
Please make sure that the apostrophes haven’t been replaced by curly quotes or entities (that’s what I see in the email:
'instead of ‘).
The topic ‘Subject line UTF-8 encoding’ is closed to new replies.
