Is there a plan to use this module as a replacement/alternative of/for core's Book module? In my opinion, using core's Book module has more drawbacks than benefits since Drupal 7. Especially, because it does not support any other entities than nodes and also it does not play well with revisioning thanks for it was built on the top of the menu system.

It should not be so complicated to port all features that core's Book can provide to this module.
I would like to help in this implementation, but I'm not sure whether I should create a new contrib for this or submit patches to this project.

What do you think?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mxr576 created an issue. See original summary.

mxr576’s picture

Made some progress today with the "Children" local task to have a Book outline-ish UI there rather than the current one. My question still stands, should I create a patch from this or a new contrib?

larowlan’s picture

Issue summary: View changes
larowlan’s picture

I would support that functionality being added here, I think as either a sub-module or part of the existing module.

Given that the children form is just an entity form added via hook_entity_info_alter, a sub module could substitute the default implementation with its own.

Of course, please start with tests, we have very high test coverage in this project and want to keep it that way.

colan’s picture

Component: Support request » Code (module)
Related issues: +#1261130: [PP-1] Rewrite book module to use a standard, reusable API for creating hierarchies

We've been discussing an idea such as this in the related issue. I've never heard of this module, but it may do the trick until we get a hierarchy API into core.

Edit: Actually, maybe this module could be the thing that gets into core.

anavarre’s picture

I really like what I see in the attached GIF file. Pursuing this would be very promising for sure.

Murz’s picture

We can reuse some part of https://www.drupal.org/project/draggableviews module for make interfae like in Book module based on Views. At now DraggableViews don't fully support Field api for store parent, but this is planned for next release.

lukasss’s picture

This is great ideas use his as book in core drupal 8

larowlan’s picture

Status: Active » Closed (won't fix)

This feels like there should be an issue in the core issue queue first

frob’s picture

Was there ever an issue raised in core? I couldn't find one.

larowlan’s picture

I don't think so. It would need to go in the core ideas queue I suspect.

mxr576’s picture

Was there ever an issue raised in core? I couldn't find one.

#1261130: Rewrite book module to use a standard, reusable API for creating hierarchies was referenced in the beginning, is not it enough?

mxr576’s picture

colan’s picture

Category: Support request » Plan
Status: Closed (won't fix) » Needs review

The core issue is #1261130: [PP-1] Rewrite book module to use a standard, reusable API for creating hierarchies, but it's blocked on #267855: Provide an entity hierarchy API, which refers to this module as a possible means of implementation. So I think we should close this ticket as a duplicate. I'll reopen for now just to get others' thoughts on this. (i.e. If you agree, close as a duplicate.)