Jump to content
LostKobrakai

ProcessAccessOverview

Recommended Posts

I did another quick module, which plugs something I always kinda missed in ProcessWire. It's just a raw overview over the access management from the templates. Nothing fancy, but useful. The visible roles and the visibility of system templats can be setup in the modules settings.

post-874-0-29254000-1426194348_thumb.png

I'll add this to the modules directory later. But for now it would be great to hear if anyone is missing anything or if someone does have a better idea how to name the module.

12.03.15: Renamed the module and fixed wrong information for superusers and inherited rights from the required guest role.

GitHub: https://github.com/LostKobrakai/ProcessAccessOverview

  • Like 27

Share this post


Link to post
Share on other sites

I love it - very handy!

Just a couple of small things.

  1. Need a nice icon for the module to show up under the Setup menu
  2. I would use the same labels as the template access tab, ie: VIEW PAGES, EDIT PAGES, CREATE PAGES, ADD CHILDREN and also in that same order.
  • Like 1

Share this post


Link to post
Share on other sites

Nice one! For larger installations and/or a larger set of roles this will really be a boost. As for naming, I'd root for "Permissions Overview" :)

Share this post


Link to post
Share on other sites

Looks really nice!

But what about the "guest" user? It's not on the screenshot but it's created by default and maybe interesting to see its rights in comparison :)

Share this post


Link to post
Share on other sites

Nice one! For larger installations and/or a larger set of roles this will really be a boost. As for naming, I'd root for "Permissions Overview" :)

I did think about this, but wanted to avoid confusion with Permissions itself. This would be more about "template access" but it would be kinda long with "overview" appended to it. 

Looks really nice!

But what about the "guest" user? It's not on the screenshot but it's created by default and maybe interesting to see its rights in comparison :)

You can change the visible roles in the modules settings. The guest user was not so useful for me, as only the viewable tab would be from use. All the others can't be assigned to the guest role. I did this, too, because I have used roles before to differ between different frontend-only user groups, so these roles could be excluded as well. 

Edit: Added the info about the settings in the intro post as well.

  • Like 1

Share this post


Link to post
Share on other sites

Updated the module to incorporate an icon and settings to enable system templates, which are now hidden by default.

  • Like 1

Share this post


Link to post
Share on other sites

I've updated the module, I'll update the Screenshot above, too:

  • Templates now show access rights inherited from parents, which are in the parentTemplates array. 
  • Templates show up in the "Free Inherited Access" if they don't define special parentTemplates or at least one of the defined ones does not lead to a template, which defines access on it's own.
  • A checkbox in the settings to enable, that the paths of inherited access' is shown. By default this info is reachable via mouse over on the icon.
  • A small description below the table to make it clear what's going on.

I would also like to have some input regarding these features. First I'd welcome any recommendations about the descriptions (mouseover / below the table). Secondly I'd like to know what you'd find more understandable regarding the paths. E. g.:

products - Defines Access
category - Must be child of products, does not define access
product  - Must be child of category, does not define access

The row for product could display either "products > category", which it does currently, or it could show "products > category > product", which would show the current template's name, too.

  • Like 2

Share this post


Link to post
Share on other sites

Updated the module to show the right access rights for superusers (can access everything no matter what) and access rights inherited to every user by the guest role. Also changed the modules name and will post it now to the modules directory.

  • Like 3

Share this post


Link to post
Share on other sites

Ho did I miss that? Looks awesome, added it to my ever growing list of modules I definitely have to check out in depth.

Share this post


Link to post
Share on other sites

I pushed some updates to prevent infinite loops, if a template can be his own parent, and improved the search of possible parent-template constellations.

Share this post


Link to post
Share on other sites

Pushed a small update, which removes path-details when access rights are not available, as it would falsely suggest that only under this path a role would have no access. Also added a bit of a description about how templates are distributed over the tabs. Also made the module officially 2.6 compatible.

  • Like 4

Share this post


Link to post
Share on other sites

@LostKobrakai Hi, is this module 3.x compatible? I'm asking this 'cos it is not stated here: https://modules.processwire.com/modules/process-access-overview/

Checking out Ryan's blog post on access control/permissions I gather that nothing has changed since ProcessWire 2.7 in this regard, so the module should be ok with PW 3 I guess, but to make sure I thought I'd ask...

Share this post


Link to post
Share on other sites

I'm not sure, I haven't used in in a while. But I haven't added the 3.0 flag for a purpose, because the module was build before the ability to assign additional permissions on a per template level was added. I'm not sure if the module does take those into account properly.

  • Like 1

Share this post


Link to post
Share on other sites

I see, thanks!

6 minutes ago, LostKobrakai said:

because the module was build before the ability to assign additional permissions on a per template level was added

Any plans on updating it? (PW3 & the above mentioned...)

Share this post


Link to post
Share on other sites
10 hours ago, LostKobrakai said:

But I haven't added the 3.0 flag for a purpose, because the module was build before the ability to assign additional permissions on a per template level was added. I'm not sure if the module does take those into account properly.

I tried the module a bit in PW3 and it works well - it's a really handy module and I wish I started using it sooner. I think the permission overrides per template only apply to the sub-permissions of page-edit (page-move, page-delete, etc) and these won't affect the module because those sub-permissions aren't displayed in the tables.

One issue I came across is that where a template has a numeric name ("404" being an obvious one) the edit link to the template is not displayed properly in the table. Have created an issue on GitHub with a proposed fix.

I also thought that where the the 'muted' class is used the text colour is too faint.

2017-05-19_105716.png.acff86c49ae9c627c74c2e01e1ec82c5.png

 

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for the report @Robin S

6 hours ago, Robin S said:

these won't affect the module because those sub-permissions aren't displayed in the tables

However, we are missing them, aren't we?

Anyway, this module with extended features to support permission overrides per template would be a great addition to the core modules.

  • Like 1

Share this post


Link to post
Share on other sites

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.

  • Similar Content

    • By MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...