Closed (fixed)
Project:
Skeleton outlines
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Jan 2009 at 21:12 UTC
Updated:
19 Feb 2009 at 20:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
deviantintegral commentedHow would you suggest structuring the multiple skeletons? Somehow you would need to choose which skeleton to create an instance of.
Options I see include:
We *can't* just add a dropdown to select a skeleton to the form, as it needs to know what skeleton for token integration to work properly.
Any other suggestions? If you can come up with a patch, I'd be glad to review it.
Comment #2
martin mayer commentedI suggest option number 2. In my opinion a skeleton with child nodes is a new content type. I want to explain why. A skeleton with child nodes is useful to create a book structure which enables users to work on documents which are to complex to be wholly contained in one page. For example this could be planning or analysis documents which are worked on by a team. In this case a structure with planning documents would be one document type and a structure with analysis documents would be another document type. And the users or teams should be able to create a new document structure without needing the help of an administrator each time.
I would be more than happy if I could come up with a patch without having to bother you. Unfortunately I am not yet familiar enough with Drupal module development to do that. I just started trying to get into that but have not come far enough by now.
Comment #3
deviantintegral commentedNo worries - it's a good idea, and one I'd toyed with myself.
Could you try the following patch and see if it works for you? It could especially use testing to ensure that the menu is updated when skeletons are added or deleted.
When you apply the patch, you'll have to reload admin/build/modules to get the menu cache to rebuild the first time.
Comment #4
martin mayer commentedGreat! I tested the patch with book pages and normal pages, each having two child nodes with and without tokens. All versions appear in the "create content" area and generate the books as expected. Thanks a lot! Very helpful to me.
Comment #5
deviantintegral commentedThanks for the testing and feedback. I've committed this to HEAD.