Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)
Marshal, those links helped. The controller/models weren't declaring a status code on success (just on failures) and apparently LiteSpeed doesn't like that (though Mongrel and Webrick seem just fine with it). Anyway, I've released an updated version of SnS to address this. You can get it here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest The new and improved specs now claim it's working but I don't run LiteSpeed. Could you (or somebody) test this to make sure it solves this issue? -Chris Marshal Linfoot wrote: Hi Chris. I found a couple of threads in the litespeed forums that might be helpful. http://www.litespeedtech.com/support/forum/showthread.php?t=1422 http://www.litespeedtech.com/support/forum/showthread.php?t=821 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 Incise Release
Sean Cribbs wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.6.8 Incise adds a number of new features that enhance support for extensions and completes the project's move to github. Of special note are: * Extension installer/uninstaller scripts (script/extension) and a global 'extension registry' at http://ext.radiantcms.org * Support for freezing edge Radiant using 'git' * Remember-me functionality for the admin UI Thanks! I don't think that this changes the documentation much, so it's still good! Cheers, Mohit. 7/28/2008 | 2:36 PM. ___ 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
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
[Radiant] Re: Error when generating controller - create Radiant Extension
Please choose an alternative and run this generator again. I'd suggest doing just that... -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 Incise Release
There's a minor error in the radiant:update:configs task that I discovered this morning when fixing the demo site -- this should only affect upgrades from older versions. I have pushed the fix to github. If you want to stay on the gem, the workaround is to do two things: 1) Make sure you have a unique secret in your config.action_controller.session setting. 2) Add the line Page.load_subclasses to the end of the file (outside the config block). Sean Mohit Sindhwani wrote: Sean Cribbs wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.6.8 Incise adds a number of new features that enhance support for extensions and completes the project's move to github. Of special note are: * Extension installer/uninstaller scripts (script/extension) and a global 'extension registry' at http://ext.radiantcms.org * Support for freezing edge Radiant using 'git' * Remember-me functionality for the admin UI Thanks! I don't think that this changes the documentation much, so it's still good! Cheers, Mohit. 7/28/2008 | 2:36 PM. ___ 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] SnS extension problem -- Fixed (New SnS Release)
Hi Chris. I hate to say it, but no change. Downloaded the latest version from the link in your message to vendor/extensions/sns. Ran the rake tasks again just to be safe. Page still displays without any styling. Here's what I see when accessing the css/elastic page directly: [EMAIL PROTECTED] curl -I test.octopusgardenyoga.com/css/elastic HTTP/1.1 404 Not Found Content-Type: text/css; charset=utf-8 Last-Modified: Wed, 23 Jul 2008 16:36:09 GMT X-Runtime: 0.00239 ETag: f95c66d251410f2f579f72e87fd28049 Date: Mon, 28 Jul 2008 13:42:16 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 PS. Minor thing...version says 0.5 on the Admin UI Extensions page. On Mon, Jul 28, 2008 at 2:15 AM, Chris Parrish [EMAIL PROTECTED] wrote: Marshal, those links helped. The controller/models weren't declaring a status code on success (just on failures) and apparently LiteSpeed doesn't like that (though Mongrel and Webrick seem just fine with it). Anyway, I've released an updated version of SnS to address this. You can get it here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest The new and improved specs now claim it's working but I don't run LiteSpeed. Could you (or somebody) test this to make sure it solves this issue? -Chris -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 Incise Release
A brand new installation seems to require specifying the name of the directory for your installation. So, for example: -bash-3.00$ radiant Usage: /home/danorine/ruby/bin/radiant /path/to/radiant/app [options] Options: -r, --ruby=path Path to the Ruby binary of your choice (otherwise scripts use env, dispatchers current path). Default: /home/danorine/ruby/bin/ruby -d, --database=name Preconfigure for selected database (options: mysql, postgresql, sqlite3, sqlserver). Default: mysql Radiant Info: -v, --versionShow the Radiant version number and quit. -h, --help Show this help message and quit. General Options: -p, --pretendRun but do not make any changes. -f, --force Overwrite files that already exist. -s, --skip Skip files that already exist. -q, --quiet Suppress normal output. -t, --backtrace Debugging: show backtrace on errors. -c, --svnModify files with subversion. (Note: svn must be in path) and, yet: -bash-3.00$ radiant radiant create create CHANGELOG create CONTRIBUTORS create INSTALL create LICENSE create README create config create config/environments create config/environments/development.rb create config/environments/production.rb create config/environments/test.rb create db create log create public create public/.htaccess create public/404.html create public/500.html create public/dispatch.cgi create public/dispatch.fcgi create public/dispatch.rb create public/favicon.ico create public/images create public/images/admin create public/images/admin/add-child.png create public/images/admin/brown-bottom-line.gif create public/images/admin/clear-page-cache.png create public/images/admin/collapse.png create public/images/admin/expand.png create public/images/admin/layout.png create public/images/admin/minus.png create public/images/admin/new-homepage.png create public/images/admin/new-layout.png create public/images/admin/new-snippet.png create public/images/admin/new-user.png create public/images/admin/page.png create public/images/admin/plus.png create public/images/admin/remove-disabled.png create public/images/admin/remove.png create public/images/admin/snippet.png create public/images/admin/spinner.gif create public/images/admin/view-site.gif create public/images/admin/virtual-page.png create public/javascripts create public/javascripts/admin create public/javascripts/admin/admin.js create public/javascripts/admin/ruledtable.js create public/javascripts/admin/sitemap.js create public/javascripts/admin/tabcontrol.js create public/javascripts/application.js create public/javascripts/controls.js create public/javascripts/dragdrop.js create public/javascripts/effects.js create public/javascripts/pngfix.js create public/javascripts/prototype.js create public/javascripts/string.js create public/robots.txt create public/stylesheets create public/stylesheets/admin create public/stylesheets/admin/main.css create script create script/about create script/breakpointer create script/console create script/extension create script/performance create script/performance/benchmarker create script/performance/profiler create script/process create script/process/inspector create script/process/reaper create script/process/spawner create script/process/spinner create script/runner create script/server create script/spec create script/spec_server create script/version create vendor/extensions create vendor/plugins create script/generate create config/database.yml create Rakefile create config/routes.rb create config/environment.rb create config/boot.rb readme ../../../../INSTALL == Installation and Setup Once you have extracted the files into the directory where you would like to install Radiant: 1. Create the MySQL/PostgreSQL/SQLite databases for your Web site. You only need to create the production database, but you may also want to create the development and test databases if you are developing extensions or running tests. 2. Edit config/database.yml to taste. 3. Run the database bootstrap rake task: % rake production db:bootstrap (If you would like bootstrap your development database run
Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)
Oh, I forgot to mention, you'll need to clear the text asset cache too so that the new status header gets updated. You can do this one of two ways: 1. Save a javascript or stylesheet file (this will clear the cache for all javascripts and stylesheets). 2. Delete the text asset cache directory manually (the next request for each file will rebuild your cache). The default location for this is: [RADIANT_ROOT]/text_asset_cache. Also, I've just corrected the version issue and committed SnS v0.6.2 as the new latest version. (You can update your version of the extension but it won't affect this status header issue). Anyway, please test either version for me once you've cleared the cache and tell me if that fixes it. If it doesn't, please browse to the text asset cache directory and check the contents of the YML part of the cached file (given the default location above, it would be at: [RADIANT_ROOT]/text_asset_cache/stylesheet_cache/[your_file_name].yml). It should look something like: --- expires: 2009-07-28 10:25:57.84 -06:00 headers: Last-Modified: Thu, 19 Jun 2008 00:30:15 GMT Status: 200 OK cookie: [] Content-Type: text/css The line I care about is the Status: 200 OK one. Make sure it's there. -Chris Marshal Linfoot wrote: Hi Chris. I hate to say it, but no change. Downloaded the latest version from the link in your message to vendor/extensions/sns. Ran the rake tasks again just to be safe. Page still displays without any styling. Here's what I see when accessing the css/elastic page directly: [EMAIL PROTECTED] curl -I test.octopusgardenyoga.com/css/elastic HTTP/1.1 404 Not Found Content-Type: text/css; charset=utf-8 Last-Modified: Wed, 23 Jul 2008 16:36:09 GMT X-Runtime: 0.00239 ETag: f95c66d251410f2f579f72e87fd28049 Date: Mon, 28 Jul 2008 13:42:16 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 PS. Minor thing...version says 0.5 on the Admin UI Extensions page. On Mon, Jul 28, 2008 at 2:15 AM, Chris Parrish [EMAIL PROTECTED] wrote: Marshal, those links helped. The controller/models weren't declaring a status code on success (just on failures) and apparently LiteSpeed doesn't like that (though Mongrel and Webrick seem just fine with it). Anyway, I've released an updated version of SnS to address this. You can get it here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest The new and improved specs now claim it's working but I don't run LiteSpeed. Could you (or somebody) test this to make sure it solves this issue? -Chris ___ 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 -- Fixed (New SnS Release)
That did it! Working like a charm now. Thank you very much Chris for a great extension and for all the help getting it to work with LiteSpeed. On Mon, Jul 28, 2008 at 12:33 PM, Chris Parrish [EMAIL PROTECTED] wrote: Oh, I forgot to mention, you'll need to clear the text asset cache too so that the new status header gets updated. You can do this one of two ways: 1. Save a javascript or stylesheet file (this will clear the cache for all javascripts and stylesheets). 2. Delete the text asset cache directory manually (the next request for each file will rebuild your cache). The default location for this is: [RADIANT_ROOT]/text_asset_cache. Also, I've just corrected the version issue and committed SnS v0.6.2 as the new latest version. (You can update your version of the extension but it won't affect this status header issue). Anyway, please test either version for me once you've cleared the cache and tell me if that fixes it. If it doesn't, please browse to the text asset cache directory and check the contents of the YML part of the cached file (given the default location above, it would be at: [RADIANT_ROOT]/text_asset_cache/stylesheet_cache/[your_file_name].yml). It should look something like: --- expires: 2009-07-28 10:25:57.84 -06:00 headers: Last-Modified: Thu, 19 Jun 2008 00:30:15 GMT Status: 200 OK cookie: [] Content-Type: text/css The line I care about is the Status: 200 OK one. Make sure it's there. -Chris -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
