Encoding issue with blogname in header  


0

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: 1 month  ago

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

  
Working

Please Login or Register