Jump to content

Recommended Posts

Posted

Hello,  I have just upgraded to v2.8.62 and all was good until I set up permissions for an editing user.  I restricted the user to editing two templates, and only a few fields used by those templates on two pages.  The fields contain data, and the two pages are displayed correctly when viewed by myself as superuser, or by the editing user.  The problem occurs viewing the two pages when logged out, which results in some empty fields.  There doesn't seem to be any logic to which fields are empty,  but the errors are consistent.  The data isn't lost, because the pages display properly if I login again.  I have disabled cache for the relevant templates; deleted the pagerender cache files and cleared browser cache.  I also tried viewing on different devices, which all displayed the same fault.   Now I am stuck!

Posted

Hi @devonic and welcome to the forum.

51 minutes ago, devonic said:

but the errors are consistent

Could you post the errors? Did you set access restrictions on just the templates or on the fields themselves?

  • Like 1
Posted

On the fields that you have set access restrictions for, on the "Access" tab try checking the checkbox shown below:

2017-11-06_090446.png.0e22726faf4a02ebf5c85f182cc33629.png

  • Like 2
Posted

Thank you for your help, SamC and Robin S - much appreciated.  I can't post the errors as such, because they aren't logged.  I set access restrictions on the templates and fields, and editing was available to the user as intended.  My problem was with front-end viewing of the fields and this was solved by Robin's suggestion.   I seem to be going around in circle's though - the template shows that the role allocated to the user has permission to edit, but now when the user logs in and views the tree, only the view button is available, so he can no longer edit the page.  

Posted

I’ve never used the access settings on fields, only on entire templates so I’m not a great deal of help here. Maybe set restrictions on only the templates first, then try it. If it works as intended, try add a restriction to a field within one of those templates, then try again.

I’d just be trying a load of combinations the old fashioned way until it worked. I’m sure another member would have a quicker solution though.

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...