Comparison with Rabbit Hole & Internal Nodes [#1558216]

How does restrict node page view compares with Rabbit Hole? If it doesn't provide features already provided by, or that could make senses being added to, Rabbit Hole, would you consider merging the two projects to avoid effort duplication?

Comments

Comment #1

13rac1 CreditAttribution: 13rac1 commented 26 July 2012 at 19:49

Title:	Comparisaon with Rabbit Hole	» Comparison with Rabbit Hole & Internal Nodes
Issue tags:		+duplicate module

Now there is a third module? :D Something needs to be done about this. I am the creator and co-maintainer of http://drupal.org/project/internal_nodes

My co-maintainer mjpa was the first to post a sandbox project with this type of functionality on April 23, 2011. I posted my sandbox module on April 27, 2011. We submitted Project Create applications within a few days of each other. End result was that we both were given Project Create, and required to merge our modules. We decided to keep my code and his module name.

Rabbit Hole was created January 18, 2012, initially duplicating all Internal Node functionality. From what I am told, there are now two primary differences between Rabbit Hole and Internal Nodes.

Rabbit Hole: Works with taxonomy terms
Internal Nodes: Allows settings per-node

Is there anything this module does that Internal Nodes or Rabbit Hole does not do?

Comment #2

pbuyle CreditAttribution: pbuyle commented 30 July 2012 at 16:14

Rabbit Hole allow per bundle and per entity configuration, so it also "allows settings per-node". It provide more options when preventing access to nodes. According to their description, both Internal Nodes and Restrict node page view only deny access to the page.

Rabbit Holes is the only of the three to mention entities in its description, so I assume this is also the only module designed the address the issue at the entity level and not the more specific node one.

But Internal nodes description documents the search behavior, I suppose this means care have been taken to properly handle it.

Features wise, Rabbit Hole and Internal nodes seems to be the richer modules. Both of them are flexible configurable and seems to avoid bloaded code. I don't see any use case where restrict node page view could be the better option.

Rabbit Hole has the larger user base (according to Drupal.org module usage stats). This can maybe be explained by the module being featured in a Lullabot's Module Monday post (http://www.lullabot.com/articles/module-monday-rabbit-hole).

@eosrei Maybe you and/or mjpa should contact ojohansson to see if and how the modules can be merged (if not already done).

Comment #3

13rac1 CreditAttribution: 13rac1 commented 30 July 2012 at 19:48

Internal Nodes handles the search behavior well, because that was my original use case. It also rewrites the node paths, so you can still display URLs to everything in Views or Search.

I think all functionality should be merged into a new module which supports hiding/rewriting any path (Views/Panels/Taxonomy/Entity/Search/etc).

I've added a comment to http://drupal.org/node/1440608 related to merging the modules.

I checked out that lulabot link. I stared at the screenshot for a while because it is weird to see nearly the exact functionality of my code re-implemented.