Hello everyone, I'm sure many would love to know how to do this!
Requirements:
* I have a Developer's Guide as a Drupal book, collaboratively edited by the development team.
* As we have released the product version associated to this Developer's Guide, the book needs to be 'branched'.
* I would like to duplicate all of the book content into another book (copy of Developer's Guide), including images uploaded with upload.module and displayed with inline.module.
* This would really mean copying the images so that changes to images in the copied book are not seen in the original book.
* I am willing to loose revision information. Only the head revision of each node need to be copied to the new book.
* Has there been any PHP scripts written (not modules) that you know can do this job?
I'm pretty sure I'm not the only one who requires this feature to make the book feature viable. How are the Drupal books maintained in regard to the different Drupal versions in production use?
Thank you very much,
Starman
Comments
hmmm, this sounds like a
hmmm, this sounds like a nice idea- better (perhaps) than the current situation at drupal.org.
My first thought is that you could export the book and then import it again as new nodes, perhaps applying a different taxonomy term (e.g. 4.7.x vs. 5.x as terms).
http://drupal.org/project/importexportapi
http://drupal.org/project/bookimport
http://drupal.org/node/38757
http://drupal.org/node/39121
http://drupal.org/node/39122
---
Work: BioRAFT
Clone?
This isn't your final solution, but something that you can probably change around to work. Check out the node clone project. Might even try submitting it as a feature request (to crawl though a book page's children and clone them also).
Good luck,
Jason
clone code
Since that's my module, I'm happy to tell you that the code is pretty minimal. It probably wouldn't be too hard to hack it into something customized for your needs.
---
Work: BioRAFT