Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
There was a problem authenticating your post information.
Hi,
Just downloaded the latest release of Vanilla (1.1.2). This is a virgin install, as opposed to an update. Installation went swimmingly well, and as a W3C-standards Nazi, I'm really impressed. However, I have an error that pops up each time I try to install an extension.
"There was a problem authenticating your post information"
I've read other posts here that show similar issues, but I've checked browser cache, and even swapped between browsers, IE6 and 7, Opera 9.x and Firefox 2. to no avail. Two two extensions I've tried are:
Applicant Email Verification
Delete User
I've checked the CHMOD permissions for the relevant directories, as per instructed in the FAQ, and they all seem in order. Any help would be greatly appreciated. I feel like the kiddie who's found the goodie jar but some swine has screwed the lid down too tightly! :)
As an aside, there also seems to be an error with the Check for Updates page:
Notice: Undefined property: UpdateCheck::$LussumoMessage in /home/{edited}/public_html/comm/themes/settings_update_check_validpostback.php on line 8 after clicking the "Check for Updates" button.
0
This discussion has been closed.
Comments
Problem after Updating 1.1.1 # 8
It can happen if you sign in with one browser, open a discussion in another window. Then sign out and back in. Then go back to your open discussion window and add a comment. You get the error because your session key has changed since the page was loaded. If you just click save again, it will post as it should.
Do you use the default language and the default theme (and without custom changes in /themes/vanilla/)?
I think in all cases I was interrupted whilst preparing a reply (that I *had* previewed) and
then continued to edit. No logging in/out, and no back-buttons were used (harmed) in
the process...
The "There was a problem authenticating your post information" is a feature, not a bug. It is have been added to prevent CSRF attack
It could be replaced by something more user friendly than an error message, a page that ask you to confirm your post for example.
message indeed needs to be clarified (e.g. with the suggestion to submit your comment
again)