Problem/Motivation
Why is book the only content type that has an export/"Printer friendly version" functionality?
Proposed resolution
Idea 1: Expand If we already have this capability in core, it should be removed from book module and expanded to work for all content types, instead of treating book specially and leaving everything else up to the Print module.
Idea 2: Remove If we think that Print module does this better than we currently do it in core, we should remove the book export functionality entirely - and leave that to contrib since we already have a fine solution there.
Remaining tasks
Expand
- move the export functionality from book module into it's own module "export" or maybe "print"?
- confirm this works for all content types.
Remove
- Remove all export functionality from book module.
User interface changes
TBD
API changes
TBD
Comments
Comment #1
jenlamptonImportant tagging
Comment #2
Bojhan CreditAttribution: Bojhan commentedI'd say remove it. I am not sure if its really a common thing anymore,
Comment #3
adixon CreditAttribution: adixon commentedActually, the I think the book export function is related to the book module's hierarchical organization functionality (i.e. it's not just what the print module does). If you export a book page, it also allows you to export all its subpages - i.e. generate a whole "book".
Since the book module does allow you to apply book hierarchies to any node type, some of this proposal still might make sense, but it does hinge on book module specific stuff.
The print module is a bit more sophisticated than just this function, it also does email and pdf stuff.
Comment #4
andypostRelated bug #1338858-4: Include theme print stylesheets in Book printer friendly export
Comment #17
quietone CreditAttribution: quietone at PreviousNext commentedThis extension is being deprecated, see #3376070: [Meta] Tasks to deprecate Book module. It will be removed from core and moved to a contrib project, #3376101: [11.x] [Meta] Tasks to remove Book.
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
This issue may be re-opened if it can be considered critical, If unsure, re-open the issue and ask in a comment.