|
hoboken
|
July 16, 2022 at 9:14 am
Until recently, in the Ticket Selector notes field, I could enter special characters like ampersand (&) and codes containing special characters like <br>. But now, every time I save an Event with any special characters, they get converted to HTML code. So "& gets saved as & and then the next time I save that event it gets saved as & and then the next time I save it becomes &amp; and so on.
This didn’t use to happen! Is it a new bug?
I really need to be able to put line breaks in this notes field. (Actually, I used to be able to just type Return for a line break, but now that gets saved as <br> and then <br> and then <br> and then….)
I’m using the latest EE Version 4.10.36.p. I have access to my templates, functions.php, etc. if that’s necessary to fix. Thanks for any help!
|
|
hoboken
|
July 16, 2022 at 9:16 am
Good grief, my codes got translated in my question, so now it doesn’t make any sense.
|
|
hoboken
|
July 16, 2022 at 9:21 am
Testing to see if the code tag helps:
& gets saved as &
and then the next time I save it becomes &
and then the next time I save it becomes &amp;
and so on.
a line break gets saved as <br>
and then <br>
and then <br>
and so on.
|
|
hoboken
|
July 16, 2022 at 9:22 am
No, code didn’t help.
:\
|
|
hoboken
|
July 16, 2022 at 9:24 am
I don’t know how to escape those characters here, but you can sort of see what I mean with the ampersand example in my second post.
|
|
Tony
|
July 20, 2022 at 8:03 am
Hi there,
Thank you for the report, I can reproduce this and have created a ticket for our developers to investigate it further.
However, as far as I know, we’ve not displayed the line breaks within the Ticket/DateTime descriptions previously? They’ll save within the editor but to save space did not output on the front end. <br> used to be allowed and I’m assuming you’ve manually added those previously?
|
|
hoboken
|
July 20, 2022 at 8:26 am
Yeah, probably I used <br> in the past, which would output as line breaks on the front end. (But that’s not working now.)
Thanks for looking into this! Eagerly awaiting the results of your investigation.
|
|
Joao Victor
|
July 25, 2022 at 4:39 pm
Hi there,
I am Joao from the Event Espresso support team.
Our development team is working to figure this out and include this fix on the next releases as soon as possible. Please, keep an eye on your Event Espresso Account for updates.
Let us know if you have any further questions!
|
