Closed (won't fix)
Project:
Drupal core
Component:
book.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Oct 2004 at 13:17 UTC
Updated:
13 Feb 2006 at 22:25 UTC
It would be usefull to have an option to switch of the navigation bar (prev, next), as also a permission to 'print the entire book' hidding the label when the user does not have permission.
These options are usefull so we can use several books to structure the content of a site, but we do not want the users to be able to see all the info in a page.
Comments
Comment #1
killes@www.drop.org commentedNo new features will be added to the RC, feature requests should be filed against CVS.
I don't see why you want to hide the book's structure from your users. That doesn't make much sense to me. It is an aid for navigation after all. Also, the print link does not reveal more information than the non-print view.
I really don't think this has much merit and mark it as "won't fix". Re-open if you disagree.
Comment #2
magico commentedSorry about filling a feature request no 4.5 :|
What I am doing latelly is configuring a base with Drupal that can be used to insert contents for corporate site quick and easy. Those contents can be:
Profile:
-- Who are we
-- What we do
-- Instalations
----- Entrance
----- Sector X
-------- a special machine that the company as proud of
----- Sector Y
-- Location
-- Contact
Services/Products/etc
-- Group of products
----- product ...
-- ...
-- ...
Portfolio:
-- Group of clients
----- client ...
-- Spetacular jobs executed
----- ...
Site info:
-- Technical info
-- Site map
-- Privacy Statment
-- Contact
If for Services we can argue that 'eCommerce' or 'image' modules could be used, the fact is that many corporates want a simple site with the most importante information. That means that we will have mostly a list of ten products (or services).
For the Portfolio, the structure of the content can be so diferent from company to company, that the easiest way is to create a 'book'
Sure that now, you can say why don't you use taxonomy to organize your contents? Taxonomy exists basicly to classify content, and create a organization based on this classification. It is not suitable to organize pages of static content.
Now that I explained why I use the book, why do I want to hide the navigation bar? Look at the first book I have - 'Profile' - I want to call directly some pages of that book from the menu but I don't want the visitors on the site be able to have that navigation bar in the end. If the navigation is provided in the main menu why have that in the page itself?
On the other hand, other books need that 'navigation bar', an example would be the 'portfolio' where the visitor will use the page as a slideshow of information.
This means that I cannot use only CSS to hide the navigation menu.
The 'print' option I was referring to is the "?q=book/print/x" that prints the entire book. I know a visitor can print a specific page, what I would not want to is that the visitor can see all the information of the book in one page; also, of course that the option to print the "About us" page does not make sense.
Sorry for my english, I hope that you can understand my ideas.
Comment #3
tangent commentedIf book.module is intended to be the primary mode of creating a structured website, instead of page.module (something which is not immediately obvious to new users), then it should be flexible in it's navigation methods. Having the in-page navigation be optional seems reasonable to me.
On the other hand, this may highlight the difference between a "book" (a set of pages which one might optimally read in a linear fashion) and a structured, hierarchical set of web pages which require a menu and why the book module could benefit from refactoring into a module which organizes "page" nodes in different ways.
Comment #4
puregin commentedYou can turn off the navigation bar (site-wide) using css.
Seems like much of the other requestion functionality is taken care of by the new menu system in 4.7; using book.module to provide site structure is therefore not really recommended. Marking this as "won't fix" (again)
Djun