I use specific schema per permission groups. I am able, from the setting page (admin/graphql-authentication/settings) to access individual permission group (/admin/graphql-authentication/settings/user-group/1) and assign a schema. I can see these permissions on the main setting page (back to admin/graphql-authentication/settings).
The problem is the following : when saving the main setting page to apply the changes, all individual permissions are not applied and simply wiped from the control panel. This appears to be a frontend CP bug as this simple vibe-coded patch does the trick. It's not meant to be solid fix.
here is what the robot has to say on the patch :
"
GraphQL Authentication’s main settings form lists per–user-group schema configuration in read-only table rows, but those values are not included in the form POST. Saving the page therefore overwrites plugin settings with an empty granularSchemas payload and clears every group’s schema in the database. The fix is a Composer patch to the plugin’s users.twig template that adds hidden inputs for each row (mirroring the keys the settings controller already expects: schemaName, siteId, allowRegistration, and the query/mutation maps) so a full settings save round-trips existing granular configuration.
"
graphql-authentication-preserve-granular-schemas.patch
Thanks!
I use specific schema per permission groups. I am able, from the setting page (admin/graphql-authentication/settings) to access individual permission group (/admin/graphql-authentication/settings/user-group/1) and assign a schema. I can see these permissions on the main setting page (back to admin/graphql-authentication/settings).
The problem is the following : when saving the main setting page to apply the changes, all individual permissions are not applied and simply wiped from the control panel. This appears to be a frontend CP bug as this simple vibe-coded patch does the trick. It's not meant to be solid fix.
here is what the robot has to say on the patch :
"
GraphQL Authentication’s main settings form lists per–user-group schema configuration in read-only table rows, but those values are not included in the form POST. Saving the page therefore overwrites plugin settings with an empty granularSchemas payload and clears every group’s schema in the database. The fix is a Composer patch to the plugin’s users.twig template that adds hidden inputs for each row (mirroring the keys the settings controller already expects: schemaName, siteId, allowRegistration, and the query/mutation maps) so a full settings save round-trips existing granular configuration.
"
graphql-authentication-preserve-granular-schemas.patch
Thanks!