ActionController::InvalidAuthenticityToken

Community FR
1

Bonjour,

Depuis que je suis passé à Rails 2.0.2 j’ai quelque problèmes avec le
Token d’authentification.

En effet, de manière aléatoire sur mon projet, je me retrouve avec
cette erreur :

ActionController::InvalidAuthenticityToken

{“user”=>{“password_confirmation”=>"",
“password”=>"",
“email”=>""},
“preinscription”=>{“code”=>""},
“authenticity_token”=>“b34bc9b7f09ede3688ef8a0dafd3d46038228282”,
“user”=>{“nom”=>"",
“prenom”=>"",
“telephone”=>""}}

C’est assez étrange…

Avez-vous des idées sur ce problème ? J’ai l’impression que j’ai cela
depuis que j’ai déployé mon application sur Internet, qui a le même
nom de session et secret que l’application en dev. Peut-il y avoir un
problème de cookie ?

Je vous remercie par avance,

Pierre

2

En fait, le problème vient de l’utilisation du plugin Restful
Authentification (avant sa dernière mise à jour).

Il faut décommenter la ligne reset_session dans UserController#Create.

Plus d’informations ici : http://dev.rubyonrails.org/ticket/10108

Bonne journée,

Pierre

3

What extensions do you have installed?

Sean

4

Rainer,

Uninstall shards. Radiant 0.6.9 includes the shards API in the core
(since 0.6.7).

Sean

5

Hi Sean,

Archive
Mailer (makes some problems as I wrote about few days ago: “mailer
extension 1.0: no form shows up”)
Markdown Filter
Page Attachments
Reorder
Shards
Tagtools
Textile Filter

Thank you! I don’t have a clue what to do…
rainer

6

Woohoo!

That was the problem.

BTW… Do you have a hint for the problem with the mailer extension?
In the backend I can see everything mailer related (Page Type: Mailer,
Mailer shows up under Extensions…). But the frontend does not show
my mailer form. No errors, no form. It worked before the update.

Best wishes,
rainer

7

Rainer,

I’m not sure. You might try upgrading to a newer version of mailer.
Try the one at http://github.com/ntalbott/radiant-mailer-extension

Sean

8

Is it possible then to hand over the keys to the radiant mailer repo
to ntalbott?

This network

and this network
http://github.com/ntalbott/radiant-mailer-extension/network/members
show entirely different users.

I fear that this is a path to endless confusion for new users down the
road where the official version has some bug, but unbeknownst to a new
user, some other (non-github-forked) repo has fixes and other features.

If most developers are using github, then we should encourage only one
tree for a particular repository. If someone wants to fork it and host
it on gitorious, well then that’s a different story.

9

Jim,

I gave him access already.

Sean

10

Jim,

I’m actually of half a mind to just make radiant’s version a fork of
ntalbott’s. Maybe I’ll check into that.

Sean

11

Great! Now just to convince users to fork that repo instead.
Rainer, sorry to hijack your thread. If you find that Nathaniel’s repo
works for you, send him a note to push changes to the official one…
or perhaps he’s reading this right now…