Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
The contributed module Rabbit Hole allows you to prevent entity pages like "/storage/1" from being publicly accessible. To use Rabbit Hole with a particular entity type, a bridge module must be enabled to provide support for that entity.
Proposed resolution
Create an integration module for Rabbit Hole and Storage.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | storage-3220934-2-rabbit_hole.patch | 1.81 KB | Les Lim |
Comments
Comment #2
Les LimPatch attached.
Comment #3
mandclu CreditAttribution: mandclu at Northern Commerce commentedI don't mind integration with rabbit hole, but maybe instead we should have a permission to view storage entities, per bundle?
Comment #4
Les LimSure, that's a good feature for the base module. That doesn't necessarily replace the usefulness of Rabbit Hole integration; with Rabbit Hole, I can configure per-bundle redirects, so I could send people directly to a View that consumes those storage entities, for example. Rabbit Hole also lets you define behaviors on a per-entity basis, if you choose to let it be that granular.
Comment #5
Les LimIf you prefer, I can publish this to its own project namespace as well.
Comment #6
mandclu CreditAttribution: mandclu commentedGiven the small amount of code required, I'm actually thinking maybe this makes more sense directly in the main module.
Comment #8
mandclu CreditAttribution: mandclu commentedMerged in the code directly to the main module, with an added check if the rabbit hole service exists.