-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Input validation for shortcode block #10790
Comments
As mentioned in #7357 (comment), |
From my understanding, I don't think this is an issue specific to the Shortcode block or Gutenberg. For example, in the Classic Editor, you can simply enter a URL that is allowed as an oEmbed provider and it will be converted to embedded content in the front end. I think this is expected behavior in WP core, so I'll close this issue, but if there's anything I've missed, please comment. |
Describe the bug
If we add an URL into the shortcode block, it accepts it and the link is displayed in the site front-end.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To get some error message when something that is not a shortcode is added.
Screenshots
Back-end:
Front-end:
Desktop (please complete the following information):
Additional context
Reported originally in the comments on #7357 when I was testing something else
The text was updated successfully, but these errors were encountered: