Firstly, thanks for making this plugin available. It's been a great use in a recent project.

However there is a bit of a large bug when using the plugin without Role Scoper (which the plugin page explains is possible).

When approving a revision (amongst other things) I receive the following error:

Fatal error: Class 'WP_Scoped_User' not found in … on line 132

From what I can tell this is caused by instantiating a new object without first checking that it exists. I am assuming here that WP_Scoped_User is part of Role Scoper and not Revisionary.

The errors can be avoided (or rather, hacked away) by performing an if (class_exists('WP_Scoped_User')) { } check before calling WP_Scoped_User

For the time being I have done this manually on my version of it, but as and when you release an update to the plugin these alterations would be overwritted.

I am aware that I could simply install Role Scoper to avoid these errors, but I don't need it and would be so much nicer to be able to use the plugin stand-alone.

Thanks,
David

hiphip said:

Yah, this is annoying. I hacked this by adding this line to «defaults_rvy.php»:

class WP_Scoped_User {function __construct($x, $y, $z) {return false;}}

That hack will break email notification. Instead, just change all instances of WP_Scoped_User to WP_User.

This is already fixed in last week's Revisionary update (1.0.2). I just forgot to trigger the "current version" status and update notice by editing the readme.txt "Stable tag".