I am currently running XOOPS 2.2.3 on a production server and have been experiencing intermittent difficulties with some of my users not being able to complete registration. They will show up as a inactive user, date joined 1970-01-01, with number of posts (-1).

Are there any thoughts on what causes this behavior and how I can get it to stop?

Can I complete/repair the activation of these users manually?

Thanks,

Sam Bowen

Hmmmm... I think I remember seeing a post like this somewhere else on the forums.... I'll see if I can do some digging and post back.

In the meantime, it might be a MySQL error. Try repairing the table using a MySQL Database Management program, like PHPMyAdmin. Remember to back up your table before performing this operation, though!

Also, just so ya know, the latest version in the 2.2 branch is 2.2.4. Try upgrading your system to that version as well.

Reparing it manually... hmmm... an active user should have a level assigned to them besides 0, I believe. You could try adjusting the number of posts and their assigned level, as well as date joined. Try using Xoops' "Activate User" interface as well.

Well, if I find that post, I'll respond back to let ya know.
Good luck with your site!
-zimmi88 =)


EDIT:
Well, I wasn't able to find that specific post, but here's a recent post with a date problem similar to yours.
https://xoops.org/modules/newbb/viewtopic.php?topic_id=52152&forum=20&post_id=231902#forumpost231902

I don't know for sure if this will help but do have you granted access to anonymous users/group for the extended profiles module? I remember seeing a post where this was causing some problems and that anonymous needed permisions for the extended profiles.

HTH
Quest

I am also using 2.2.3 on a site (I've made lots of script changes so didn't want to make the wholesale change to 2.2.4 - I know that's bad).

I used to have the exact problem you describe.

But haven't had it since I stopped deleting user accounts (just disactivate them now). I really can't explain why that made the difference. The final poster on the thread linked-to below believed it was due to making mistakes on the registration form. I sometimes make mistakes (I register the users) but haven't had the problem recently, although I do try to be careful just in case.

https://xoops.org/modules/newbb/viewtopic.php?forum=2&topic_id=43591

The incorrect entries can be amended manually using mysqladmin or similar. I use the site below to change dates if necessary (they are stored in a funny format which took me ages to realise). The 'incorrect' joining date is unixtime zero (000000000).

http://www.captain.at/review-unixtime-javascript.php

“Also, just so ya know, the latest version in the 2.2 branch is 2.2.4. Try upgrading your system to that version as well.”

The 2.2 branch is problematic. A lot of the modules do not function correctly. In fact I wonder if this registration behavior is not a problem with the 2.2 branch. I intend to roll back to the 2.0.14 branch when I have a rainy day to work on it. This rollback will not work with 2.2.4 so I have stayed with 2.2.3 for a while. I am waiting on the development team to make some progress towards fusing the two branches into 2.4. If they do not make enough progess towards 2.4 (or abandon 2.2) then I will roll back to the 2.0 branch. Either way, upgrading to 2.2.4 is not likely going to fix this problem.

It seems that more experienced users are the ones who have trouble with the registration. As stated later in this thread, mistakes made during the registration process seem to be causing the problem and would explain the erractic behavior.

All inactive users appear to have a level 0. Where the active users have a level of 1. Unfortunately simply promoting the inactive user from level 0 to level to level works only if the number of posts = 0. If the number of posts shows -1 this does not fix the users status. (I've already tried this).

I understand that Unix time zero is shown as midnight of 1970-01-01 (or on some systems as 1969-12-31). I stated this in my post in the forum #231902. I take this to mean that the existing add user function is passing a null value to the “date joined” field. This should not be allowed to happen and represents a bug in the add user function.

Deleting the user accounts doesn't work. I've tried this also. When I go back in to receate the account using the same user name and e-mail address the account is still broken.

The anonymous users already have access right to the extended profiles.

The thread #43591 is definitely discussing the same problem but there does not appear to be any clear solution other than using a manual deletion. It appears that this add user function updates the database with incorrect information before the user is able to verify that the information thereby, breaking the registration process.

Does this ever happen in the 2.0.14 (stable) branch?

Sam Bowen

I was able to manually repair the affected users. I did install phpMyAdmin to do the following:

table

users set level = 1
user_profile set posts = 1
user_profile set user_regdate = 1152705600 (the unix date of registration)

I then entered the extended profile of the affected user and gave them a group select of Registered Users.

After this the user behavior appears to be normal.

Still, Why does the registration routine allow this to happen in the first place?

Sam Bowen