Loading Profile...
Author guidance not encoding extended characters as html entities
When you need to add characters like a "é" in the author guidance section, the character doesn't get turned into a html entity. If you add the html entity in, then when you edit the author guidance later, it gets turned back into the actual character and thus gets saved incorrectly again when you save your update.
I’m unconcerned
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Yerp, I know about this one. Something with the AJAX call going on there not escaping entities properly, since it works fine in stories and chapters. I'll see what I can do about getting it fixed. I have a feeling it's happening in comments too (they use a lot of the same code as the guidance box.)
Thanks for the heads up, though.
The company says
this solves the problem
-
Inappropriate?Alrighty, this should be fixed. Let me know if it's still giving you trouble anywhere, but I'm pretty sure comments and guidance should be encoding UTF-8 properly now.
I’m confident
The company says
this solves the problem
EMPLOYEE
