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.

CommentFileSizeAuthor
#2 storage-3220934-2-rabbit_hole.patch1.81 KBles lim

Comments

Les Lim created an issue. See original summary.

les lim’s picture

les lim
he/they
Primary language English
commented
Status: Active » Needs review
StatusFileSize
new storage-3220934-2-rabbit_hole.patch1.81 KB

Patch attached.

mandclu’s picture

mandclu commented

I don't mind integration with rabbit hole, but maybe instead we should have a permission to view storage entities, per bundle?

les lim’s picture

les lim
he/they
Primary language English
commented

Sure, 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.

les lim’s picture

les lim
he/they
Primary language English
commented

If you prefer, I can publish this to its own project namespace as well.

mandclu’s picture

mandclu commented

Given the small amount of code required, I'm actually thinking maybe this makes more sense directly in the main module.

  • mandclu committed c67e693 on 1.0.x authored by Les Lim 
    Issue #3220934 by Les Lim, mandclu: Integration with Rabbit Hole
mandclu’s picture

mandclu commented
Status: Needs review » Fixed

Merged in the code directly to the main module, with an added check if the rabbit hole service exists.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.