Re: [Radiant] rake rails:update:javascript and ActionController::InvalidAuthenticityToken
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] how to integrate rails app existing on radiant cms???
Please search the email archives, I've answered this question numerous times. Sean Wes Wes wrote: how to?? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
Marshall, I just saw this message (I use Live HTTP Headers too) as I'm preparing to leave on a two day trip. So I won't be able to do anything until I get back (didn't want you to think I was ignoring you). The big question still is: Why is LiteSpeed serving up the content fine yet assigning a 404 to the page? Again, I'm guessing that it's something with SnS but right now I don't know where to start looking. Any help by the Radiant community here would be greatly appreciated. If nobody has any suggestions, I'll start analyzing the output of the TextAssetResponseCache once I get back to see if I stumble on anything. This one smells weird. -Chris Marshal Linfoot wrote: LiteSpeed has a log with optional debug output but it's mostly server state information (ie. processes starting/stopping). I couldn't find anything useful. I discovered a nifty FF add-on called Live HTTP Headers, though. Here's what it shows for the production site using the old-fashioned way of including css and for the test site using sns. The only differences I can spot are the addition of the Etag and If-None-Match headers in the test site responses. Is this significant? The html files returned are the same except for the link ... / tags. http://octopusgardenyoga.com/ GET / HTTP/1.1 Host: octopusgardenyoga.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5; __utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F; style=Default; _session_id=a398654d739c03309b141883e3ae8f6c If-Modified-Since: Wed, 23 Jul 2008 16:08:48 GMT HTTP/1.x 200 OK Content-Type: text/html; charset=utf-8 Last-Modified: Fri, 25 Jul 2008 03:05:45 GMT Content-Encoding: gzip Vary: Accept-Encoding Transfer-Encoding: chunked Date: Fri, 25 Jul 2008 03:05:45 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 -- http://octopusgardenyoga.com/styles/elastic.css GET /styles/elastic.css HTTP/1.1 Host: octopusgardenyoga.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Accept: text/css,*/*;q=0.1 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://octopusgardenyoga.com/ Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5; __utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F; style=Default; _session_id=a398654d739c03309b141883e3ae8f6c If-Modified-Since: Wed, 23 Jul 2008 16:51:31 GMT HTTP/1.x 200 OK Content-Type: text/css; charset=utf-8 Last-Modified: Fri, 25 Jul 2008 03:05:45 GMT Content-Encoding: gzip Vary: Accept-Encoding Transfer-Encoding: chunked Date: Fri, 25 Jul 2008 03:05:45 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 -- http://test.octopusgardenyoga.com/ GET / HTTP/1.1 Host: test.octopusgardenyoga.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5; __utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F; _radiant_session=34d224ec40d533ed1ac0fc36474823de If-Modified-Since: Fri, 25 Jul 2008 02:24:00 GMT If-None-Match: 465d8f78af243db4736e38c4452ee778 HTTP/1.x 304 Not Modified Content-Type: text/html; charset=utf-8 Last-Modified: Fri, 25 Jul 2008 03:01:58 GMT X-Runtime: 0.20425 Etag: 465d8f78af243db4736e38c4452ee778 Date: Fri, 25 Jul 2008 03:01:58 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 -- http://test.octopusgardenyoga.com/css/elastic GET /css/elastic HTTP/1.1 Host: test.octopusgardenyoga.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Accept: text/css,*/*;q=0.1 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://test.octopusgardenyoga.com/ Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5;
Re: [Radiant] rake rails:update:javascript and ActionController::InvalidAuthenticityToken
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
Re: [Radiant] undefined method `[]' for #
Radiant is not compatible with 1.8.7 because it is based on Rails 2.0.2. We'll upgrade to Rails 2.1.x soon. Sean Mark Kirby wrote: hi, I just updated my site to 0.6.7 gem and all was well. Then my system updated ruby to ruby 1.8.7 (2008-06-20 patchlevel 22). Now my front page just displays undefined method `[]' for # where it should be rendering the content. The layout is rendered fine just not the content. The relevant layout is: r:find url=/articles/ r:children:each limit=5 order=desc div id=xsnazzy_ class=xsnazzy b class=xtop b class=xb1/b b class=xb2/b b class=xb3/b b class=xb4/b /b div class=xboxcontent h3r:title //h3 r:content / pa href=http://www.srcdigest.org/issues/netbsd/r:breadcrumb //index.htmlRead more.../a/p p class=infoPosted by r:author / on r:date format=%b %d, %Y //p /div b class=xbottom b class=xb4/b b class=xb3/b b class=xb2/b b class=xb1/b /b /div /r:children:each /r:find Not quite sure where the trouble lies so any pointers are very much appreciated. Thanks Mark Kirby ___ 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
