No bbuserid or bbpassword cookies

[kevcj]

Does anyone know what modification would stop vbullletin from handing out bbuserid and bbpassword cookies?

My forum has about 25 modifications installed. Instead of having to go through every mod, I thought I would start here and ask.

[TigerC10]

Those mods aren't handing them out, vBulletin is. That's how users stay logged in without appending session IDs to the end of every URL. Session IDs hurt your google page rank big time...

The bbpassword cookie is formatted like so...

PHP Code:

MD5( MD5( MD5(plaintext_password) . user_salt ) . vB_license_number ) 


Essentially, the password hash stored in the cookie, is randomized with the user salt AND your vBulletin license number. MD5 is irreversable, so no one can get any of the private info of your users because your user salt is stored in the database (where only people with permission can get it) and the license number should only be visible by you.

[kevcj]

Originally Posted by TigerC10

Those mods aren't handing them out, vBulletin is.

Maybe you did not understand the question - a modification is STOPPING vbulletin from handing out the bbuserid or bbpassword cookies.

I asked this same question at vbulletin.com and was told that it was a modification that is causing the problems.
http://www.vbulletin.com/forum/showthread.php?t=302518

[RLShare]

Really, all you can do is disable all your modifications and test to see if its working. Then re-enable them one by one and test until you figure out which one is causing the problem

[TigerC10]

Originally Posted by kevcj

Maybe you did not understand the question - a modification is STOPPING vbulletin from handing out the bbuserid or bbpassword cookies.

So you're right, I misread it.

Yeah, it's easy to disable all of your mods at once, and then re-enable them one at a time until you get your cookies set. You must log out and back in each time you turn a mod on to verify it though.

[kevcj]

It might have been an older "who has visited today" modification. One that had been made for vb 3.6. I started removing some of the older modifications that I did not really need.

I removed the mods one at a time, checking the cookies and after that mod was removed. After that mod was removed, there were no more cookie issues.