Zhuo

Yes, it’s necessary while your database scale is small.
Yes, that’s what this plugin for.

Sorry for that, I will update this plugin ASAP

What kind of the “related entries” that should be deleted?
I’m feel confused

jayharle
Please delete the your 2.1.2 and reinstall.
If it still haunting you, then tell me what did you do before you got this.

I’ve fixed the problem, last time I had a bad wifi condition that makes the code broken…PLEASE re-download or re-install the 2.1.2 again, SORRY

I think you don’t has the right of “edit_user” which is hard-wired in the plugin near line 219,

function Revis_save_user_profile_fields( $user_id ) {

        if ( current_user_can( 'edit_user', $user_id )) {

please contact your Administrator to rectify your rights, or change it yourself.
I’ve admit it’s kind of weird…

First Sorry for that, But code 4 means you don’t had the right to modify current user, please check your authorities.

I’ve check the plugin under:
Wordpress – 3.2.1
revision cleaner – 2.1.1
qtranslate – 2.5.24

It works, no serious compatible issue, just the I18N not functioned. It seems I had to change the way load I18N files ??

if you still encounter this error with RC version 2.1.1. Please email me your plugins list to wordpress(at)mengzhuo.org if you like to do so, thank you.

Hmm…please tell me which version is it at less.

Upgrade to 2.1.1
Feel free to report any bug

Best Wishes.

:O
Sorry, can’t activated the plugin is better than can’t login into admin panel, isn’t it? please tell me which version you upgrade from. If you can access to your Mysql server, delete the entry named “Revis_Setting” in the table named “wp_options” , it might help,

I’ve upgrade to 2.1
Enjoy!

Thank you for reporting this, I presume that you might remove your admin whose ID is 1 for security, is’t it? The Revision Cleaner is hard-wired to read ID=1 as admin setting while multi-site is off.
The customization of Designate one admin’s ID as 1 (Neo) will be add in version 2.1 ?? (May be release it after I’ve done some tests couple hours later)

VERY Sorry for any inconveniences , I have fix it in 2.0.1