Banning front-end users after login

I've sent login info via PM.

NOTE: In trying to set-up a superadmin for you, I found that this issue is blocking all new accounts on the admin-side. Even if they have a subscription, they get set as Enabled: No. (That's why I had to give you login using a different extension maker's test login - sorry).

I've looked for any other 'user' extensions that may have been 'messing around' with the login process, but I did not find any (other than those previously mentioned).
(We did have JSN Easy Profile installed and using before we switched to CB, but that was completely deleted when we switched to CB).

Also ... there is another 'issue' that we've been trying to track down (across a number of sites) where the admin 'content' of the screen is getting a huge 'padding' added at the top, so you may need to scroll down to see page content. [I'm trying to track it down as it is effective only certain sites that we manage. But I haven't been able to identify which extension might be responsible.]

UPDATE (and possible explanation) ...

I just saw that I got some email noticed about creating SuperUsers:

"If you are receiving this email it means that these Super User accounts were created outside Joomla's “Users” page."

I'm doing some more checking to see if this all related to Akeeba Admin Tools in some way (which I believe sent that email).

Strange, I don't see anything wrong with CBSubs configuration. Also tested a new exclusive plan and it also wouldn't display on login. Seams like CBSubs onlogin behavior isn't firing at all. I believe you've something installed doing this. If you re-enable a user that was disabled then attempt to login through CB you are sent to the following.

/component/users/?view=login&Itemid=101

Then presented with "Login denied! Your account has either been blocked or you have not activated it yet.". That's a Joomla user component page. More specifically Joomla login page. I've no idea what's trying to send the user to Joomla on CB login attempt.

Thanks for confirming what I was starting to think was the problem (3rd party 'stuff').

I think I may have identified a potential conflict between CB and Akeeba Admin tools (I'll test more and post if confirmed/repeatable). However, very possibly all related to the main issue on this site.

Unfortunately, I inherited this site with lots of 'stray code' throughout.

I'll update here once I dig through this and get to the bottom (or still have the issue on a 'clean' site).

One thing that is perplexing me (and might point me in the proper direction to locate the issue)...

Should the user be having Enabled set to NO for the user when their subscription is expired? (based on our CB configuration)?

Should the user be having Enabled set to NO for the user when their subscription is expired? (based on our CB configuration)?

Yes, it disables their account in this case and on login will allow them to re-enable either by renewing or upgrading to another plan. The alternative is to allow free subscriptions without registration then set your plans to be Exclusive instead of Non-Exclusive.