One of my favorite features of Drupal is the user access control experience. Drupal has a robust permission and role (access control list) API that allows for fine-tuned control of what users can and cannot do. Drupal developers end up interacting with Drupal’s access system in one way or another. Every project has some request to enhance or alter how normal access works. When this happens, some modules (see Field Permissions) provide no-code solutions for the end user. Other times the developer taps into Drupal hooks and writes code to adjust the access result.

A common use case I have experienced is allowing content from a specific content type to be accessible to privileged users (like paywalled content.) Drupal core doesn’t provide granular permissions for viewing the content of specific content types. You need to extend Drupal and use the hook_node_access hook to alter the default user access.

I always liked rails templating collections that allowed us to quickly compose ruby apps. Now the same is possible for Hanami

Dear community

The GNU Health federation community server (federation.gnuhealth.org) has been updated! These are some of the main improvements:

– NGINX and WSGI: The Hospital Management component instance is now running behind uWSGI and NGINX.

– HMIS 4.2 Release Candidate 2: We are very close to HMIS 4.2 stable. This pre-release version will help us to test the upcoming features and find bugs before the release. 🙂

– Secure connection: You can test the demo web client using TLS. Please check the demo database section on the GNUHealth Wikibooks.

– Thalamus, the GNU Health Federation message and authentication server still runs on Gunicorn, also using https.

More info and resources:

• Wikibooks: https://en.wikibooks.org/wiki/GNU_Health
• GNUHealth documentation portal: https://www.gnuhealth.org/docs/
• Mastodon:  https://mastodon.social/@gnuhealth
• Matrix: https://app.element.io/#/room/#gnuhealth-space:matrix.org

Happy and healthy hacking!

Luis