Editing Permission Not Working - Question | JoomShaper

Editing Permission Not Working

RL

Riku Lahteenmaki

SP Page Builder 10 months ago

I have given a user group 'Edit' and 'Edit State' permissions on a page's permission settings.

Calculated Setting for this user group in now 'Allowed'.

Then I assigned a user to this user group to enable editing of this single page, but not any other pages.

But when the user logs on the site in the front-end and tries to open the editor, this error happens:

403 You don't have permission to edit this page.

Only when the user is assigned to the 'Editor' group is the editing allowed. But then, the user can also edit all other pages, which is not acceptable.

0
11 Answers
RL
Riku Lahteenmaki
Accepted Answer
10 months ago #179593

I found the solution to this permissions problem:

The editing permission can be limited to 'Edit Own' -> 'Allowed', which is the default setting in all Joomla components.

You cannot (easily) limit a user group's edit permission to a specific page, but you can limit it to a single user.

But in SPPB, you cannot set the page owner in the page settings. You have to do it in the database, by finding the user's id, and then change the value of the SPPB page's 'Created by' column.

Now, when the user logs on to the site, he/she can edit the SPPB pages that were 'created by' this user, but not any other pages.

PLEASE UPGRADE SP PAGE BUILDER TO ALLOW CHANGING OF PAGE CREATOR IN THE PUBLISHING OPTIONS, LIKE IN JOOMLA ARTICLES.

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 10 months ago #179478

Hello Riku Lahteenmaki,

Apologies for the inconvenience. SP Page Builder uses Joomla's core ACL system, which operates hierarchically. If a permission, such as 'Edit' or 'Edit State,' is set to "Not Allowed" at the global level for a user group, this restriction cannot be overridden at the page or item level within SP Page Builder. Even when permissions are explicitly set to "Allowed" for a specific page, the global "Not Allowed" setting will take precedence.

This is an inherent characteristic of Joomla ACL and applies to SP Page Builder as it adheres strictly to Joomla's permission structure.

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 10 months ago #179481

Hi there!

Sorry for your experience.

Would you please give me your admin access to check the issue for you? Kindly, keep a full site backup before sharing the credentials.

Best Regards

0
RL
Riku Lahteenmaki
Accepted Answer
10 months ago #179485

See the details in the hidden area.

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 10 months ago #179504

Hello Riku Lahteenmaki,

Upon reviewing your settings, I noticed that the 'Edit' permission for this user group is currently set to 'Inherited' in the global settings tinyurl.com/276u87ku. As a result, it defaults to "Not Allowed." This means that even though you have set the 'Edit' permission to 'Allowed' for a specific page, it will not take effect due to the global restriction.

To resolve this issue, please update the 'Edit' permission for this user group to 'Allowed' at the global level. This will enable the permission to be applied at the individual page level as intended.

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 10 months ago #179583

By "global level," I am referring to the permissions set under System -> Global Configuration -> SP Page Builder -> Permissions tinyurl.com/276u87ku in Joomla, which define the baseline permissions for the user group across the entire site. These settings affect all components and extensions, including SP Page Builder, unless overridden at a more specific level.

When you set the 'Edit' permission to "Allowed" in SP Page Builder's options, it applies to all pages managed by SP Page Builder. Unfortunately, Joomla ACL does not support granting 'Edit' permissions for individual pages while restricting it for others without affecting the global or component-level permissions.

0
RL
Riku Lahteenmaki
Accepted Answer
10 months ago #179579

Please can you clarify what you mean by the 'global level'.

If I set Edit permission for the group in SP Page Builder options, then the user in this group can edit all Page Builder pages, which cannot be allowed in our site.

0
RL
Riku Lahteenmaki
Accepted Answer
10 months ago #179591

I can prevent the editing permission of a SP Page Builder page for a user group by selecting 'Edit' -> 'Denied' in the page's permissions settings.

Is that really the only way to limit SPPB editing permissions?

Should I set each individual SPPB page's permission for the specific user group?

That would be rather laborious.

0
RL
Riku Lahteenmaki
Accepted Answer
10 months ago #179604

I am still wondering, why SPPB behaves differently from Joomla articles component.

With Joomla articles, I can create a group, which has editing permission to an articles category. At the com_content level, there is Edit -> Not Allowed for this user group.

Now, a user who belongs to this group can edit all the articles within the category, to which the user group has Edit permission. This user certainly cannot edit any other articles, which do not belong to the specific category.

This is not possible with SP Page Builder. SPPB pages do not seem to inherit permissions from their categories.

Why is SPPB different from Joomla articles component?

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 10 months ago #179639

Thank you for sharing this workaround! It’s indeed a practical approach to manage editing permissions in SP Page Builder. Your suggestion to include a feature for changing the page creator directly within the publishing options, similar to Joomla articles, is valuable feedback. I’ll ensure it’s communicated to the development team for consideration in future updates.

0
RL
Riku Lahteenmaki
Accepted Answer
10 months ago #179652

Please can you elaborate on the SPPB categories permission issue (see my message above).

In Joomla articles component articles inherit permissions from their categories, but SPPB pages do not. Why is this different in SPPB?

0