Revisioning for one nodetype, not all

Are you adding those nodes from admin side?
if not, then check with user permissions and if something is related to creating rivisions, just uncheck the box.

Regards.

Hi kukie,
Thanks for your interest in Revisioning.
...what do I have to do to create a node type that doesn't have revisioning, as by now every nodetype has the revisioningsettings...

Well, what should happen is that if you do NOT tick "new revision in moderation" it should not be subject to pending revisions being created....
Moreover, if you also NOT tick "create new revisions", you should definitely not experience Revisioning functionality, as revisions are a pre-requisite for Revisioning....

I think I don't fully understand the setup/configuration of your system...

Rik

Hi kukle,
The Revisions tab appears when more than one revision exist for the node you're looking at. This is core behaviour and not related to Revisioning.
If you want this tab to go you must delete all revisions that exist, except for the current.
To then avoid new revisions being created go to Content management>>Content types>>edit and untick "Create new revision" for the content types in question.
Rik

I also have this problem - no matter what I try I can't stop content types having revisions.

Attached is an image of the settings for the workflow on one of my content types. As you can see, "Create new revision" is unticked, but the "Create new revision:" option cannot be turned off or unchecked, and this content type, like all others, has revisioning enabled.

Is there something stupid I am missing?

Hi Luke,

I just produced a snapshot of the same page on my system, Content management >> Content types for the forum content type. See attached. Note that the actual content type is mentioned in the various messages.

On your screen I don't see that. Are you using Revisioning 6.x-2.7 ?

The radio-box under "Create new revision:" cannot be unticked, but that's ok as it doesn't apply when "New revision in draft" isn't ticked also.

When accessing a node of a type that doesn't have the "Create new revision" box ticked, you will still see the "Revisions" tab (and a single node revision), even though subsequent Saves of the node won't produce new revisions.
The tab needs to be there as that page also houses the "(Un)Publish" link. Without the Revisions tab appearing authors (without the "administor node" permission) would not be able to (un)publish a node.

Hope this helps,

Rik

Seems like small UX problem - option to choose revision save mode is there even if revisions are disabled. I agree that this can be confusing at the first time you use the module.
This could be changed with little JS, to graying out or hiding revisioning options if revisions are disabled.

As for "publish/unpublish" stuff: sure it does seem confusing to have node operation as revision sub-task especially when revisions are disabled. I guess we just missed this part of UI in the process of implementing menu local tasks.

Closed - no activity for 3 weeks.

I have the same problem as kukle.

In fact I do not need the "unpublish" link but would really like to have an "edit" link on content types that do not use revisions.

Not having the edit link means that you need to click first on revisions, then on the only revision that is there and only then you have the edit link. This is far too complex for a navigation intended for basic users.

Couldn't we just have an "edit" link *in addition* to the "revisions" tab?

Subscribing.

This is pretty key to me too. Also, the revisioning module makes /node/123/edit access denied regardless of whether the content-type uses revisioning or not. This is very frustrating.

@soyarma, #15
You have logged this against 6.x-2.7, which is no longer supported. Please upgrade to the latest versions of Revisioning (6.x-3.9) and Module Grants (6.x-3.5) and see if you still have the same problem.