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

Validation fails on user content_editor field editor set but disabled #278

Closed
rhukster opened this issue Apr 20, 2021 · 2 comments
Closed
Assignees

Comments

@rhukster
Copy link
Member

Edge case, but ran into this while testing nextgen-editor. I had an overridden content_editor setting in my user set to nextgen-editor, but then disabled the plugin. I then got a blueprint validation failure because the valid 'options' for this field as defined by the blueprint are provided by a function that has an event that allows nextgen to add itself to the list. With the plugin disabled it can't add itself, so is not available, you get the idea.

We can discuss offline for solutions, but wanted to create a ticket to keep track of it.

@mahagr
Copy link
Member

mahagr commented Apr 21, 2021

Needs also flex users enabled in system configuration, as well as session_user_sync in login, turned on.

@mahagr
Copy link
Member

mahagr commented Apr 21, 2021

The error happens because $object->update() is meant to be used for user input and has validation. Though that said, there is no alternative method to bulk update fields without having a check...

@mahagr mahagr transferred this issue from getgrav/grav Apr 22, 2021
@mahagr mahagr added the bug label Apr 22, 2021
mahagr added a commit that referenced this issue Apr 22, 2021
@mahagr mahagr added the fixed label Apr 22, 2021
@mahagr mahagr closed this as completed Jul 30, 2021
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

2 participants