>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3173808. --> Reported by: [joel_osc](https://www.drupal.org/user/124931) Related to !94 !81 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The current book module allows for multiple enabled content-types for books but only a single content-type for child pages. The problem is that if you want to use the book construct but have different requirements depending on the application then a series of problems arise. For example: two different sets of users that only have access to create and edit specific content-types by role or if different path patterns are required depending on the type of book content. </p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>1. Enable book<br> 2. Configure book settings</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>There are modules in the contrib space to help deal with things like access control, but it gets complicated fairly quickly. In looking at it the easier solution is to remove the constraint of a single content-type for all book children and allow each enabled book content-type to have its own child content-type.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Address D6/D7 migration related code and config.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>Conditional settings per content-type on the book settings admin page.</p> <h3 id="summary-api-changes">API changes</h3> <p>None.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None.</p> <h3 id="summary-release-notes">Release notes snippet</h3> <p>Enhance book module settings to allow users to configure the add child link content-type per book content-type.</p> > Related issue: [Issue #460736](https://www.drupal.org/node/460736) > Related issue: [Issue #3265493](https://www.drupal.org/node/3265493) > Related issue: [Issue #3549180](https://www.drupal.org/node/3549180)