Saas CMS LongString TextArea
Adding an optional toggle to allow Longstring properties to display as Text areas for CMS editors would be useful.
Danyaal Ahmed
shared this idea
Thank you for your suggestion! We have this on the roadmap, however not limited to LongString properties. As the regular string supports up to 255 chars it applies to this type as well.
-
Andrew Markham
commented
Not having the textarea is very limiting. We are starting a new build and we have multiple instances in which we require this.
- robots.txt
- csp settings
- introduction text that we don't want to be styled
- SEO meta data.This isn't possible with the longstring as it stands, so we have to fallback to using the minimal version of the richtext editor, which causes confusion for the editors.
-
Shivam Barve
commented
Will this LongString TextArea be a recommended option to be used where we need to enter content including embedded HTML code (HTML, Javascript, Style, etc.)? Currently we can use Single-Line Text property but the authoring experience is not desirable.
-
Mike Potter
commented
Adding my vote to this. Our client was shocked that this wasn't an option. We've had to make all plain-text multi-line description fields into XHTML types, which is very confusing to the content editors and potentially can cause data problems if the editors use any of the WYSIWYG buttons. Also complicates the front-end that has to parse this HTML into plain strings.