Encoding issue with blogname in header  


Our client's blogname includes an apostrophe and it's coming out as & #039; (without the space between the ampersand and hash).


Can you fix this?

I've noticed that products don't have the same problem.

Edited: 9 months  ago

Ok, thank you for letting us know, we'll fix this in next release.


Please Login or Register