- Feb 25, 2011
-
-
The Great Git Migration authored
-
- Jun 18, 2007
-
-
Derek Wright authored
-
- Apr 10, 2007
-
- Apr 05, 2007
- Mar 21, 2007
-
- Jan 26, 2007
-
-
beginner authored
-
- Jan 24, 2007
- Jan 23, 2007
-
-
beginner authored
A first big patch, after changing the DB schema to two tables. Main changes: * A volume is not a node, but the definition of a group of nodes. * Added a volume creation/update form in the volume_outline tab. * Since a volume is potentially independent from any node, I added a "title" field in {outline_volume} * Created <default> setting for nodes in volume for child_node_type and toc_depth : the volume's default value will be used. * Much of the logic is different from the one used with one table only. TODO: * volume navigation is broken. * Test all the forms in the volume_outline tab. I have noticed some interference when updating a node, another node from another volume got affected!
-
beginner authored
-
beginner authored
-
- Jan 15, 2007
-
-
beginner authored
-
beginner authored
-
beginner authored
* created 'administer outlines' permission. * fixed the administer outline settings permission.
-
beginner authored
* wrong indentation in settings. * location of the setting page. * we do not need to define a default node type. The cover page for each volume can be of any type, depending on the use made of the volume.
-
- Jan 08, 2007
-
-
Peter Wolanin authored
-
Peter Wolanin authored
-
Peter Wolanin authored
-
- Jan 07, 2007
-
-
Peter Wolanin authored
-
Peter Wolanin authored
-
Peter Wolanin authored
-
Peter Wolanin authored
-
Peter Wolanin authored
-
Peter Wolanin authored
-
Peter Wolanin authored
-
Peter Wolanin authored
-
- Jan 02, 2007
-
-
beginner authored
so we can remove the sql query checking for whatever it was checking. :-/ Also, a major difference with the original book.module PATCH, it is that there is not book_cover node type specifically declared. The volume cover will now be the first node to be top-level within the volume. There could be more than one node at the top level within the volume. Of course, the webmaster can have only one top-level node for a volume, and that top level node be different from the other nodes within the module: this way the volume has a specific volume cover. And a high level of flexibility is maintained.
-
beginner authored
Minimum changes so that book.module and outline.module can be enabled at the same time.
-
beginner authored
-
beginner authored
-
- Dec 29, 2006
-
-
beginner authored
The aim is to strip the book node type definition, but to keep and improve the outline function, based on beginner's and pwolanin's patch here: http://drupal.org/node/65319 and http://drupal.org/node/81226 . TODO: replace book_hooks() into outline_hooks(). replace {book} into {volume} remove book node type definition make outline function more general.
-