Jump to content

Search the Community

Showing results for tags 'request forged'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Recently I set up ProcessWire for 3 environments: - Development - Testing - Production From the very beginning I've had the issue when logging in in the admin the WireException "This request was aborted because it appears to be forged." gets triggered. I've already changed the vars in config.php: //different for each env. $config->sessionName = 'wireDEV'; $config->sessionName = 'wireTEST'; $config->sessionName = 'wirePROD'; $config->sessionChallenge = false; $config->sessionFingerprint = false; It even happened to someone that has only logged in to Production. I'm very sure the assets folder and the config.php in the site folder both have 777 permissions recursively. I've added phpcode to remove all cookies when the WireException triggers, that sort of seems to fix the problem, only people have to login twice to get in the admin... Does anyone know what could be wrong?
×
×
  • Create New...