Jump to content

Search the Community

Showing results for tags 'user access'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. Hi! I think answer onto this question could be useful for all PW newbies with little PHP experience like myself... Let's imagine the following "typical" scenario: We have 2 user types of logged-in users: - user-type-1 - user-type-2 Each user type may have any number of actual users. The difference btw these two types is in view access to pages: - page-type-1 can be viewed only by users from user-type-1 - page-type-2 can be viewed only by users from user-type-2 - page-type-3 can be viewed both by users from user-type-1 and user-type-2 - page-type-4 can be viewed only by one user independently on its type (let's say that it is sensitive profile info page. Or individual mailbox page.) Also we have unauthorized users (not logged-in) that should have view access to sign-up, sign-in and general info pages. Looks like PW has all needed to enable scenario above, as key ingredients are in place: - API ($user, $session) - pw access management (defining users, roles, permissions) - pw template properties (defining roles that can access pages) But how to put it together and make work is a challenge for newbie like me...) Please can someone help? I'd even suggest to make kind of sample project with step-by-step tutorial as this should be a topic of common interest...I believe.
  2. I have stumbled many times for this: I have added new roles (usually created through API) I go to access tab of "extranet_home" template I add view permission for these new roles for that template I test this and user cannot access extranet home page. This problem is because "view" access need to be added in two places: template access tab and also role needs "view pages" permission. It would be great that it wouldn't be possible to add view access on tab, if that role doesn't have view access at all. Or other solution (not sure if I understand all the side effects): remove view permission all together. There is no create page permission either, only setting on access tab.
  • Create New...