My changes (features/bug fixes) to the module

Hello,

Your module is a life-saver for me. I was afraid I'd have to program something similar from scratch. I work for a University, and we needed a way for people to submit nodes which would then be moderated on a per-revision basis.

The hitch was that we didn't want to give the moderator the full "administer nodes" permission. So, I started making changes to your module to suit our needs here. I thought I would post my changes, in case anyone else wanted to check them out or comment on them (or, if you want to include them in your next release).

I marked ALL of my changes with the text: RP EDIT. So if you want, you can just search through the code for "RP EDIT" to see what I did.

Below is a list of what I changed (starting from 6.x-1.0-alpha2's .module file):

#1: Created a new permission, called "approve revisions." The "administer nodes" permission is no longer required. Instead, give the "approve revisions" permission to the user(s) you want to be able to moderate revisions.

#2: Added to the settings form, to let you set what message is displayed to the user upon submission (instead of simply "Your changes have been submitted for moderation").

#3: Fixed a bug with the function revision_moderation_get_all_pending_revisions() function. As it was, if you had 2 revisions waiting for the same node, the earliest revision would be returned-- but logically you would want the latest revision returned instead. That is what I changed.

I might make more changes or additions during the course of my project here at work. If I do, I will post updated files in response to this message.

Thanks again for this great and useful module!

Richard