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

Save as Copy errors not shown to the user #11722

Closed
3 tasks done
allanmoso opened this issue Feb 18, 2022 · 0 comments · Fixed by #11761
Closed
3 tasks done

Save as Copy errors not shown to the user #11722

allanmoso opened this issue Feb 18, 2022 · 0 comments · Fixed by #11761
Labels

Comments

@allanmoso
Copy link

Preflight Checklist

Describe the Bug

When Save as Copy is performed in the Item Page while a user does not have the Create permission or if there is a Unique value error for one of the fields there is no visual indicator to the user that an error has occurred; it can seem like the page has already saved, but it didn't due to the error.

(This issue does not occur for Required field validations, however.)

To Reproduce

  1. Create a collection with a unique value field.
  2. Make sure that the duplication settings for the collection includes the unique value field.
  3. Create a new record for the collection.
  4. Edit the new record (keeping the unique value field unchanged) without saving yet.
  5. Use the alternate save option "Save As Copy".

Errors Shown

There is no error shown to the user but you can check the network log for the unique value validation error that should've been shown to the user.

What version of Directus are you using?

9.5.2

What version of Node.js are you using?

17.3.0

What database are you using?

Postgres 13

What browser are you using?

Chrome

What operating system are you using?

Windows

How are you deploying Directus?

Docker (local development) and Heroku (for Test, Prod)

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

Successfully merging a pull request may close this issue.

2 participants