Account disable option in Privacy plug in

I have two questions on the Privacy plugin.

1. When an admin disables a users account from the front end, the admin is logged out and has to log back in again to continue. This can get annoying if you have several accounts to disable. Is there a way to stop it from logging out the admin?

2. Is there a way to disable the ability of a disabled account from reenabling their account? I have changed the access level of the CB Privacy plug in to Registered. That seems to have taken the ability away, but I want to make sure it's gone. Is there another way to disable it?

Thank you.

1. When an admin disables a users account from the front end, the admin is logged out and has to log back in again to continue. This can get annoying if you have several accounts to disable. Is there a way to stop it from logging out the admin?

That'd be a bug. The logout operation should be skipped when it's the admin disabling the users account. Have added a bug ticket for that.

forge.joomlapolis.com/issues/6926

2. Is there a way to disable the ability of a disabled account from reenabling their account? I have changed the access level of the CB Privacy plug in to Registered. That seems to have taken the ability away, but I want to make sure it's gone. Is there another way to disable it?

No, there is no way to disable the ability to re-enable an account. I've added a feature ticket to allow disabling of this functionality.

forge.joomlapolis.com/issues/6927

Thank you.

In the mean time my work around of making the Privacy plug in only available to registered users seems to be an acceptable option for that issue.

It solves that, but causes issues elsewhere. You've now made it so public users ignore all privacy controls, because the plugin responsible for blocking access based off privacy settings never loads for them. I do not recommend setting plugins to anything other than Public unless you completely understand plugin loading behavior.

I understand. All the profiles, and any page that shows them are only visible to registered user so I don't believe blocking the re-enable this way will cause any other problems

Ok, as long as that's the case it should be fine setting the plugin access to Registered then.