Any chance of a D6 version? This is some functionality I'm really interested in. I'm building a fiction archive, and I'd like users to be able to create hierarchical relationships between their stories, to create story series. However, the Book module would allow any user to ad a new story (book page) to anyone else's book. I was originally dicking around with CCK and Views and while I could get the child-parent relationship to work, I haven't been able to figure out how to make a story's parent visible, or how to make a parent's children visible.
This module would be perfect, so... any plans for D6?
Comments
Comment #1
Wolfflow commentedSubscribe.
Comment #2
dwees commentedYeah this is a good idea. I do plan on porting all my modules properly to 6.x versions, but haven't had a chance as yet. I also have a number of other bug fixes/feature requests I need to get at.
Dave
Comment #3
Osfer commentedThat's great news! This module would be a perfect solution.
Comment #4
dwees commentedThe API for the Book module has completely changed in Drupal 6. I suspect this will be a while, largely because of my lack of ti.me to work on this. I'm sorry. I've fixed the problems in the 5.x version, and I've done a bunch of the conversion work, but the 6.x version will not work yet without some major fixes.
Comment #5
lil-1 commentedLooking forward to testing the 6x version!
Comment #6
ultimateboy commentedI too what what this module does, and would greatly appreciate the d6 port. I will provide all the testing you need ;)
Comment #7
Flying Drupalist commentedThere's a book manager module that does something similar, but this one has a richer featureset. Please update!
Comment #8
dwees commentedWell there are two possibilities here.
1. We can try and merge our two projects and allow the Book Manager module to support the other filters this module provides, such as filter by group, filter by role, and filter by private (I'm not sure Filter by Private even works anymore since I don't know if the Private module is being maintained/updated).
2. We can decide that this module is significantly different than the Book Manager module and keep it separate.
Either way I'm going to need help upgrading this module, either through patches provided that I can test and commit, or funds to justify working on this when I have paid work I could be doing instead.
After looking at the Book Manager module, it seems that a feature it is missing is the ability to decide whether or not all books are personal (which is essentially filtering by user, which is what this module does).
Comment #9
ultimateboy commentedMy two cents. After trying to port this module myself, I realized that I do not know enough about how book.module was re-factored in the 5.x=>6.x upgrade. It appears that quite a few things have changed with book, and this module is not easy by any means. With that said, book_manager.module already has a 6.x release. I think that the goals of these two modules are similar enough that it does not warrant two separate modules. Therefore, I think our efforts are better suited for bringing the features offered by book_expand into book_manager. Since you are worried about if the private filter works or not, I would say drop that feature for now, and lets focus on getting group and role into book_manager. It appears that you (dwees) have already posted an issue to the book_manager queue stating your goals (http://drupal.org/node/333241).
I think that this is a very valuable set of tools, and your efforts should be commended.