BBtoNuke.22 NP - Invalid Session. Please resubmit the form

Worker Joined: Apr 26, 2005 Posts: 114

Probably good reasons to be careful with this release as it seems to have issues.

I installed it on Nuke 7.6, patched 3.3 (went trough all upgrades, from the included .17 in NP3.3, to .18, .19, .20, .21 and then .22) and cant post anything due to this error. This is a totally clean site for testing purposes only, so i think its safe to say this issue might be server spesific.

There is a workaround, but as it removes the enhanced security in .22, it's probably not an option:
http://www.phpbb.com/phpBB/viewtopic.php?t=489986

Any takers on this one?

Posted: Mon Dec 25, 2006 12:58 pm

Problem vanished litterarly by itself, no explanation for it whatsoever. Might have been some bad handling of sessions in FireFox, dunno...

Still, a heads up in any case, since it will affect mods, like the quick reply for one.

Posted: Thu Dec 28, 2006 9:24 am

Having smae problem, but can't seem to find the solution...deleting cach or cookies don't seem to help...

Posted: Thu Dec 28, 2006 11:26 pm

Same problem here. Skinny over at phpBB seems to be leaning towards the quick reply mod.
One person there posted a fix for the quick reply.
However, since I don't have a quick reply, I guess that couldn't be it.

I did the upgrade on my local server and everything worked great, but after upload I get this happening when we try to post.
No idea what could be different since I set my local up to match my host server.

Posted: Fri Dec 29, 2006 3:09 pm

For what it's worth, I'm testing RN 2.10 and just installed (thanks Guardian) the 22 bbtonuke patches. The reply function works fine. Created a new topic, posted it, replied to it.

I don't have the quick reply mod (lol, don't want it either because almost invariably I start typing something there and realize I want to quote something or post some code and then I can't).

If you come across any other bugs or have the steps to reproduce what you stated please post them here.

Posted: Sat Dec 30, 2006 3:29 pm

The solution to this problem is:
Change in the forums administration cookie name and/or cookie domain. Smile

I changed both and that worked. Smile

To avoid conflicts when you have several forums e.g in folders you always need to change the cookie name for example to:phpbbnew2mysql

Hangin' Around Joined: May 09, 2004 Posts: 32

Thank You, that resolved my problem, Both with posting and PM's.

Thanks

Andy.

Regular Joined: Nov 05, 2006 Posts: 96

hmmm, that didn't fix it for me...

Posted: Sat Jan 06, 2007 4:59 am

sixf00t4 are you saying then that you have changed the cookie name and changed the cookie domain to your web address (yoursite.com) and it still is not working?
I don't know what to tell you if thats the case as I have done multiple installs and updates and when there has been a problem, this has fixed it every time.

New Member Joined: Jan 11, 2006 Posts: 13

that does nto work for me either I have tried everythign I can think of

Posted: Tue Jan 09, 2007 5:30 pm

Do you have any mods installed or the standard session lenght changed ?

Posted: Tue Jan 09, 2007 5:33 pm

Session length is 3600

Mods on the forums I have

Private Messages

User list

Posted: Tue Jan 09, 2007 5:39 pm

I don´t know if these mods can cause problems but I suppose it could be" Private Messages". Can you try it without this modification.

Posted: Tue Jan 09, 2007 5:55 pm

removed them both and no luck.

My install is in my public_html folder. SO when I type in www.stcloudscoots.com whatever index.html/php is there I go to. the Forums are in public_html/modules/Forums.

I have the cookie set to
Domain: stcloudscoots.com
Name: St. Cloud Scoots (that could be messed)
Path: /
Secure: Disabled
Session length [ seconds ]: 3600

I could just be retarded. I do appreciate the help.

Posted: Tue Jan 09, 2007 6:11 pm

Ok my bad. I just was poking around and saw other cookies in my cookie folder. I took out the spaces and in my cookie name and added _ underscores

Name: St. Cloud Scoots

Changed to

Name: St_Cloud_Scoots
Worked

Thanks

Posted: Wed Jan 10, 2007 12:18 am

Thanks for letting us know!!!

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

