Drush for Developers, Second Edition, takes common challenges in Drupal projects and solves them using Drush. This book starts with the different installation approaches for Drush and its command structure. It then moves on to perhaps the trickiest challenge in Drupal projects: keeping code and configuration together during a project's lifetime. Next, we will deep dive into the tasks needed to keep a website under control and learn how to run, automate, and monitor them effectively.
Error validating and debugging our Drush commands is a must and this book has a whole chapter on that topic. The magic of managing remote Drupal projects through Drush site aliases is explained in the following chapters through a practical example. Finally, the book wraps up by putting in practice all the concepts covered in previous chapters in order to implement a development workflow for a team.
Migrating book module nodes is one of the more difficult tasks to accomplish with Migrate module. This is due largely to certain workflow issues that can come up during migrating book nodes, and the fact that book node hierarchy is stored within menu links (Drupal 6 and later). The following code is an example of how to deal with this.
A book is a set of pages tied together in a hierarchical sequence, perhaps with chapters, sections, subsections, and so on. You can use books for manuals, site resource guides, Frequently Asked Questions (FAQs), or whatever you'd like.
Book module is not enabled by default. It must be enabled through Administer >> Site building >> Modules (Drupal 5 and 6) or Administration >> Modules (Drupal 7).