Hi,
this is really a great module but it's not perfect because it doesn't support drafts.

In my opinion it's a bug that a user with permission to create new nodes but without permission to approve them when creating a new node that node is automatically published without approval.

The workaround of the "Initial revision - this node is under moderation and no revision has been set live yet." is ok but now it's not working.

I have a content type with:
- 1 text field
- 1 data field
- 1 image filefield
- body

After node creation
- text field is visible
- data field is visible
- image filefield isn't visible in the node view but that is visible in a view with an imagecache preview
- body isn't visible, there is the "Initial revision - this node is under moderation and no revision has been set live yet." message. [OK]

Can you implement a "default node live revision", for each content type set for moderation, that is created by the admin with "safe content"?

For example when I set that content type for moderation I create one node of that content type with in the text field "waiting for approval", in the date field "00/00/0000" and the image field with an image with a "man at work". So when a user create a new node the revision with the data inserted by the user go for approval and a live revision of that node is created cloning the "default node live revision".

Comments

eugenmayer’s picture

Category: bug » feature

You can build your own templates by using the hook described in the project description.

For the CCK fields we will need some implementation to hide them away, but thats rather a feature request then a bug.

Thank you for the input

eugenmayer’s picture

Status: Active » Closed (fixed)

closed due to the new implementation in 1.3. Should not be a problem anmore