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

Mandatory Image not validating after first time failure #11057

Closed
jawood1 opened this issue Sep 8, 2021 · 3 comments
Closed

Mandatory Image not validating after first time failure #11057

jawood1 opened this issue Sep 8, 2021 · 3 comments

Comments

@jawood1
Copy link

jawood1 commented Sep 8, 2021

Which exact Umbraco version are you using? For example: 8.13.1 - don't just write v8

8.16

Bug summary

I initially started getting this issue most recently on an existing install that I had upgraded from 8.14.1 to 8.16 with a slight difference in the outcome to a fresh installation.

On upgrade I could no longer save and publish the page if the the image field was mandatory even and I applied an image before the validation error occurred.

I then thought to test this using a fresh install of Umbraco 8.16 to see if it was just me or a bug.

On the fresh install when I added a mandatory image field then saved and published without an image I got the validation error. Once I added the image it wouldn't allow me to save without refreshing the page.

Specifics

I've tested this on the latest versions of Firefox and Chrome.

Looking in the console logs on initial save without the image I get a 400 error. Once the image is added it won't allow me to save and no further logs are produced.

image

Steps to reproduce

  1. Save and Publish the page without an image field being filled

on inital save

  1. Add an image, Validation error isn't cleared and the page won't save.

image

Expected result / actual result

Once the image is added for the page to save.


This item has been added to our backlog AB#14294

@emma-hq
Copy link
Contributor

emma-hq commented Sep 10, 2021

Hiya @jawood1

Thanks for reporting this. I'll take a look and reproduce and tag. If it's regression, which I suspect given your report, I'll label it as such and we'll look at cherry picking the solution. I'll let you know what happens!

Emma

@nul800sebastiaan nul800sebastiaan added state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks status/regression labels Oct 5, 2021
@nul800sebastiaan
Copy link
Member

Thanks @jawood1 - we'll have to have a look, I can reproduce. The workaround for now is to Save first and then Save & Publish, then it will indeed work properly.

11057.mp4

@nul800sebastiaan
Copy link
Member

Cherry picked for 8.17.1 in da48f84

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

5 participants