This module allows you to control access to views based on configurable conditions. It also enables controlling the visibility of fields and filters within views based on these conditions. This is particularly useful for multi-site setups or shared codebases where sites need differentiated access to views.
A Drupal module that allows you to control access to views based on configurable conditions.
Overview
Views Access Conditions provides a flexible way to control when views are accessible on your Drupal site. This module extends Drupal's views access plugin system to include conditional rules, making it easy to control access to views based on various conditions.
In version 2.1+ users can also control what fields and filters are visible in their views based on conditions. Contextual filters can be enabled/disabled based on conditions as well.
But why?
The benefit of this approach is for multi-sites, or shared codebase platforms, that share configuration across multiple sites but want some flexibility in control of when views are accessible. For example, if there are two sites sharing the same codebase, Site A and Site B, and only Site B needs a particular view to be accessible then using views access plugins, we are able to configure access based on a condition - this could be one provided by core, the contrib space, or something custom. This way both sites can still share the same configuration, as the access conditions are stored in config, but the conditions are evaluated per-site.
Requirements
- Views
Installation
1. Download the module:
You can download the module using Composer:
composer require drupal/views_access_conditions
2. Enable the module:
After downloading, enable the module using Drush or the Drupal admin interface:
drush en views_access_conditions
Or, enable it through the admin interface at /admin/modules.
Configuration
The module offers a settings page to configure which conditions are available for use with restricting views access.
Usage
1. Navigate to edit a view
2. Look for the "Access" section
3. Select Conditions
4. Add one or more conditions that determine when the view should be accessibled
5. Save the view configuration
Extending the module
Developers can alter the available conditions using the provided hook:
/**
* Implements hook_views_access_conditions_available_conditions_alter().
*/
function hook_views_access_conditions_available_conditions_alter(array &$conditions, ?FormStateInterface $form_state = NULL, ?string $form_id = NULL): void {
// Remove specific conditions
$conditions_to_remove = [
'language',
'request_path',
];
$conditions = array_diff_key($conditions, array_flip($conditions_to_remove));
}
Contributing
Contributions are welcome! If you would like to contribute to this module, please follow these steps:
1. Open an issue on the issue tracker
2. Create a Merge Request or add a patch
3. Mark your issue as Needs Review.
License
This module is licensed under the GPL-2.0+ license.