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.

Sign up for GitHub

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

Jump to bottom

Admin UI Force Unlock button on create for auth collections #48

Closed
DanRibbens opened this issue Feb 2, 2021 · 0 comments
Closed

Admin UI Force Unlock button on create for auth collections #48

DanRibbens opened this issue Feb 2, 2021 · 0 comments
Assignees
@DanRibbens

Comments

@DanRibbens
Copy link
Contributor

Bug Report

The "Force Unlock" button is visible on create for auth collections.

Expected Behavior

The button should be disabled so you can see where it is for later use.

Current Behavior

The button is not disabled and when clicked it and it makes a non-sense request to unlock a user without sending the needed email address, returning a 500 status.

Possible Solution

Instead of disabling, we could hide it. I prefer to disable it for UX.

Steps to Reproduce

  1. Have a collection that includes auth
  2. From the admin panel, go to create a new item in the collection
  3. Click the "Force Unlock" button

Detailed Description

payload v0.2.9
@DanRibbens DanRibbens added the bug label Feb 2, 2021
@DanRibbens DanRibbens mentioned this issue Feb 3, 2021
Merged
3 tasks
jacobsfletch added a commit to jacobsfletch/payload that referenced this issue Oct 15, 2023
@jacobsfletch
fix: supports custom fields payloadcms#41 (payloadcms#48)
8271c20
denolfe pushed a commit that referenced this issue Oct 24, 2023
@DireWolf707
docs: add default value for GCS_CREDENTIALS (#48)
8b186db 
without default value, it gives error in payload admin page (in console of browser)

caught SyntaxError: "undefined" is not valid JSON
    at JSON.parse (<anonymous>)
    at ./src/payload.config.ts 

as envs are not availabe in payload admin GCS_CREDENTIALS gives undefined
resulting JSON.parse(undefined) raises this error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DanRibbens DanRibbens

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DanRibbens