I may be onto something here (or not). In posting.php, I decided to find out exactly what was happening to cause that error. In posting.php, I added debug code to:

Code:

    // session id check introduced v2.0.22


    if ($sid == '' || $sid != $userdata['session_id'])


    {


        $error_msg .= (!empty($error_msg)) ? '<br />' . $lang['Session_invalid'] : $lang['Session_invalid'];


    }

so that it looked like this:

Code:

    // session id check introduced v2.0.22


    if ($sid == '' || $sid != $userdata['session_id'])


    {


        $error_msg .= (!empty($error_msg)) ? '<br />' . $lang['Session_invalid']." x - sid=$sid -- userdata_sid = ".$userdata['session_id'] : $lang['Session_invalid']." {else} - sid=$sid -- userdata_sid = ".$userdata['session_id'];


    }

and kept trying to post a new message using windows xp. The following data was garnered. Notice that the userdata_sid, in each instance, becomes the sid the next time I tried to post. That smells like a timing error of some kind. Now to find it in the code. Any takers? The {else} means that the tertiary logic is falling into the ELSE clause.

Invalid Session. Please resubmit the form. {else} - sid=1d9b5e4dbf02c0cec9d1b480ede6e162 -- userdata_sid = 6d5804bd2da6f34fbc959936af4f08dc
Invalid Session. Please resubmit the form. {else} - sid=6d5804bd2da6f34fbc959936af4f08dc -- userdata_sid = 37c8a9bf50bd1cd3e2ab381034842967
Invalid Session. Please resubmit the form. {else} - sid=37c8a9bf50bd1cd3e2ab381034842967 -- userdata_sid = e975bb72499b2aa0fa015e5c67746638
Invalid Session. Please resubmit the form. {else} - sid=e975bb72499b2aa0fa015e5c67746638 -- userdata_sid = dc7edda3a4874cb2c3877ced09596267
Invalid Session. Please resubmit the form. {else} - sid=dc7edda3a4874cb2c3877ced09596267 -- userdata_sid = c44ba9e707abdc1a0e2aa12930b4fe6b

New Member Joined: Jan 17, 2007 Posts: 1

so how to fix this? sorry i'm not understand

Posted: Wed Jan 17, 2007 9:14 pm

All I did was change my Cookie settings in forums admin config section.
I will use mine for example.
www.stcloudscoots.com

Cookie Domain: stcloudscoots.com
Cookie Name: stcloudscoots

Client Joined: Aug 11, 2005 Posts: 32

Susann wrote:

The solution to this problem is:
Change in the forums administration cookie name and/or cookie domain. Smile

I changed both and that worked. Smile

To avoid conflicts when you have several forums e.g in folders you always need to change the cookie name for example to:phpbbnew2mysql

Thank you very much!!! Worked for me.

Hangin' Around Joined: Oct 17, 2006 Posts: 25

I hit same problems .. but seem not only changing cookies name and domain is solved all problem..

in my case i have 3 domain parked in on host.. the one .com is main one and other like .net .info .org is parked..

there r no problems if login by .com but this issue when using other domain name on browser to login..

i have set on my config:
server cookie: xaluan.com
name: xaluan
path: /

hope some one can find out..

and other thing is I have look at original patched of phpbb there is a file named update_to_latest.php for updating table struc .. it totaly longer and complex than the table bbtonuke patched .....????

is that the problem??

any idea ..

registered · Posted: Sat Jan 27, 2007 12:33 am

The cookies will not work correctly with cloaked/redirected URLs, esp in Internet Explorer. There is no fix that I know of

BBToNuke contains only the database changes that are need from one 2.0.xx version to the next 2.0.xx version. update_to_latest.php is a cumulative update script

New Member Joined: Jan 30, 2007 Posts: 2

One thing i don't understand acording this problem is, why can admins and moderators post, but normal users can't ?

Posted: Thu Feb 01, 2007 4:12 pm

Doesn't make any sense to me unless you had the permissions set to Private

Posted: Thu Feb 01, 2007 4:28 pm

No i didn't, all permissions set to members. No normal user could post a msg, or change his profile. Changed one of them to admin, and he could do both.