Kim, There are three main places where formkeys might fail in a new installation. The first and most likely is, the site_key was not peroperly defined in your apache configuration file. In reviewing your apace configuration file for Scoop, you should see a line that begins: PerlSetVar site_key and ends with a 50-60 character random string. If something else appears there such as the text '__SITE_KEY__' the site key was not generated as part of the installation process and you'll need to generate it using the provided script scripts/gen_key.pl in the Scoop distribution. This script required access to the unix devide /dev/random which may not be accessible in some virtualization scenarios such as the Virtuozo virtual dedicated server system (which is is typically why the site_key wouldn't have been generated at installation). In those cases, the random string can be generated by hand, though that of course reduces it's randomness by definition. The site_key string should be uniwque for each Scoop site and is used to seed the formkey generator. It's absence would be the most likely cause of such errors on a new site. The second, less likely scenario is a problem with the Strring::Random, Crypt::Blowfish, or Crypt::CBC perl modules responsible for generating the form keys. If the keys aren't being generated properly, then validation of the keys would fail. In that case you'd want to reinstall these modules, being sure to run the package tests provided with each. The third and least likely case is if, for some reason your database drivers or related perl modules (DBD::mysql, DBI) are missing or improperly installed it's possible the keys aren't being written to the database properly although this would result in MANY other issues resulting most likely in none of the pages of the site displaying at all. So, here I included the top three possible causes of formkey problems but when debugging anything in Scoop, the first place to look is you apache error log file, which should include some indication of what went wrong, beyond the error displayed on the generated page. If that yields nothing, it's possible to systematically enable debugging for (most of) each of the perl module files that make up Scoop, restarting apache and reviewing the log file after each request to a page on which the targeted error occurs. Please feel free to contact me off-list if you run into further issues. Best Regards, Colin Hill -- Scoophost.com - a service of Pinnacle Digital Scoop consulting and hosting services scoop-help-request at lists.kuro5hin.org wrote: > Send Scoop-help mailing list submissions to > scoop-help at lists.kuro5hin.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.kuro5hin.org/mailman/listinfo/scoop-help > or, via email, send a message with subject or body 'help' to > scoop-help-request at lists.kuro5hin.org > > You can reach the person managing the list at > scoop-help-owner at lists.kuro5hin.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Scoop-help digest..." > > > Today's Topics: > > 1. Invalid Form Key error (Kimberly.Haas at sanofi-aventis.com) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 Nov 2007 12:10:03 -0500 > From: <Kimberly.Haas at sanofi-aventis.com> > Subject: [Scoop-help] Invalid Form Key error > To: <scoop-help at lists.kuro5hin.org> > Message-ID: > <737E32BFFCDCD94B8B699026A83ACC060119BC79 at brwsmxsusr01.pharma.aventis.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > Hi, I am a na?ve user and just set this sucker up. Not really a perl hacker so don't get too fancy on me. > I think this question has been addressed before but I have a new twist on it. I am setting up scoop on RedHat Enterprise 4 for WS. The build on this machine was created for me by the IS department and some parts of mysql were omitted. I have sudo rights so I attempted to install the mysql components but got into what someone called dependency hell. So, I uninstalled all mysql and downloaded the latest version of mysql directly from the website. (you see where I'm going with this? You really need to put this information up front). So, my question is, could the Invalid Form Key error derive from the mysql incompatibility? Or is there another possible cause that I haven't even considered yet? It's still early in the game so doing everything over is not a problem while it's fresh in my mind. > Any help is greatly appreciated. > Kim H. > Somewhere in NJ > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://lists.kuro5hin.org/pipermail/scoop-help/attachments/20071128/f4ce2bc0/attachment-0001.html > > ------------------------------ > > _______________________________________________ > Scoop-help mailing list > Scoop-help at lists.kuro5hin.org > http://lists.kuro5hin.org/mailman/listinfo/scoop-help > > > End of Scoop-help Digest, Vol 39, Issue 1 > *****************************************