Permissions issue in the pages section "Add" button

[bvdputte]

Describe the bug
The add() method in a pages section only checks global pages create permission. The consquence is that the Add button is never shown if the role/editor does not have this permissions. Nonetheless, if a role/user has permissions to create a page (can be template specific) in that pages section, he should be able to Add it from the pages section.

More info about this in the forum: https://forum.getkirby.com/t/kirby-permissions-to-give-role-permissions-to-manage-content-of-1-blueprint-only/23716

Expected behavior
A user should be able to add a page to a pages section if he has permissions to generate that page, even when his global "pages create" permission is false.

Kirby Version
3.5.7.1

[afbora]

I think this issue can be fixed in 3.7.0 that includes refactored sections with fiber.

[bvdputte]

@afbora , I've just checked with the latest branch of develop (3.7.0-rc1 and a few commits further), and I still can't make it work? Any chance to get this in the release please?

It's an annoying issue and it's blocking further development. Apparently there are other waiting for this as well (see forum link).

thx!

[afbora]

Unfortunately, this is not so easy to solve. A case that concerns the blueprint of both sections and pages. We even have a concept for it: https://discord.com/channels/525634039965679616/985503322259722321/986529133347631114

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. This is for us to prioritize issues that are still relevant to our community. It will be closed if no further activity occurs within the next 14 days. If this issue is still relevant to you, please leave a comment.

[bvdputte]

Another question about this popped up on the forum: https://forum.getkirby.com/t/remove-the-add-block-button-for-permissions/29017

[texnixe]

I think we should reopen this...

[lukasbestle]

I reopened the issue because it was closed by our stale bot when we still had it configured to close issues even when they have become stale because of us, not because of the issue author. Because there is demand for a fix, we of course need to have an open issue.

Unfortunately I cannot promise a quick fix for this, but at least we won't forget about this then. :)