Offer migration path from book.module
| Project: | Outline |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
This module is an awesome improvement to the book module -- I think it is much-needed. A few thoughts:
1) to what extent is the module like "node relativity" -- could these be integrated somehow?
2) I downloaded and installed it. After enabling it in the modules view, I found that it adds another "Add child page" and "Printer-friendly version" at the bottom on the pages. I am afraid to turn off the book module, however, because my complicated site structure (about 40 pages) might cease to exist.
3) I was hoping the volume outline would allow me to have multple parents / belong to multiple volumes, but this didn't seem to be the case.
4) Now I'm eager to integrate the volume into navigation, breadcrumbs, and have a sitemap page. Hmm... I can't quite figure out how to do it right off the bat...
These are my initial thoughts.
Thanks!
Mac
#1
Thank you for your feedback.
It is customary to open 1 project issue per item discussed.
Here is a quick reply:
1) I have never used node relativity and learned about that module after I was committed to this one. You can open one new issue per feature you would like to see more integrated between the two modules, and the two module maintainers can discuss what could be made possible.
2) It should add another "Add child page" and "Printer-friendly version" only to those nodes that are both within a volume outline (this module) AND a book outline (book.module). This module is meant as a replacement of book.module, but I need to add a migration function from book to outline. For those like you who have existing nodes of type 'book' turning off the book module is not yet an option. A proper migration path should be a critical feature.
This node is now about this issue.
3) I almost added this feature, and the code can be easily adapted to do so. But I didn't do it, because there are some useability difficulties in allowing this. Those difficulties must be thoroughly reviewed and a solution found before we can add such a feature. People interested can follow up on this topic in this new issue: http://drupal.org/node/135309
4) :-D
Thanks again for your feedback.
#2
btw, use the latest development snapshot until I create a 5.x-2.0 version. There are a few bugfixes in it.
#3
subscribing