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'.
BecauseAvailableGloballyis defined as default true (Boolean(1)) in $db, setting the$default_global_elementsconfig to false has no effect (AvailableGloballyis always checked for new elements).AvailableGloballyis always the default value as set in$dbfor new blocks.Setting the
$default_global_elementsconfig tofalsehas no effect whatsoever.Also hardcoding
AvailableGloballyto befalsefrompopulateDefaults()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 seemspopulateDefaults()does get called when adding/creating a new object via the GraphQL 'resolver'.