Login Cookies gone awry after upgrade

Involved Joined: Dec 27, 2005 Posts: 296

I just upgraded from 2.02.00 to the 2.02.02. And after I upgraded, when I try to log in as a regular user, it gives me an error :
"Cookie functions seem to be disabled.
Please change your browser settings!"
Except it *does* log me in and I can access all the member areas.
I can't seem to log out either. I haven't changed anything in my browser, any ideas?
I'm using CNBYA so I didn't upload the Modules/Your_Account that was in the upgrade package.

Posted: Wed May 10, 2006 6:55 pm

I don't know anything about CNBYA but I'm wondering how the table structure that it expects conforms with the table structure of 2.02.02. Does the installation of CNBYA involve any table changes to the base Nuke tables such as nuke_user?

When you ran the upgrade did you run the SQL steps? How did you maintain your old user table?

Of course you can always try the tried and true ... delete your cookies and have them recreated.

Posted: Wed May 10, 2006 7:58 pm

Hi fkelly,

Ok, am going to try to answer those questions in order:

1. These are the only changes that is made by CNBYA to any base Nuke tables:
ALTER TABLE ".$user_prefix."_users ADD agreedtos TINYINT(1) DEFAULT 0 NOT NULL;
ALTER TABLE ".$user_prefix."_users_temp ADD realname VARCHAR(255) NOT NULL AFTER username;

From what is altered and added, it would only seem to affect a users sign-up process (Agreeing to the terms of service and adding a field for their real name).

2. Yes, I ran the SQL steps from the upgrade package. (It came as a seperate download). I had a couple errors, but it said those errors were cause by duplicate entries which the file said would be ok to ignore.

3. Not sure I understand the question? I manage my database through phpmyadmin.

4. I've tried several variations of clearing cache, cookies, browser and reboot technique, but none have worked.

Sad

Posted: Wed May 10, 2006 8:27 pm

Ok, I found a work-around. I set the configuration in CNBYA to NOT check to see if the users' browser accepts cookies and that got rid of the error. It still is doing some funky things, but nothing that affects the functionality of things (like still showing the 'logout' link after I logout, etc)...at least so far... Bang Head

Thanks for the help!

Posted: Thu May 11, 2006 6:34 am

Glad to hear that it is working, in a manner of speaking. I was trying to find out how you got your user table data over into the RN 2.02 structure but instead it sounds like you applied that structure to your old table thru the upgrade script leaving the old data intact.

Honestly it doesn't sound like your problem is table related but it can be hard to tell. Let's say the CNBYA code has SQL code similar to INSERT INTO prefix_users Values (a, b, c, d ...). It will expect a predefined order of field names with the values corresponding to that order and with exactly one value for each field name. If the upgrade script has added another field (and I don't know if it did) the SQL will bomb, error, terminate unexpectedly, abend ... well you know). With errors hidden you might not even notice except that something strange appears.

Perhaps something might show in your server's error log? Or you could manually compare the table structures before and after the update. If RN2.02 didn't insert any new fields you should be okay in that way. If it did you might inspect the CNBYA code for SQL statements and see if any of them might be at "fault".