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

$default_global_elements config setting has no effect #42

Open
micschk opened this issue Nov 18, 2021 · 0 comments
Open

$default_global_elements config setting has no effect #42

micschk opened this issue Nov 18, 2021 · 0 comments

Comments

@micschk
Copy link
Contributor

micschk commented Nov 18, 2021

Because AvailableGlobally is defined as default true (Boolean(1)) in $db, setting the $default_global_elements config to false has no effect (AvailableGlobally is always checked for new elements).

AvailableGlobally is always the default value as set in $db for new blocks.
Setting the $default_global_elements config to false has no effect whatsoever.

Also hardcoding AvailableGlobally to be false from populateDefaults() has no effect, seems the value always gets set to the db field's default value. Could this have something to do with GraphQL? I've checked but it seems populateDefaults() does get called when adding/creating a new object via the GraphQL 'resolver'.

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

No branches or pull requests

1 participant