In the visual editor, whenever a user types an ampersand into a text input it gets written as the & HTML entity. The site I’m working on is an Astro project and I just use regular templating like <h2>{section.heading}</h2> to render the text field which doesn’t decode the entities and leaves it as a literal “&” on the page. Is there a way to prevent the CloudCannon visual editor from converting an ampersand to the HTML entity? Or is that the wrong approach here?
I’m guessing that you’re using a type: html rich text input, is that right? Since the text in those inputs is saved as HTML, CloudCannon encodes special characters like & to ensure there is a clear differentiation between the user’s input and the HTML that is generated (e.g. so that a user’s <s and &s aren’t interpreted as opening tags and escape sequences respectively).
If you do want to save this text back as HTML, you’ll need to make sure your templating code handles that by decoding it before render. Alternatively, you could consider using _inputs config to turn this into a plain text input (no HTML allowed).