-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
V13.5-RC Content fields to stay disabled when save and publishing #17019
Comments
Hi there @Yinzy00! 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 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 🤖 🙂 |
Fixed in: #17018 |
I have upgraded to latest @Yinzy00 @nielslyngsoe any thoughts why this is still happening? |
Created new issue here |
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
v13.5.0 RC
Bug summary
We discovered that when attempting to save and publish with invalid fields, those fields remained disabled.
We tested this with text fields, media pickers, block lists
Specifics
No response
Steps to reproduce
=> After validation text fields (and blocklist, mediapicker, ...) will stay disabled
Expected result / actual result
Fields should be disabled while save and publishing but should be enabled after validation.
The text was updated successfully, but these errors were encountered: