-
Notifications
You must be signed in to change notification settings - Fork 57
Allow book module to handle unpublished content #463
Comments
Thank you for your suggestion @KatieAK-enviro. We would look for this in a stable release rather than a patch. As a suggestion, your dev partner could have a conversation with the maintainer on Drupal.org to help expidite this process. |
The issue on Drupal.org was created in 2005, the year I started doing Drupal. I agree there would be only one or two sites that need this, so it's not an ideal patch for the distribution, as it's not a simple patch. For the record, I want to flag that the PaaS scaffold allows patches to be applied on a site-by-site basis and if this strategy ever reached SaaS then there would be a mechanism for the helpdesk solve this problem for just the site in question (not saying it would be ideal, but worth mentioning). |
Thankyou for looking into this. The Department does not currently have the capacity to fund our development partner to work with the maintainer to resolve this issue. I'd be curious to understand how other GovCMS sites that use the book module work around this; as it adds significant complications to our publishing workflow. |
It's quite possible that no saas sites are using book module as extensively as you are, govcms team can answer that for sure. |
If I needed to solve this on a SaaS site, here is the way I might solve it. I'm putting this here not because it's quick and easy or even wise, but because it would be way less effort than helping a 15 year old issue get merged to Drupal. Technical jargon follows.
There are a number of side effects of doing this and it should not be done on a whim. There will be a number of places where you need to preprocess to hide content from these pages.
|
Apologies for the delay in responding, I have just returned from leave. Thanks @simesy for your contribution in this issue. Unfortunately, GovCMS doesn't have the resources to progress functionality within modules. I can offer some other options:
Hope that's helpful. |
Problem
We (Department of Agriculture, Water and the Environment) have sites using the book module to create longform reports, which allows us to take a digital first approach to content that would have traditionally been published as large pdf files.
The book module doesn't currently allow unpublished "books" or "book pages" to be used in the book hierarchy. This makes it impossible to effectively prepare a full report in an unpublished state; which means our content approvers can't see what the finished product will look like before approving content. This is a problem in a Goverment publishing workflow, where embargoed content needs to be prepared ahead of time and only published once approved and generally on a designated launch date.
Solution
Our development partner has investigated and found that this issue has been patched:
https://www.drupal.org/project/drupal/issues/26552
The text was updated successfully, but these errors were encountered: