Then you probably cannot override the user yaml settings and would have to turn the logic around, i.e. generelly allow creating pages and disallow it on a per blueprint setting.
This definitely works and re-enables the update option as expected. Maybe someone from the team can figure this out and let us know if it is intended or not.
Mmh, actually turning the logic around does not work either. Seems like there is no way of tackling this at the moment other than maybe with a hook.
The Github issue is about the “Add” button still being visible and the user only getting a message about not being allowed to create pages after filling out the form. However, with the following setup while logged in as an editor, I don’t even get that warning and am actually able to create pages.