Error on membership Sugn-up: Column 'lastResetTime' cannot be null

Hi,
I'm getting "Column 'lastResetTime' cannot be null" on new membership Sign-Up. The new user account gets created but no membership plan is assigned to the user record.

I recently migrated my site from J3 to J4 and finally to J5.3.0 - all went smoothly

CB/CBsubs are up to date, as are all other plugins and components.

I ran all the CB database Tools - no errors

I checked System - Maintenance - Databases - Update Structures (no errors reported)

I attach a copy of my System Information

Any help would be appreciated,

     Phil.
 

CB doesn't have a lastResetTime column. That's a part of Joomla. Within your database ensure the _comprofiler table does not have a lastResetTime column. If it does delete it.

krileon wrote:

CB doesn't have a lastResetTime column. That's a part of Joomla. Within your database ensure the _comprofiler table does not have a lastResetTime column. If it does delete it.

I checked my _comprofiler table and there is no sign of a lastResetTime column, and the problem persists (no membership plan gets assigned to new account registrations) - new users are not able to login even after their account is Enabled, Confirmed and Approved. No membership plan gets assigned to the new account.

Login attempts result in an error message: "Session Expired - Please login again. Membership is required for access"

Clearing my browser cache doesn't help.

I can provide SuperUser access to the live site if needed.

Thanks,

Philip

Please PM backend super user login credentials and will take a look. I believe something went wrong with your Joomla migration as lastResetTime absolutely can be null. Within _users database table ensure your table structure matches the below.

 

PM sent.

Ok, it looks like your table structure didn't migrate properly. Please update your _users table to match the above. You can leave whatever collation you currently have, but NULL state and defaults need to be updated for the table. Joomla 4 and 5 database tool should've caught this so am not sure why it's not picking up the structure issues. You'll have to fix this manually within phpmyadmin or whatever database management software you're using.