ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Unable to set Process form data in Secure Mode

June 05, 2013 9:08am

Subscribe [3]
  • #1 / Jun 05, 2013 9:08am

    fanderson

    899 posts

    I just finished an upgrade to EE 2.6.1 and when I try to set Process form data in Secure Mode I can click Yes, but when I click Submit it reverts back to No.

    Currently the Preferences are set to Session ID Only for the Contro Panel and Cookies only for User Session Type.

    I have been getting a lot of spam on the site lately and would like to see if I can at least reduce it.

    Thanks.

  • #2 / Nov 08, 2013 3:29pm

    visualpeople

    6 posts

    I know this is from a couple of months ago, but did you come up with a solution to this? I’m having the same problem and can’t figure out why and this seems to be the only relevant result to my search.

  • #3 / Nov 08, 2013 3:32pm

    fanderson

    899 posts

    You know I never did hear back on this and for the life of me can’t even remember the problem. What version of EE are you running?

  • #4 / Nov 08, 2013 3:38pm

    visualpeople

    6 posts

    I’m running 2.7.2, so it might not be the same, but I was getting a (maybe unrelated?) error when doing a site search:

    unknown column ‘csrf_exempt’ in ‘field list’ ...

    Which should be in my exp_actions db table, so I was trying to troubleshoot by turning on the ‘Process Form Data…’ setting.

  • #5 / Nov 08, 2013 3:41pm

    fanderson

    899 posts

    Are you using the standard simple search?

  • #6 / Nov 08, 2013 3:51pm

    visualpeople

    6 posts

    Yes, just the standard simple search which has always worked before.

  • #7 / Nov 08, 2013 3:51pm

    fanderson

    899 posts

    Can you post your code for it here?

  • #8 / Nov 08, 2013 3:58pm

    visualpeople

    6 posts

    No problem:

    {exp:search:simple_form channel="about|barrel-to-keg|contact|education|feature|housing|how-can-i-help|jobs|misc_content|news|nutrition|resources|news" result_page="search/results" no_result_page="search/no_results" search_in="everywhere"}
    <fieldset>
        <input type="text" name="keywords" id="search" value=""  />
     <input type="submit" id="submit" name="submit" class="button" value="Search" />
    </fieldset>
    {/exp:search:simple_form}
  • #9 / Nov 08, 2013 4:01pm

    fanderson

    899 posts

    Everything looks right, so I am not sure what the underlying problem is. I recommend that you take your question to the much more responsive forum on Stack Exchange: http://expressionengine.stackexchange.com.

  • #10 / Nov 08, 2013 4:12pm

    visualpeople

    6 posts

    Thanks for your help! I appreciate you taking a look anyway.

  • #11 / Nov 13, 2013 12:56pm

    Stamp Idea Group

    38 posts

    It looks like when upgrading EE, it doesn’t create csrf_exempt in action table.
    You can fix it by adding an csrf_exempt field in action table, using tinyint(1) as data type, default value will be 0.

  • #12 / Nov 13, 2013 12:59pm

    visualpeople

    6 posts

    I should have replied to this—but I wasn’t 100% sure I was correct. But that’s what I did, too, and haven’t had any problems since. Thanks!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases