Say I have a content type called "project" that's used for the top parent page of a book. When I add the content type "project" as a template in a skeleton, it works, but after it's created, it's forcibly converted to a "book page." This action breaks all my rules and views designed around the content type "project." I can't make these rules or views without separate content types.

I can't use a basic "book page" as a top parent page because I don't want EVERY page to have all the same custom fields.

Is there any way to keep my content types as "project" and use Skeleton Outlines? (or...why is it converting the content types?)

Comments

deviantintegral’s picture

deviantintegral commented

The content type should be preserved; all that matters is that the content type can be inserted into a book hierarchy. It sounds like a bug to me.

eileen’s picture

eileen commented

I thought it was a bug, too. Any idea what might be causing it? I just tested it again, and it's happening for all users no matter their role. If I create each content type individually outside the skeleton module, they don't convert to book nodes.

Can you offer any advice? Where do I start looking to resolve this?

eileen’s picture

eileen commented

FYI: I just did a clean install of Drupal 6.22 and tried both versions of Skeleton Outlines 6.x-1x-dev and 6.x-1.0-alpha1. Both releases convert all node types used in a template to a "book page." I've checked all settings and permissions repeatedly and I'm completely puzzled. Any ideas to fix this are hugely appreciated!