November 20, 2012 at 4:52 am #6443
I have the problem that in my blog title there is an umlaut. All the subscription messages now have these ugly things in it:
any Ideas?November 20, 2012 at 12:25 pm #6444
Hi, the character you see are due to the utf8 encoding while sending email and probably I missed to declare that encoding for the subject. Since I changed the way I send email, probably I missed that (I already solved the problem in the past).
Stefano.November 20, 2012 at 12:51 pm #6445
Hi, I checked the code and it seems correct: can you give me the address of your blog so I can try to subscribe and verify the problem my self?
Stefano.November 20, 2012 at 3:22 pm #6448November 20, 2012 at 4:33 pm #6449
Ok, the problem is on pages and not on emails, I misunderstood. 🙂
I need to force the enconding of that pages, because probably the default encoding in your server is iso-8859-15 and not utf-8.
If you prefer to have a blog page to show those messages, see the documentation on how to set up it.
Stefano.November 20, 2012 at 4:35 pm #6450
If you want to patch it, open the file subscription/page.php and add that after line 21:
It should work.
Stefano.November 20, 2012 at 4:54 pm #6453
That didn’t work
But I changed the encoding of that file to utf – 8 BOM and the problem was solvedNovember 20, 2012 at 5:03 pm #6454
This is rather strange, but did you write the blog title directly in the page?
Stefano.November 20, 2012 at 5:29 pm #6473
No, I didnt write the title into the page, it is automatically added.
I guess (without further knowledge) that the blog title comes from configuration/basic settings “sender Name and adressee”November 20, 2012 at 5:52 pm #6474
Yes, it comes from blog configurations. It’s strange… may be the web server forces the content type charset and set it to utf-8 if the file has the BOM… really strange.
Stefano.December 14, 2012 at 1:55 pm #6790youngcrewParticipant
we have the same problem. Umlauts are not displayed correctly within the newsletter plugin (in the backend plugin and in sent emails).
All articles are displayed correctly on the homepage. Database and blog are using UTF8 character set.
We have installed the latest version of newsletter plugin. Obviously somewhere within the newsletter plugin the character set is changed.
Blog Article with Umlauts for Newsletter: http://wordpress.youngcrew.de/?p=324
If you need access to our blog I can send you backend login infos. I hope you find a solution.
Thank you in advance
PatrickDecember 27, 2012 at 1:36 pm #6864
there are pages auto generated by Newsletter (not inside the wordpress system) which can have this problem when the server charset is not utf-8. In fact the reported wrong characters are character utf-8 encoded but shown by a browser believing the page is not utf-8. The problem should be solved since I added an header, but maybe I missed someones.
Newsletter at the database level stores everything in UTF-8, sho it shouldnot be a database problem. Can you send me an access and the exact place where thos characters are shown wrongly?
Stefano.January 11, 2013 at 7:55 pm #6942youngcrewParticipant
sorry for my late reply. I have been in vacation.
I sent you an email to firstname.lastname@example.org with login data for our website.
The database is running utf8 and we do not have the problems with umlauts anywhere else on our website. When you login to our site, go in the NL-plugin, go to new message and you see in the preview that the first article “test” begins with a wrong interpretion of the Umlauts. Same article is shown with correct Umlauts in UTF8 at the website frontend. So it seems to be an error in the newsletter plugin interpretion of the article characters.
Thanks for your helpNovember 1, 2014 at 1:09 am #12140BernardBrunetParticipant
I have the same problem with my newsletter subscription email subject. Instead of “l’heure des montres” the subject shows some character code
What can I do?
Thank you!November 6, 2014 at 11:23 pm #12153
From time to time, this problem rises, but it seems connected to the mail servers. I definitively need to put a test function to verify that.
- You must be logged in to reply to this topic.