Skip to content

RTE custom regex validation fails #19044

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tomvanenckevort opened this issue Apr 15, 2025 · 3 comments
Closed

RTE custom regex validation fails #19044

tomvanenckevort opened this issue Apr 15, 2025 · 3 comments

Comments

@tomvanenckevort
Copy link
Contributor

Which Umbraco version are you using?

13.8.0

Bug summary

When enabling custom validation on a doc type property that uses the RTE (TinyMCE) property editor, the validation will fail because it validates the JSON value, rather than the markup entered in the RTE.

Specifics

No response

Steps to reproduce

  • Create a new doc type with a property that uses the built-in Richtext editor data type.
  • Enable validation for that property and set it to use custom validation.
  • Enter a regular expression, for example this one that will check that the length does not exceed 250 characters: ^.{0,250}$
  • Save the doc type and create a new node using this doc type.
  • Enter some text in the RTE, but make sure it does not exceed 250 characters.
  • Try to Save & Publish the node and see the validation failure pop up.

Image

Expected result / actual result

  • Expected: when the content in the RTE matches the specified regular expression, it should save & publish without errors.
  • Actual: the node fails to save & publish.
Copy link

Hi there @tomvanenckevort!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@NguyenThuyLan
Copy link
Contributor

Thanks @tomvanenckevort , I was able to reproduce it on v13.8.0 and v15.4.0-rc, both on tiptap and tinycme

@Migaroez
Copy link
Contributor

Migaroez commented May 8, 2025

Fixed #19045 and forward ported to 16 #19280

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants