[support] CCK versus older Flexinode modules

[Bruce Whealton]

Well, I don't need to upgrade from Flexinode because I don't have that
  setup.  What it did is let me create a new content type/node called Poem.
  So, before I can edit my poem node type, I need to figure out how to 
  create the node.
   
  You mention the views module, is that a core module?
  Bruce

Larry Garfield <larry at garfieldtech.com> wrote:
  
Yes, CCK has the same "place in the ecosystem" as flexinode, but is a much more robust and extensible architecture. At this point it seems a foregone conclusion that CCK is/will be Drupal's node management system. Unfortunately, there is no good migration from flexinode to CCK that I'm aware of. There's a module that does a conversion in 4.7, but I have not used it and the description, when last I looked, described it as somewhat shaky.

In Drupal 5, on Content > Content types you can configure any node type in the system. Simply edit your poem node type and set its default publishing settings to not published. You can then create a View using the Views module to list all poem nodes that have their published flag set to false, and only let admin users see it.

Cheers.

--Larry Garfield

On Mon, 28 May 2007 20:55:21 -0700 (PDT), Bruce Whealton 
wrote:
> Hello all,
> I had previously used Flexinode content on a Poetry Magazine
> website using
> Drupal 4.7.x Now, in Drupal 5.x it appears that Content Creation Kit
> replaces
> flexinode from previous versions, correct? Is the idea the same?
> I had a menu link to Create Content >> Poems. I also had it setup
> so that
> what is submitted appears in the queue, whether it comes from a user
> role of
> Contributor, authenticated user, or anonymous. If I give access for all
> these roles
> to Create Content, how can I be sure that it goes into the queue for
> approval first,
> instead of any user being able to publish directly?
> Thanks,
> Bruce
> 
> 
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20070530/38936f52/attachment.htm