Not that I noticed. I've had it installed since 1.0 as well. Are you sure you didn't revert the templates or upgrade your vB version and had to revert some of the templates?

Thanks, I tried that already. No change. The only thing I may have forgotten to do, was upload the other xml file before installing.

plugin.php does not have an eval() call on line 1192.
Are you sure you are using RC3?

@thecool
The Template Edits are basically still the same, just the references to search for have changed slightly.

I have this on line 1192

eval($code['installcode']);


And yes RC3

I got
on line 1192, but I might have a different RC3 then you (CVS Revision 1.57) :)

OK, fixed.

Well I don't get that error anymore. But AWS is still in my AdminCP

Yeah, the cpnav is attached to vbulletin, didn't notice that :)
Anyway, just remove the File and it's gone.
I'll update the ZIP but won't increase the Version Number as it isn't a real issue.

Cool, that worked ;)

If I used the "Private Messaging Cut-off Limit" when the user exceeds the number. He won't be able to send PM's till he falls under the limit which is set by Warn Maturity. So if I set the Warn Maturity to 30 days, he won't be able to use PM's for 30 days??

A user could be banned for just one day. But have their PM's taken away for 30 days. Doesn't sound right.
Can we have a preset setting or incremental like bans?

I get this error when trying to warn a user from the AdminCP