"Your submission could not be processed because a security token was missing."

[Lynne]

That account works fine. I get sent to the /forums/ page and all is fine. And, when I click the home page link, I can see the page. Very, very odd!

I then went back and tried the first account, and now it is fine. But, the first two times I logged in using it, I got the problem I described. However, using this first account, I still get a No Permission message when hitting the Home link - http://marketersspaceforum.com/index.php

[mmurtha]

Yes it is very odd!

Now the only thing I did different was that I set the "Time and Date" option to "DST corrections always on" in the options when I set that account up.

It seems to be a problem with the DST function someplace.

Thanks so much for your help btw, I truly appreciate you!

Perhpas someone else who has a fix for this will come along, or maybe I'll hire a programmer to resolve the issue.

[Lynne]

The problem there is I'm redirected to marketspaceforum.com instead of www.marketspaceforum.com . I can see www.msf.com just fine. I would change this (in your footer):

<form action="http://marketersspaceforum.com/forum/profile.php?do=dst" method="post" name="dstform">

To this:

<form action="/forum/profile.php?do=dst" method="post" name="dstform">

[mmurtha]

Okay, I gave it a try, and thanks again!

Okay, Dan's going to check things in the backend. Maybe he'll come up with something.

--------------- Added [DATE]1241479397[/DATE] at [TIME]1241479397[/TIME] ---------------

Originally Posted by Lynne

I am not getting a security token error when I log in. I am redirected to this page - http://marketersspaceforum.com/ - and told I have no permission. That is different than the security token error. I can try to click on the Home link, and I get the no permission error. This sounds like a problem with your vbadvanced (which I have no experience with).

Hey Lynne,

Just for the recoed, I believe you were right about this problem being in the VbCMPS. Dan took a look at it, and found out that vBulletin was looking in the footer template of vBa CMPS for the security token information instead of the predominate VB footer template.

We think he fixed the issue, so if someone else has this problem and is using vBCMPS, this might help.

[angeljs]

Just want to say thanks...this error has been driving me mad, so thanks for the fix!

[gnagplank6]

Originally Posted by Dan Clement

Hi folks,

I was having the same error but I seem to have been able to resolve it. I'll run you through what I did in the hopes it'll sort you out too.

In the Admin CP, drop down Styles & Templates, then go to Style Manager. Find the skin you're having trouble with and go to Edit Templates. Find your 'footer' template and find the following snippet of code:

<!-- auto DST correction code -->
<form action="profile.php?do=dst" method="post" name="dstform">
<input type="hidden" name="s" value="$session[sessionhash]" />
</form>

From what I can make out, the error arises because the lines that calls upon the user's security token are omitted leading vB to think that the user doesn't have one. You need to add in a couple of lines to make vB call the security token. To do this, replace the code above with this:

<!-- auto DST correction code -->
<form action="profile.php?do=dst" method="post" name="dstform">
<input type="hidden" name="s" value="$session[sessionhash]" />
<input type="hidden" name="securitytoken" value="$bbuserinfo[securitytoken]" />
<input type="hidden" name="do" value="dst" />
</form>

Save your changes and try accessing your User CP again. Should have fixed you right up. If not, give me a shout.

Just to re-iterate, you should not have to edit profile.php at all to fix this error and in trying to do so you're probably more likely to break something!

Thanks, I have tried this solution and will post up on whether it works.

For some time now new users have been receiving the security token message and were unable to participate in the forum upon registering. I recently, within the last week, started receiving the "security token" message every time I tried to access my own user CP and sometimes when I tried to preview some of my posts. Today this issue mysteriously disappeared for me prior to executing the above solution. dunno why

I have read the available threads on this forum and so I have done my part. Any advice or help would be most appreciated.

This security token issue also happens to myself and others when I try to use the basic forum search function. Advanced search works just fine.

We are still in Beta but do have enough members that all these security token issues cause a great deal of consternation.

We are currently running VB 3.8.3 and are using a skin originally from vbskins.com which we totally customized for our site. It's awesome but until we fix these issues with some new members being unable to register and participate, as well as jacked basic search function we are dead in the water.

[gnagplank6]

Hey does anyone have any input on my above post????

I could use some advice here. Thanks.

[gnagplank6]

Well I ran the fix posted on by Dan Clement and so far it seems to work. Several people who were unable to log on now can.

Thanks Dan!!

CAN I PLEASE GET SOME INPUT on the reasons that my basic search function is not working? Any help would be most appreciated. I get a Security Token error when I try to use the basic quick search function, but strangely advanced search works fine.

I won't let this thread die.

[Lynne]

Originally Posted by gnagplank6

CAN I PLEASE GET SOME INPUT on the reasons that my basic search function is not working? Any help would be most appreciated. I get a Security Token error when I try to use the basic quick search function, but strangely advanced search works fine.

Did you add the securitytoken correctly to the search form in the navbar? Read this - Implementing CSRF Protection in modifications

[gnagplank6]

Originally Posted by Lynne

Did you add the securitytoken correctly to the search form in the navbar? Read this - Implementing CSRF Protection in modifications

wow someone responded!! Thanks for your advice Lynne!!!

I will try to implement this fix ASAP and report back on the linked thread.