Hi Webchic et all,

I'm actually working on integrating CCK fields into revision based views so that users can see what changes were made to any cck fields and when / why (note: this is different than the "diff module" approach. During my research, I came across the revision moderation module and the views include is just about perfect for my needs. the only real issue i have is that for what i'm doing, i have to patch CCK to support this functionality and add the same node_revisions tables to cck (or either add node_revisions to views or force my copy of cck to be dependant on 'revision moderation'). This leads me to a couple of notes that might make the revisions moderation module more streamlined, cck a bit cooler, and any other contribs easier ;)

a) I think that the node_revisions views table definitions might be more suited in the views/modules/node.inc file with other 'core' tables. This would allow for cck (for example) to rely on the node_revisions table when generating view fields and showing revision data. (yes I also have a solution for the "well this is great but every view would then get every revision of every node displayed" problem )

b) by moving this to views, more modules (such as RM ) can produce view fields that wont conflict or duplicate what other modules are doing.

c) If this gets moved, the 'revision moderation' module's views definition should probably use a different alias of the node_revisions table to allow for and only create the moderation fields that are needed.

I havent done much in the way of patching modules, and this seems to be a multi-module fix.. i'm happy to produce all the code/patches & do the work, if I can get a bit of guidance and backing on where to go/what to do & who to ask ;)

thoughts anyone?

Comments

gnucifer’s picture

gnucifer commented

I think this is great, and exactly what I need. If I understand you correctly this should enable one to se when a new file (file field) was uploaded etc. Im implementing a simple document handling system in drupal, and this is a much needed feature. Righ now I have to rely either on user input creating a file_modified and file_created cck date field, or use the node modified date which is far from a perfect solution. Quite busy right now but i will try to look into this later on.

heydere’s picture

heydere commented

I too like this idea, especially section a) regarding adding the node revisions information directly to views/modules/nodes.inc. I simply needed the functionality to do things like adding "Node last revised by" to a view. I had actually started writing a custom module to do this before I saw that it had been included in the revision moderation module.

add1sun’s picture

add1sun commented
Project: Revision Moderation » Views (for Drupal 7)
Version: 5.x-1.x-dev » 6.x-2.x-dev
Component: Miscellaneous » node data

Well nothing to be done in RM if you want to add code to Views module. Moving this issue over there if you want to pursue it. No idea how/if this even applies to Views V2.

eriktoyra’s picture

eriktoyra commented

Subscribing. Needs the same for 5.x versions. If this is solved views will be even more powerful!

I was trying to filter on a CKK select list only to find that this will only use the filter on the value of the node set to be the current version. I would like to be able to filter the values of this select field for nodes that are in moderation.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Fixed

Node revision is included in views. Every additional field has to be added in RM

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.