Michael Jubin wrote:
> I am new to RoR. I am running Linux Red Hat Enterprise with MySQL for
> my db, and when I go and either create/update the database I get this
> message:
>
> ActionController::InvalidAuthenticityToken in Test1Controller#create(or
> update)
> ActionController::InvalidAuthenti
Sandip Ransing wrote:
> In your controller add
> skip_before_filter :verify_authenticity_token
>
> Hope this will help !
Thanks for that tidbit, but the problem was that the wait_message()
function destroyed the content of the div with the form in it and
replaced it with the message, S E A R C
In your controller add
skip_before_filter :verify_authenticity_token
Hope this will help !
Sandip R~
--
Ruby on Rails Developer
http://sandip.sosblog.com
http://funonrails.wordpress.com
www.joshsoftware.com
--~--~-~--~~~---~--~~
You received this message because
I suppose it was not a good idea to replace the form with "removeChild"
:before the form is submitted...
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Tal
Here are more details from that error:
Processing DocdirController#search (for 127.0.0.1 at 2009-06-04
11:34:39) [POST]
ActionController::InvalidAuthenticityToken
(ActionController::InvalidAuthenticityToken):
:8:in `synchronize'
/usr/local/lib/ruby/1.9.1/webrick/httpserver.rb:111:in `servi
pete wrote:
> Ah, ok, so the suggestion is to add a hidden field with the <%=
> form_authenticity_token %> in it?
>
> Thanks again, I've been messing with this all day...
Did you solved your problem ?
I'm having the same trouble, but in my source html page I can see the
token there:
No ma
Ah, ok, so the suggestion is to add a hidden field with the <%=
form_authenticity_token %> in it?
Thanks again, I've been messing with this all day...
On Nov 29, 9:25 pm, "James Mitchell" <[EMAIL PROTECTED]> wrote:
> The generated token is a one time use token. So, if the page is
> rendered, an
The generated token is a one time use token. So, if the page is
rendered, and the token value is stored on the page, but you interact
with the app via ajax, that token becomes invalid. It's a way to
guarantee that the page rendered was the one submitted and prevents
duplicate posting whether on
Also, if you refresh the page, the problem is fixed. I don't
understand this...
Thanks for your feedback.
On Nov 29, 8:41 pm, pete <[EMAIL PROTECTED]> wrote:
> What if I'm using the cookie_session_store?
>
> On Nov 29, 8:24 pm, "James Mitchell" <[EMAIL PROTECTED]> wrote:
>
> >http://alwaysmovef
What if I'm using the cookie_session_store?
On Nov 29, 8:24 pm, "James Mitchell" <[EMAIL PROTECTED]> wrote:
> http://alwaysmovefast.com/2008/01/30/ajax-in-rails-with-authenticity-...
>
> --
> James Mitchell
>
> On Sat, Nov 29, 2008 at 9:53 PM, pete <[EMAIL PROTECTED]> wrote:
>
> > Hi-
>
> > I am
http://alwaysmovefast.com/2008/01/30/ajax-in-rails-with-authenticity-token/
--
James Mitchell
On Sat, Nov 29, 2008 at 9:53 PM, pete <[EMAIL PROTECTED]> wrote:
>
> Hi-
>
> I am trying to use AJAX calls to login and logout of my Rails app so
> that the form renders in the side bar when you are n
11 matches
Mail list logo
