Skip to content
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

Closed
Yinzy00 opened this issue Sep 6, 2024 · 4 comments
Closed

V13.5-RC Content fields to stay disabled when save and publishing #17019

Yinzy00 opened this issue Sep 6, 2024 · 4 comments

Comments

@Yinzy00
Copy link
Contributor

Yinzy00 commented Sep 6, 2024

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

  1. Add a mandatory text field to a doctype
  2. Add a non mandatory text field to that doctype
  3. Create an instance of that doctype
  4. Save and publish without value
    => 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.

Copy link

github-actions bot commented Sep 6, 2024

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'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 🤖 🙂

@Yinzy00
Copy link
Contributor Author

Yinzy00 commented Sep 6, 2024

Fixed in: #17018

@Yinzy00 Yinzy00 changed the title Content fields to stay disabled when save and publishing V13.5-RC Content fields to stay disabled when save and publishing Sep 6, 2024
@Yinzy00 Yinzy00 closed this as completed Sep 10, 2024
@laimonas
Copy link

laimonas commented Sep 13, 2024

I have upgraded to latest

validation

@Yinzy00 @nielslyngsoe any thoughts why this is still happening?

@laimonas
Copy link

Created new issue here
#17054
I think one difference that our page can vary by culture

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