Upon registration 5-10 % of my members become inactive users

Worker Joined: Aug 26, 2007 Posts: 236

This have happened for me both with 7.2 and 7.6, which makes me to think it is a flaw in PHP-Nuke.

Approx 5-10 % of my members that registers can't access forums, private messages or memberlist at all. This is caused by that they upon registration of some reason is becoming inactive user i.e in nuke_users the field user_active is 0 instead of 1, which is normal.

In Forum admin you can search for a member and change that member from inactive to active and it will work normally then. You can also change this with phpMyAdmin in the user_active field.

Has anyone else seen this behavior? Have you checked your database and searched for user_active 0?

Posted: Wed Apr 02, 2008 6:27 am

Have you tried it in RavenNuke?

Posted: Wed Apr 02, 2008 6:58 am

No, I can't turn to RavenNuke, as I started with PHP-Nuke 6.8 almost 5 years ago. It would be interesting to know, how many have user_active 0 in the database. Maybe there are many crippled members. For me only about 10 % of the concerned members complained about it.

Posted: Wed Apr 02, 2008 8:35 am

Are you up to date on your phpBB forums? Do you have any forum mods?

Posted: Wed Apr 02, 2008 8:44 am

I have no mods, but I have phpBB 2.0.10 i.e the original for 7.6.

Posted: Wed Apr 02, 2008 11:24 am

Well the obvious thing to try would be to get yourself the BBtoNuke packages and update your forums.

Posted: Wed Apr 02, 2008 6:27 pm

I have also inactive users but I guess its quite normal cause I started my board long time ago with Nuke 6.5 and one of the the first integrated BB2Nuke forum version. Nobody informed me ever that there is an issue to login. Quess a lot of these "inactive" are just bot registrations from the past or they had somewhere issues with the e-mail.

Thats from the phpBB documentation:

Quote:

User is Active - You may deactivate/activate a user. This is most often used to activate a user who is having trouble with email activation. A user may not log in while their account is inactive.

I switched over from 6.5 to RavenNuke without any problem you can do the same. Its really not difficult. Smile

Posted: Wed Apr 02, 2008 8:18 pm

Thanks! I had 120 old members that was inactive, but I had not a single bot member of them. By running this SQL query: UPDATE nuke_users SET user_active = '1' I turned all inactive users to active in one operation.

Regular Joined: Oct 14, 2006 Posts: 60 Location: Norway

Hi.
One thing that will set a user "inactive" is;
If you (in Forums AdminPanel -> Configurations) have set

"Allow Username changes" = "No"

.. any user that do change his/hers name at a later time
will then be marked/set as "inactive" ("0") in the DB.

Posted: Thu Apr 03, 2008 2:13 am

Catweazle thanks. I didn´t know this.
Multi accounts and allow usernames changes is never recommendable in Nuke and a similar stupid thing are open guest forums in my opinion.

Posted: Thu Apr 03, 2008 2:20 am

catweazle wrote:

Hi.
One thing that will set a user "inactive" is;
If you (in Forums AdminPanel -> Configurations) have set

"Allow Username changes" = "No"

.. any user that do change his/hers name at a later time
will then be marked/set as "inactive" ("0") in the DB.

Should not it be "Allow Username changes" = "Yes"?

If you are not allowed to change the username, you should not be able to become inactive?

Posted: Thu Apr 03, 2008 5:53 am

slackervaara wrote:

Should not it be "Allow Username changes" = "Yes"?

Nope...

The same goes for any changes to their e-mail address as well - which will also set the user "inactive".

I'm not sure if this is accurate for RavenNuke(tm) though...
The sites on which this has occured to my users are all running PHP-Nuke v7.6 patched.

Posted: Thu Apr 03, 2008 6:21 am

RavenNuke(tm), for the most part, should behave like a normal up-to-date BBtoNuke installation. The main difference between RN and the others in BBtoNuke is that we are XHTML compliant, where-in core BBtoNuke is not.

Posted: Thu Apr 03, 2008 7:04 am

Username changes should not be allowed, it is the quickest way to a raft of problems.
User email changes automatically switch the user to inactive status if they then do not re-authenticate their changed email address.