is it at all posible to disable a user from frontend?

Correct, frontend display is only for active users. It's possible to alter a userlist through triggers though and force it to display disabled users, but you won't be able to access their profile (that maybe also be doable through triggers, but haven't checked).

I have used Jumi to print out a list of users active and inactive. in that instance I can click on inactive profiles.

Strange, you shouldn't be able to reach their profile if they're blocked; maybe it works fine if they're just unconfirmed or unapproved, but not blocked.

Yes, these are simply blocked but approved and confirmed

ThePiston wrote: cool. but, CB lists only show active users, right? Once they are inactive, how do you display them on the frontend?

Why would you want to show inactive accounts on the front end?

Seems strange for a site wanting to show its customers a list of inactive accounts, a list of inactive accounts = an inactive site to any one of your visitors looking at the site for the first time surely?

But yes you could always just have CB auto-actions block the account instead of unconfirm (I prefer to unconfirm so they can re-confirm if they want).

my clients run membership sites using CBsubs. members often forget to pay dues and they get inactivated - then my admins can't find them on the frontend. these sites need to be able to get in and activate these users or maybe just find their email, etc. I try to keep them out of the backend whenever possible