🕸Fergus Duniho wrote on Sat, Dec 10, 2022 02:07 PM UTC:
What I think happened is that HTML entities got converted into the actual characters in the database, and this messed up those places where you relied on HTML entities. Since it now converts to HTML entities to display HTML in forms, and it now converts back to save to the database, you can no longer rely on using HTML entities if you use the HTML format. However, the new chr shortcode will let you display HTML entities without storing any in your code. Unlike HTML entities themselves, the shortcode is unaffected by the conversions that affect HTML entities. So, you can safely use them where you would once have used HTML entities. When replacing HTML entities, make sure to use chr with the text you would normally place between an ampersand and a semicolon for the HTML entity. If you use a number instead of text, it will use PHP's chr function to display the actual character rather than the HTML entity.
What I think happened is that HTML entities got converted into the actual characters in the database, and this messed up those places where you relied on HTML entities. Since it now converts to HTML entities to display HTML in forms, and it now converts back to save to the database, you can no longer rely on using HTML entities if you use the HTML format. However, the new
chrshortcode will let you display HTML entities without storing any in your code. Unlike HTML entities themselves, the shortcode is unaffected by the conversions that affect HTML entities. So, you can safely use them where you would once have used HTML entities. When replacing HTML entities, make sure to usechrwith the text you would normally place between an ampersand and a semicolon for the HTML entity. If you use a number instead of text, it will use PHP'schrfunction to display the actual character rather than the HTML entity.