Re: [Radiant] rake rails:update:javascript and ActionController::InvalidAuthenticityToken

2008-07-28 Thread Casper Fabricius
The new 0.6.8 release seems to have fixed this problem for me.  
Something good has happened during the weekend, since I was running  
off trunk from Friday :)


/Casper


On 25/07/2008, at 17:24, aslak hellesoy wrote:


On Fri, Jul 25, 2008 at 1:16 PM, Casper Fabricius
[EMAIL PROTECTED] wrote:

Aslak,

Did you ever find a solution to this problem? I'm running a new  
Radiant
based project on Edge Radiant (to avoid other bugs in 0.6.7), but I  
am
getting the ActionController::InvalidAuthenticityToken exception  
approx.
every other time a save a Page or a Layout. I'm running off a fresh  
git

clone from GitHub.



I haven't found a solution to it yet, and I'm seeing the same as you.

Aslak

Has anyone else encountered this error? I'm pretty sure it is not  
related to

the out-of-date javascript issue, is these are standard form submits,
nothing ajaxy.

Cheers,
Casper

On 10/07/2008, at 4:46, aslak hellesoy wrote:

On Thu, Jul 10, 2008 at 4:32 AM, Sean Cribbs  
[EMAIL PROTECTED] wrote:


rake radiant:update will only make a difference when you're  
running in
project mode (in vendor or gem), not if you're running Radiant  
directly

from
source.  And yes, we probably need to update our JS libs to the  
latest.


As far as the authenticity token problem, make sure that you  
don't have
something overwriting the entire page edit view, which was common  
in

extensions before 'shards'.



Thanks for the quick answer, Sean. I'm running off a fresh clone,  
and

the only extension I have is a small one of my own which doesn't do
anything with the edit view. Any other ideas?

Cheers,
Aslak


Sean

aslak hellesoy wrote:


I have a clone of the most recent [EMAIL PROTECTED] I just ran rake
rails:update:javascripts.

This upgraded 4 of the standard rails js files. Shoudn't this be
committed to Git?

The reason I did it was that I keep getting
ActionController::InvalidAuthenticityToken when I save pages. I
googled for solutions and saw a mention of a radiant:update task  
that
is supposed to fix this (but that task seems to be gone). So I  
tried
rails:update:javascripts instead. Unfortunately I still get the  
same

error (and only occasionally). I've reset all my cookies and saved
sessions in FF too.

Anyone knows what's up with this?

Cheers,
Aslak
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant




___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] rake rails:update:javascript and ActionController::InvalidAuthenticityToken

2008-07-25 Thread Casper Fabricius

Aslak,

Did you ever find a solution to this problem? I'm running a new  
Radiant based project on Edge Radiant (to avoid other bugs in 0.6.7),  
but I am getting the ActionController::InvalidAuthenticityToken  
exception approx. every other time a save a Page or a Layout. I'm  
running off a fresh git clone from GitHub.


Has anyone else encountered this error? I'm pretty sure it is not  
related to the out-of-date javascript issue, is these are standard  
form submits, nothing ajaxy.


Cheers,
Casper

On 10/07/2008, at 4:46, aslak hellesoy wrote:

On Thu, Jul 10, 2008 at 4:32 AM, Sean Cribbs [EMAIL PROTECTED]  
wrote:
rake radiant:update will only make a difference when you're running  
in
project mode (in vendor or gem), not if you're running Radiant  
directly from
source.  And yes, we probably need to update our JS libs to the  
latest.


As far as the authenticity token problem, make sure that you don't  
have

something overwriting the entire page edit view, which was common in
extensions before 'shards'.



Thanks for the quick answer, Sean. I'm running off a fresh clone, and
the only extension I have is a small one of my own which doesn't do
anything with the edit view. Any other ideas?

Cheers,
Aslak


Sean

aslak hellesoy wrote:


I have a clone of the most recent [EMAIL PROTECTED] I just ran rake
rails:update:javascripts.

This upgraded 4 of the standard rails js files. Shoudn't this be
committed to Git?

The reason I did it was that I keep getting
ActionController::InvalidAuthenticityToken when I save pages. I
googled for solutions and saw a mention of a radiant:update task  
that

is supposed to fix this (but that task seems to be gone). So I tried
rails:update:javascripts instead. Unfortunately I still get the same
error (and only occasionally). I've reset all my cookies and saved
sessions in FF too.

Anyone knows what's up with this?

Cheers,
Aslak
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant




___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] rake rails:update:javascript and ActionController::InvalidAuthenticityToken

2008-07-25 Thread aslak hellesoy
On Fri, Jul 25, 2008 at 1:16 PM, Casper Fabricius
[EMAIL PROTECTED] wrote:
 Aslak,

 Did you ever find a solution to this problem? I'm running a new Radiant
 based project on Edge Radiant (to avoid other bugs in 0.6.7), but I am
 getting the ActionController::InvalidAuthenticityToken exception approx.
 every other time a save a Page or a Layout. I'm running off a fresh git
 clone from GitHub.


I haven't found a solution to it yet, and I'm seeing the same as you.

Aslak

 Has anyone else encountered this error? I'm pretty sure it is not related to
 the out-of-date javascript issue, is these are standard form submits,
 nothing ajaxy.

 Cheers,
 Casper

 On 10/07/2008, at 4:46, aslak hellesoy wrote:

 On Thu, Jul 10, 2008 at 4:32 AM, Sean Cribbs [EMAIL PROTECTED] wrote:

 rake radiant:update will only make a difference when you're running in
 project mode (in vendor or gem), not if you're running Radiant directly
 from
 source.  And yes, we probably need to update our JS libs to the latest.

 As far as the authenticity token problem, make sure that you don't have
 something overwriting the entire page edit view, which was common in
 extensions before 'shards'.


 Thanks for the quick answer, Sean. I'm running off a fresh clone, and
 the only extension I have is a small one of my own which doesn't do
 anything with the edit view. Any other ideas?

 Cheers,
 Aslak

 Sean

 aslak hellesoy wrote:

 I have a clone of the most recent [EMAIL PROTECTED] I just ran rake
 rails:update:javascripts.

 This upgraded 4 of the standard rails js files. Shoudn't this be
 committed to Git?

 The reason I did it was that I keep getting
 ActionController::InvalidAuthenticityToken when I save pages. I
 googled for solutions and saw a mention of a radiant:update task that
 is supposed to fix this (but that task seems to be gone). So I tried
 rails:update:javascripts instead. Unfortunately I still get the same
 error (and only occasionally). I've reset all my cookies and saved
 sessions in FF too.

 Anyone knows what's up with this?

 Cheers,
 Aslak
 ___
 Radiant mailing list
 Post:   Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



 ___
 Radiant mailing list
 Post:   Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

 ___
 Radiant mailing list
 Post:   Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

 ___
 Radiant mailing list
 Post:   Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant