Recently Browsing 0 members
No registered users viewing this page.
for a project I have pages with different “content areas“ that can be edited only by specific user roles. In the past I setup a fieldset (tab) containing all the fields that should be available to only one specific group of users and set the fields' view and edit permissions (in the Access tab) accordingly. The result was as expected: Users assigned to the specific role could see the tab, click on it, edit content, users without the role could not see the tab. After updating this installation to 3.0.148 yesterday I wanted to setup another tab following the same principle, but I have no "Access" tab for the fieldset to limit access to the specific role. I even tried cloning an existing (and still working) fieldset. The existing fieldset has some template overrides (screenshot attached) that lead to the desired behaviour, but I am not able to reproduce these settings because there is not "Access" tab for my fieldset in template context either.
Is this a bug in 3.0.148? Has the fieldset fieldtype changed? Am I missing anything here?
I am glad to hear from you guys.
this is the first time I'm using ProcessWire.
I thought I get how fields, template and pages work, but when I create a template in the CMS, it doesn't generate any file in site/templates/
Then I thought I might need to create a blank file myself manually on the FTP (which already seems odd to me).
Once I did that, I tried to add fields to the template but again, doesn't write to the php file.
When I create a new page and apply said template to it, the page stay blank.
AFAIK the mod_rewrite of the apache is on and I went for the worst case scenario described here https://processwire.com/docs/security/file-permissions/ and set all file-permissions for future files to 0666 and folders to 0777 in the config.php
What am I not getting and what am I doing wrong?
Help is appreciated, stay save everybody,
Having just wasted the best part of a day debugging an access issue because I hadn't realised that page-edit-created negated any related page-edit permissions, could I suggest that a note to this effect is included in the default title. I have amended the title on my system to read:
Edit only pages user has created (IMPORTANT: This will negate any related page-edit permission - including permissions granted to a user by other roles) ..although it may be possible to make it briefer while not losing clarity and impact.
Is it possible to let people edit a page without having to have a user-role?
My case is the following:
Visitors fill in a form (Formbuilder) which is saved to pages. They get a confirmation email which could contain a unique editing link. In case they need to update some information, they can click on this link, edit the fields and save.
Am I totally off? Is there a better practice?
I'm using this kind of setup (https://processwire.com/blog/posts/language-access-control-and-more-special-permissions/#language-page-edit-permissions) in order to control the page edit permissions. Now I'm wondering if it's possible to hide the "none-ediable" language-tabs instead of striking them through.