Re: [Radiant] problem with r:children:each by tag
E, Aren't those identical? John On Feb 5, 2013, at 7:05 AM, Erasmo da Narni wrote: hello! in page children, to whom I've added a Keywords field, if I use, for example, this by clause: r:children:each by=slug order=ASC the page renders fine but if I use: r:children:each by=slug order=ASC it gives: `by' attribute of `each' tag must be set to a valid field name any ideas on what i'm doing wrong? thanks in advance. --e -- --- You received this message because you are subscribed to the Google Groups Radiant CMS group. To unsubscribe from this group and stop receiving emails from it, send an email to radiantcms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- --- You received this message because you are subscribed to the Google Groups Radiant CMS group. To unsubscribe from this group and stop receiving emails from it, send an email to radiantcms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Radiant] TagError with aggregate:each in v1.1.1
r:aggregate paths='/about; /articles' r:children:each r:title/ /r:children:each /r:aggregate and r:aggregate paths=/about; /articles r:children:count/ /r:aggregate work on the demo site. inside the aggregate tag you have a collection that you still the use the children tags. On Monday, January 14, 2013 2:04:25 PM UTC-6, Jim Gay wrote: On Mon, Jan 14, 2013 at 11:46 AM, Mohit Sindhwani te...@onghu.comjavascript: wrote: Hi Jim, On 15/1/2013 12:27 AM, Jim Gay wrote: Benito, Try putting the paths inside the aggregate like this: r:aggregate paths=...r:each... I'd like to rework the way tags share information, but for now that should do it. I was trying to see if I could help, but I actually got the same error for: r:aggregate paths=/stage/utk/common;/stage/utk r:aggregate:children:count / /r:aggregate == `aggregate’ tag must contain a `paths’ or `urls’ attribute. Not sure what the cause is... What's the best way to try stuff? Would it be best to freeze radiant locally to the project and then try to edit that source code to see what the problem is? Interesting. We should have tests that cover this. Would either of you mind making an issue on github for this https://github.com/radiant/radiant/issues -- Write intention revealing code #= http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
[Radiant] Re: Radiant 1.1.0 Hurdles (Part 3) - Gallery
i don't think attachment_fu was ever updated to be fully compatible with ruby 1.9.x...see https://github.com/technoweenie/attachment_fu/issues/25 for this specific issue On Sunday, January 6, 2013 10:40:06 AM UTC-6, Mohit Sindhwani wrote: Hello! I'm continuing on with my explorations of a bunch of plugins that are important as I try to move my sites up to Radiant 1.1.0. So far, a bunch of things are working fine. From what I see, the following are Ok: * Aggregation (built in) * paperclipped (built in as clipped) * Copy Move * reorder_children extension - works fine (minor problem with SQLite3 fixed) [didn't try Blog Tags because I mainly needed next, prevbut this also offers time_ago_in_words] * cr = CodeRay -- works fine * co = Comments -- seems to work fine Now, I am on to Gallery and am facing problems. Is anyone successfully using Gallery (or equivalent) on Radiant 1.0+? Specifically, it seems to install fine using: Radiant Gallery - https://github.com/hairballopolis/radiant-gallery git clone git://github.com/technoweenie/attachment_fu.git vendor/plugins/attachment_fu git clone git://github.com/hairballopolis/radiant-gallery.git vendor/extensions/gallery bundle exec rake RAILS_ENV=production radiant:extensions:gallery:install I've got imagemagick installed (to a directory with no spaces in the path) and I have mini_magick. I edited config/extensions/gallery/gallery.yml to include: path_prefix: public/galleries processor: mini_magick restarted the server and went to create a gallery. creating a gallery works fine. then, I go to the gallery and click on New File - select a file from my filesystem and click on upload get a set of errors: /!\ FAILSAFE /!\ 2013-01-07 00:38:52 +0800 Status: 500 Internal Server Error can't convert nil into Integer E:/projects/radiant/test_v10/vendor/plugins/attachment_fu/init.rb:7:in `sprintf' E:/projects/radiant/test_v10/vendor/plugins/attachment_fu/init.rb:7:in `make_tmpname' C:/Ruby193/lib/ruby/1.9.1/tmpdir.rb:132:in `create' C:/Ruby193/lib/ruby/1.9.1/tempfile.rb:134:in `initialize' C:/Ruby193/lib/ruby/gems/1.9.1/gems/rack-1.1.3/lib/rack/utils.rb:547:in `new' Seems to be related to attachment_fu Does anyone have any thoughts on what I could do? Best Regards, Mohit.
Re: [Radiant] Re: Radiant 1.1.0 Hurdles (Part 2)
the latest comments gem ought to work On Tuesday, January 1, 2013 10:51:35 AM UTC-6, Mohit Sindhwani wrote: Hi Jim, Thanks for the note. On 1/1/2013 4:29 AM, Jim Gay wrote: Thanks for reporting all this. I'm planning to push breaking changes into the master branch soon, so tracking these things will be really helpful. Please do report any bugs you find on the github issues I will do so! I've made the changes to the documentation for reorder_children and sent a pull request to Benny. I've also fixed an issue in using previous and next in that extension, and pull request sent! If I can't find a way to fix something, I'll report issues. Before I get started (it's 1AM, so I'm off to bed here), are people facing any problems with comments or galleries with Radiant 1.1.0? Those are the next 2 I need to look at in evaluating whether I can move to Radiant 1.1.0. Best Regards, Mohit.
Re: [Radiant] System Stack Error for Radiant 1.1.0
I have not tried this yet, but I have heard from a very experienced source that using Thin makes this problem go away. Let me know if it works: http://code.macournoyer.com/thin/ On Nov 4, 2012, at 2:25 AM, Gang Wang wrote: I am new to radiant. After installing Radiant 1.1.0, I can get DEMO site running. But after viewing a few of pages (public pages or admin pages), I got those errors. SystemStackError (stack level too deep): Rendered rescues/_trace (1.4ms) Rendered rescues/_request_and_response (1.1ms) Rendering rescues/layout (internal_server_error) Illegal instruction: 4 I changed my ruby stack size and even reinstalled my system but still can't fix the errors. I didn't encounter any issues when I was with radiant 1.0.1. I am using rvm 1.16.17 (stable) brew installed GCC /usr/local/Cellar/apple-gcc42/4.2.1-5666.3 mysql-5.5.27 RubyGems Environment: - RUBYGEMS VERSION: 1.8.24 - RUBY VERSION: 1.9.3 (2012-10-12 patchlevel 286) [x86_64-darwin11.4.2] - INSTALLATION DIRECTORY: /Users/harry/.rvm/gems/ruby-1.9.3-p286@test1 - RUBY EXECUTABLE: /Users/harry/.rvm/rubies/ruby-1.9.3-p286/bin/ruby - EXECUTABLE DIRECTORY: /Users/harry/.rvm/gems/ruby-1.9.3-p286@test1/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-darwin-11 - GEM PATHS: - /Users/harry/.rvm/gems/ruby-1.9.3-p286@test1 - /Users/harry/.rvm/gems/ruby-1.9.3-p286@global - GEM CONFIGURATION: - :update_sources = true - :verbose = true - :benchmark = false - :backtrace = false - :bulk_threshold = 1000 - REMOTE SOURCES: - http://rubygems.org/ I have spent 2 weeks but still can't sort it out. Any help will be appreciated.
Re: [Radiant] Re: undefined method `keys' for #Syck::Omap:...
All five are firing for me just fine now. Thank you for looking into this. Radiant 1.1.0 Ruby 1.9.3p194 If there is a source of syck and !omap fu, can you point me towards it? Prosit! John On Sunday, 7 October 2012 12:08:05 UTC-7, Benny Degezelle wrote: I have removed the !omap statements; syck does not seem to handle them well.. At some point the order of db fixtures needed to be fixed to prevent errors, but this seems to be no longer the case. At least, the Roasters template never used !omap, and has always worked fine for me.. I just released 1.0.6 of radiant-site_templates-extension, could you update your Gemfile and affirm that all the templates can be chosen again? Cheers, Benny Op dinsdag 2 oktober 2012 18:24:03 UTC+2 schreef Jim Gay het volgende: Thanks for looking into this. We must have some YAML formatting problem in the site_templates extension (https://github.com/radiant/radiant-site_templates-extension) I ran into this before when I was testing things out for 1.9.3 (I think) but I don't understand why this would appear again after fixing it. I'll try to take a look, but if you have the opportunity, check out the YAML in that project. -Jim On Mon, Oct 1, 2012 at 10:23 PM, John Moroney jpmo...@gmail.com wrote: I've just replicated this. It appears during the rake db:boostrap, when selecting a database template. I get the error below when selecting options 4 and 5. 3 works, but I haven't tried either 1 or 2. Select a database template: 1. Empty 2. High Five! 3. Roasters (a coffee-themed blog / brochure) 4. Simple Blog 5. Styled Blog [1-5]: 5 rake aborted! undefined method `keys' for #Syck::Omap:0x007fe391e48a28 Ruby 1.9.3 Gem 1.8.24 Radiant 1.1.0 Rails 2.3.14 John Moroney On Friday, 7 September 2012 14:31:05 UTC-7, IamNaN wrote: Tried three times to get Radiant installed on Linode with Ruby 1.9.3-p194 and postgres. Using the installation and setup directions in INSTALL.md, I get the title error trying to populate the database with `bundle exec rake production db:bootstrap`. Can you help with that? On another note... the system requirements aren't listed anywhere that I can find. Rails 3 gets blown away by running `gem install radiant` (I think because Gemfile.lock is included in the gem). And I'm getting numerous deprecation warnings throughout the installation process. Radiant development is still active, right? -- Write intention revealing code #= http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
[Radiant] Re: undefined method `keys' for #Syck::Omap:...
I've just replicated this. It appears during the rake db:boostrap, when selecting a database template. I get the error below when selecting options 4 and 5. 3 works, but I haven't tried either 1 or 2. Select a database template: 1. Empty 2. High Five! 3. Roasters (a coffee-themed blog / brochure) 4. Simple Blog 5. Styled Blog [1-5]: 5 rake aborted! undefined method `keys' for #Syck::Omap:0x007fe391e48a28 Ruby 1.9.3 Gem 1.8.24 Radiant 1.1.0 Rails 2.3.14 John Moroney On Friday, 7 September 2012 14:31:05 UTC-7, IamNaN wrote: Tried three times to get Radiant installed on Linode with Ruby 1.9.3-p194 and postgres. Using the installation and setup directions in INSTALL.md, I get the title error trying to populate the database with `bundle exec rake production db:bootstrap`. Can you help with that? On another note... the system requirements aren't listed anywhere that I can find. Rails 3 gets blown away by running `gem install radiant` (I think because Gemfile.lock is included in the gem). And I'm getting numerous deprecation warnings throughout the installation process. Radiant development is still active, right?
Re: [Radiant] Cache seems determined to be on 300 seconds
Jim, Thanks for the reply. I think I've narrowed the issue down to file system resources. If the file system is changed and saved, the cache does not refresh. A web inspector shows the 300 second setting. If, however, a page is saved in the CMS itself, the cache refreshes and the changes are loaded, including all filesystem changes. A conversation with a very experienced Radiant user has described this behaviour as normal. I have never seen Radiant behave this way. I'd like to try your solution of changing set_cache_control. If I'm successful, I'll post it here. John On 2012-07-12, at 9:16 AM, Jim Gay wrote: I think this might have to do with Rails reloading classes in development mode. If we set the timeout during the initialization process, that step is skipped during a reload. Of the top of my head, it might be necessary to rewrite set_cache_control to overcome this. -Jim On Wed, Jul 11, 2012 at 7:41 PM, John Moroney jpmoro...@gmail.com wrote: I'm in the development environment and the cache is locked on five minutes. The config settings are correct, and I see nothing obvious in the extensions that would cause a conflict. This install was also working just fine until it wasn't. I noticed on line 525 of the changelog that a similar issue came up and was fixed by Mr. Long, but that issue describes the behaviour. Any ideas would be greatly appreciated. The extensions are: file_system_resources page_factory page_parts ruby 1.9.2 radiant 1.0.1p180 -- Write intention revealing code #= http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
[Radiant] Cache seems determined to be on 300 seconds
I'm in the development environment and the cache is locked on five minutes. The config settings are correct, and I see nothing obvious in the extensions that would cause a conflict. This install was also working just fine until it wasn't. I noticed on line 525 of the changelog that a similar issue came up and was fixed by Mr. Long, but that issue describes the behaviour. Any ideas would be greatly appreciated. The extensions are: file_system_resources page_factory page_parts ruby 1.9.2 radiant 1.0.1p180
[Radiant] Re: Radiant app on heruko errors on first request after idle
i've run into the same issue and found the easiest solution to be completely disabling css generation in production; e.g. add Sass::Plugin.options[:never_update] = true to `config/environments/production.rb` On Thursday, June 28, 2012 1:55:54 AM UTC-5, jsmorris wrote: Due to my site having low volume, heroku spins down/idles my dyno. So, when the first request comes in I get a 500 Internal Server Error. Then, when I refresh, the app comes up as expected. Has anyone experienced this and could help with a solution? The interesting line in the log output is 2012-06-28T04:18:31+00:00 app[web.1]: Permission denied - /app/public/stylesheets/admin/assets.css Thanks, Jason Here is my log when this happens 2012-06-28T03:42:45+00:00 heroku[web.1]: Unidling 2012-06-28T03:42:45+00:00 heroku[web.1]: State changed from down to starting 2012-06-28T03:42:50+00:00 heroku[web.1]: Starting process with command `thin -p 52699 -e staging -R /home/heroku_rack/heroku.ru start` 2012-06-28T03:42:57+00:00 app[web.1]: There is no support for CoffeeScript 2012-06-28T03:42:58+00:00 app[web.1]: [Clipped] Using image thumbnailer: ImageMagick 6.6.0-4 2010-06-01 Q16 http://www.imagemagick.org 2012-06-28T03:42:59+00:00 app[web.1]: Thin web server (v1.2.6 codename Crazy Delicious) 2012-06-28T03:42:59+00:00 app[web.1]: Listening on 0.0.0.0:52699, CTRL+C to stop 2012-06-28T03:42:59+00:00 app[web.1]: Maximum connections set to 1024 2012-06-28T03:43:00+00:00 heroku[web.1]: State changed from starting to up 2012-06-28T03:43:03+00:00 heroku[router]: GET pisr-staging.heroku.com/favicon.ico dyno=web.1 queue=0 wait=0ms service=9ms status=200 bytes=0 2012-06-28T04:18:31+00:00 heroku[router]: GET pisr-staging.heroku.com/cleanple-home/ dyno=web.1 queue=0 wait=0ms service=1746ms status=500 bytes=309 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin/compiler.rb:356:in `initialize' 2012-06-28T04:18:31+00:00 app[web.1]: /!\ FAILSAFE /!\ Wed Jun 27 21:18:31 -0700 2012 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin/compiler.rb:356:in `open' 2012-06-28T04:18:31+00:00 app[web.1]: Permission denied - /app/public/stylesheets/admin/assets.css 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin/compiler.rb:356:in `write_file' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin/compiler.rb:349:in `update_stylesheet' 2012-06-28T04:18:31+00:00 app[web.1]: Status: 500 Internal Server Error 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin/compiler.rb:202:in `update_stylesheets' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin/compiler.rb:200:in `each' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin.rb:81:in `update_stylesheets' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin/rack.rb:51:in `call' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin/compiler.rb:200:in `update_stylesheets' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/sass-3.1.19/rails/../lib/sass/../sass/plugin.rb:54:in `check_for_updates' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/rack-cache-1.0.3/lib/rack/cache/context.rb:132:in `forward' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/rack-cache-1.0.3/lib/rack/cache/context.rb:243:in `fetch' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/rack-cache-1.0.3/lib/rack/cache/context.rb:181:in `lookup' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/rack-cache-1.0.3/lib/rack/cache/context.rb:65:in `call!' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/rack-cache-1.0.3/lib/rack/cache/context.rb:50:in `call' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/actionpack-2.3.14/lib/action_controller/string_coercion.rb:25:in `call' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/rack-1.1.3/lib/rack/head.rb:9:in `call' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/rack-1.1.3/lib/rack/methodoverride.rb:24:in `call' 2012-06-28T04:18:31+00:00 app[web.1]: /app/.bundle/gems/ruby/1.8/gems/actionpack-2.3.14/lib/action_controller/params_parser.rb:15:in `call' 2012-06-28T04:18:31+00:00 app[web.1]:
[Radiant] Re: malformatted comment rendering with radiant-comments extension
are you on ruby 1.9 by chance? i ran into a similar issue the other day but haven't had time to track it down yet. On Wednesday, June 20, 2012 6:06:37 AM UTC-5, Eren Gölge wrote: I try to render my entered comments but it write it on in very silly format like: [\r\n \r\n \r\n \r\n \r\n Eren said on Wednesday, June 20, 2012:\r\n \r\n sdfwfwefwf \r\n \r\n \r\n\r\n , \r\n \r\n \r\n \r\n \r\n asdad said on Wednesday, June 20, 2012:\r\n \r\n asdasda \r\n \r\n \r\n\r\n , \r\n \r\n \r\n \r\n \r\n asdad said on Wednesday, June 20, 2012:\r\n \r\n asdasda \r\n \r\n \r\n\r\n , \r\n \r\n \r\n \r\n \r\n adad said on Wednesday, June 20, 2012:\r\n \r\n daadasdasd \r\n \r\n \r\n\r\n ] this is what actually seem on my page. What is the problem behind it, any idea? This is what I use for rendering. r:comments:field div class=comment id=comment-r:id/ p class=author r:if_author_urla href=r:author_url/ title=Visit r:author/'s website/r:if_author_url r:author/r:if_author_url/a/r:if_author_urlsaid on r:date/: /p div class=content_htmlr:content_html //div r:if_selectedpem r:if_approvedThanks for your comment!/r:if_approved r:unless_approvedThanks for your comment, it has gone into the moderation queue and will be dealt with shortly./r:unless_approved /em/p/r:if_selected /div /r:comments:field
[Radiant] Re: Deployment recommendations?
cool. i'll try to duplicate your setup in the next couple of days (and update the wiki if you haven't got to it yet) On Thursday, April 19, 2012 6:23:40 PM UTC-5, jsntv200 wrote: Radiant runs fine on cedar. Here's a site Im currently building on the cedar stack : http://queminhluu-staging.herokuapp.com/ But there are a few gotcha's with the Gemfile, you'll also need to add a Procfile and delete the config.ru (breaks compass for some reason I think). Here's a gist : https://gist.github.com/2424787 Locally I generally run without the production group : $ bundle install --without production I haven't included any extensions in the Gemfile but if you want to use Heroku's memcache add-on with Radiant then a simple extension I created seems to do the trick, just add it to the production group : gem radiant-heroku_dalli-extension, ~ 1.0.0 Cedar also removed the Varnish caching layer but I've been getting pretty good results out of Cloud Flare [https://www.cloudflare.com/] cheers jt On Apr 20, 8:22 am, John Moroney j...@juniork.com wrote: Jim, bundle update returns radiant (1.0.1) in the gemfile.lock, which crashes the app on heroku radiant seems to like only the bamboo stack, if that is important I'm currently having a beast of a time getting Radiant to find the js and image files. They are not being pointed to correctly in the admin interface, though the call is identical to the local copy. i would very much like to help in any way I can to simplify the radiant/heroku process. My biggest hurdle has always been getting all the necessary information in one source, and then getting current information. John On Apr 19, 2012, at 8:29 AM, Jim Gay wrote: I definitely want to support Heroku easily. Any bug reports or code you can provide would be really helpful. On Thu, Apr 19, 2012 at 1:49 AM, Bruce Davison bruce.au@gmail.com wrote: I Deploy to Bamboo for Radiant. I only use Cedar for Rails 3. Also Heroku doesn't use Sqlite3 it uses Postgresql. If you are using taps to push your db it creates a Postgresql database Hope that helps -- Bruce Davison Sent with Sparrow On Thursday, 19 April 2012 at 11:52 AM, John Moroney wrote: It was that I deployed to the cedar stack, mostly. On cedar, it would not resolve sqlite3, saying it was either missing or needed a sqlite3.h. I also had to change the gemfile.lock from radiant (1.0.1) to radiant (1.0.0) for the app to fire. I'm still showing some unresolved dependencies which I'm trying to run down, and now my admin/content is css-less. And only on Heroku. Locally? Brilliant as ever. For the record, thanks for Radiant. I've been using it since 2006-2007. John Moroney On Apr 17, 2012, at 9:01 PM, john wrote: what exactly is the problem with heroku? On Tuesday, April 17, 2012 8:52:03 PM UTC-5, John Moroney wrote: I usually deploy to Heroku, but can someone suggest a more Radiant-friendly server? It's the deployment which seems to be the bottleneck, even after the experience of many installs. Heroku has many advantages, one of which is being free for micro-scale sites and blogs. Are there low-priced, Rails-friendly servers that are still in the Ruby/Rails community? -- Write intention revealing code #=http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
Re: [Radiant] Re: Deployment recommendations?
On Thursday, April 19, 2012 5:22:46 PM UTC-5, John Moroney wrote: Jim, bundle update returns radiant (1.0.1) in the gemfile.lock, which crashes the app on heroku if you use radiant from git 1.0.1 works fine on heroku. # Gemfile gem radiant, 1.0.1, :git = git://github.com/radiant/radiant.git, :tag = 1.0.1 the released gem was built with ruby 1.9 and rubygems 1.8 which leads to a gem incompatible with rubygems 1.3.7 which heroku uses. radiant seems to like only the bamboo stack, if that is important right. as far as i know heroku only supports rails 3.x on cedar and radiant is on 2.3.x. bamboo and cedar both support ruby 1.9.2 so if there is nothing stopping you from using bamboo it's certainly going to make life easier at least until radiant is on a newer rails.
Re: [Radiant] Re: Deployment recommendations?
Joel, You're right. I'd like to do a step by step so those with fists of ham like myself can have a five minute install. Sent from my iPhone On 2012-04-19, at 4:54 PM, Joel Oliveira joel.olive...@gmail.com wrote: On my phone and haven't checked, but are all these nuggets of quality heroku-related information up on the radiant site and/or github wiki? On Apr 19, 2012, at 7:40 PM, jsntv200 jsntv...@gmail.com wrote: Yep. I never got around to looking into it since everything seems to work fine if you delete it. On Apr 20, 9:31 am, John Moroney j...@juniork.com wrote: Do you suppose something in config.ru might be causing Heroku to misplace my image and js files in the admin interface? This is driving me nuts. github.com/johnmoroney/sugarcat On Apr 19, 2012, at 4:23 PM, jsntv200 wrote: Radiant runs fine on cedar. Here's a site Im currently building on the cedar stack : http://queminhluu-staging.herokuapp.com/ But there are a few gotcha's with the Gemfile, you'll also need to add a Procfile and delete the config.ru (breaks compass for some reason I think). Here's a gist : https://gist.github.com/2424787 Locally I generally run without the production group : $ bundle install --without production I haven't included any extensions in the Gemfile but if you want to use Heroku's memcache add-on with Radiant then a simple extension I created seems to do the trick, just add it to the production group : gem radiant-heroku_dalli-extension, ~ 1.0.0 Cedar also removed the Varnish caching layer but I've been getting pretty good results out of Cloud Flare [https://www.cloudflare.com/] cheers jt On Apr 20, 8:22 am, John Moroney j...@juniork.com wrote: Jim, bundle update returns radiant (1.0.1) in the gemfile.lock, which crashes the app on heroku radiant seems to like only the bamboo stack, if that is important I'm currently having a beast of a time getting Radiant to find the js and image files. They are not being pointed to correctly in the admin interface, though the call is identical to the local copy. i would very much like to help in any way I can to simplify the radiant/heroku process. My biggest hurdle has always been getting all the necessary information in one source, and then getting current information. John On Apr 19, 2012, at 8:29 AM, Jim Gay wrote: I definitely want to support Heroku easily. Any bug reports or code you can provide would be really helpful. On Thu, Apr 19, 2012 at 1:49 AM, Bruce Davison bruce.au@gmail.com wrote: I Deploy to Bamboo for Radiant. I only use Cedar for Rails 3. Also Heroku doesn't use Sqlite3 it uses Postgresql. If you are using taps to push your db it creates a Postgresql database Hope that helps -- Bruce Davison Sent with Sparrow On Thursday, 19 April 2012 at 11:52 AM, John Moroney wrote: It was that I deployed to the cedar stack, mostly. On cedar, it would not resolve sqlite3, saying it was either missing or needed a sqlite3.h. I also had to change the gemfile.lock from radiant (1.0.1) to radiant (1.0.0) for the app to fire. I'm still showing some unresolved dependencies which I'm trying to run down, and now my admin/content is css-less. And only on Heroku. Locally? Brilliant as ever. For the record, thanks for Radiant. I've been using it since 2006-2007. John Moroney On Apr 17, 2012, at 9:01 PM, john wrote: what exactly is the problem with heroku? On Tuesday, April 17, 2012 8:52:03 PM UTC-5, John Moroney wrote: I usually deploy to Heroku, but can someone suggest a more Radiant-friendly server? It's the deployment which seems to be the bottleneck, even after the experience of many installs. Heroku has many advantages, one of which is being free for micro-scale sites and blogs. Are there low-priced, Rails-friendly servers that are still in the Ruby/Rails community? -- Write intention revealing code #=http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
Re: [Radiant] Re: Deployment recommendations?
It was that I deployed to the cedar stack, mostly. On cedar, it would not resolve sqlite3, saying it was either missing or needed a sqlite3.h. I also had to change the gemfile.lock from radiant (1.0.1) to radiant (1.0.0) for the app to fire. I'm still showing some unresolved dependencies which I'm trying to run down, and now my admin/content is css-less. And only on Heroku. Locally? Brilliant as ever. For the record, thanks for Radiant. I've been using it since 2006-2007. John Moroney On Apr 17, 2012, at 9:01 PM, john wrote: what exactly is the problem with heroku? On Tuesday, April 17, 2012 8:52:03 PM UTC-5, John Moroney wrote: I usually deploy to Heroku, but can someone suggest a more Radiant-friendly server? It's the deployment which seems to be the bottleneck, even after the experience of many installs. Heroku has many advantages, one of which is being free for micro-scale sites and blogs. Are there low-priced, Rails-friendly servers that are still in the Ruby/Rails community?
Re: [Radiant] Re: Scheduler extension
thank you for helping out. i'll get this merged and a gem pushed today. On Thursday, March 29, 2012 11:52:31 AM UTC-5, marshal wrote: Thanks for the pointers, John. I forked the repo, committed/pushed my changes, and initiated a pull request. I get the feeling though that Sean Cribbs isn't watching the original repo anymore -- I didn't see any notifications for the pull request. What's next? Assuming my changes are incorporated into the original repo, would someone (Sean or some other Radiant guru) build the gem and publish it on RubyGems? Hope this helps... -- marshal On Thu, Mar 29, 2012 at 9:36 AM, john johnm...@gmail.com wrote: check out http://help.github.com/fork-a-repo/ and http://help.github.com/send-pull-requests/
[Radiant] @font-face
1.0.0.rc4
I am having the strangest error using @font-face. It keeps returning a
404 for the font, and the CMS assets tab/filter does not recognize the
font itself, i.e. click the tab and the fonts don't show up. The
other assets are found easily enough--just not fonts.
I have used @font-face in the previous version of Radiant without
issue. This is not a CSS forum, but I am beginning to wonder if I'm
overlooking something. The problem is both on Heroku and local.
John Moroney
@font-face
:font-family 'OstrichBlack'
:src url('/assets/8/ostrich-black-webfont.eot')
:src url('/assets/8/ostrich-black-webfont.eot?#iefix')
format('embedded-opentype'), url('/assets/11/ostrich-black-
webfont.woff') format('woff'), url('/assets/10/ostrich-black-
webfont.ttf') format('truetype'), url('/assets9/ostrich-black-
webfont.svg#OstrichBlack') format('svg')
:font-weight normal
Re: [Radiant] Re: Create Permalink Dynamically
thanks jim. i was thinking of r:path/.
On Tuesday, March 13, 2012 5:50:07 AM UTC-5, Jim Gay wrote:
I think you mean r:path /
A r:link would include the a href=...
--
Write intention revealing code #= http://www.clean-ruby.com
Jim Gay
Saturn Flyer LLC
571 403 0338
On Mar 12, 2012, at 9:57 PM, john johnm...@gmail.com wrote:
what about http://example.comr:link/? r:link/ should return something
like /path/to/page/ or /2012/03/12/slug/ if you're using the archive
extension.
On Monday, March 12, 2012 8:32:28 PM UTC-5, Bentley78 wrote:
I'm trying to add facebook comments to my site and when I get teh code
Im presented with the following:
`div id=fb-root/div
script(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = //connect.facebook.net/en_US/all.js#xfbml=1;
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));/script`
`div class=fb-comments data-href=http://example.com;
data-num-posts=2 data-
width=470/div`
What I'd like to do is where the data-href resides I'd like to
create
a permalink to my page/pot dynamically. is there a radiant tag or
something similar to do this? I can't seem to find one.
[Radiant] Re: Error creating my first Radiant project
i think this is a problem that only happens on older versions of rubygems. what version does `gem -v` show? On Tuesday, March 13, 2012 7:15:26 AM UTC-5, Maik wrote: Hi, I just installed Radiant on Debian 6 via Gems. When I execute radiant --database mysql ~/test-project radiant stops with the following error: WARNING: Invalid .gemspec format in '/var/lib/gems/1.8/specifications/ radiant-1.0.1.gemspec' /usr/lib/ruby/1.8/rubygems.rb:779:in `report_activate_error': Could not find RubyGem radiant (= 0) (Gem::LoadError) from /usr/lib/ruby/1.8/rubygems.rb:214:in `activate' from /usr/lib/ruby/1.8/rubygems.rb:1082:in `gem' from /var/lib/gems/1.8/bin/radiant:18 Any idea what is wrong? I am running Ruby 1.8.7 and rails has version 2.3.14. However, just running rails gives me the same error about the radiant-1.0.1.gemspec as above. Thanks, -Maik
[Radiant] Re: Create Permalink Dynamically
ah. didn't realize you were using an old version of radiant. if you ever
upgrade you'll need to replace r:url/ with r:path/
On Tuesday, March 13, 2012 9:46:18 AM UTC-5, Bentley78 wrote:
Actually r:y=url works. So data-href=http://www.example.comr:url /
seems to work great. I trolled through the mailing lists and found
it.
On Mar 13, 10:13 am, john johnm...@gmail.com wrote:
thanks jim. i was thinking of r:path/.
On Tuesday, March 13, 2012 5:50:07 AM UTC-5, Jim Gay wrote:
I think you mean r:path /
A r:link would include the a href=...
--
Write intention revealing code #=http://www.clean-ruby.com
Jim Gay
Saturn Flyer LLC
571 403 0338
On Mar 12, 2012, at 9:57 PM, john johnm...@gmail.com wrote:
what abouthttp://example.comr:link/? r:link/ should return
something
like /path/to/page/ or /2012/03/12/slug/ if you're using the archive
extension.
On Monday, March 12, 2012 8:32:28 PM UTC-5, Bentley78 wrote:
I'm trying to add facebook comments to my site and when I get teh
code
Im presented with the following:
`div id=fb-root/div
script(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = //connect.facebook.net/en_US/all.js#xfbml=1;
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));/script`
`div class=fb-comments data-href=http://example.com;
data-num-posts=2 data-
width=470/div`
What I'd like to do is where the data-href resides I'd like to
create
a permalink to my page/pot dynamically. is there a radiant tag or
something similar to do this? I can't seem to find one.
Re: [Radiant] Re: Error creating my first Radiant project
but can't we build the gem to accomodate this? some people might not want to move away from their package manager provided software. and we probably don't want to have to explain this over and over. Maik can you try this: sudo gem uninstall radiant wget http://goo.gl/jx8vr sudo gem install radiant-1.0.1.gem radiant --database mysql ~/test-project On Tuesday, March 13, 2012 9:43:59 AM UTC-5, Jordon Bedwell wrote: RubyGems (for Ruby1.8) provided by Debian tends to be outdated and this is a well known problem. If you are using system ruby, use Ruby gems installed via RubyGems.org unless it's 1.9.3. On Tue, Mar 13, 2012 at 9:35 AM, john johnm...@gmail.com wrote: i think this is a problem that only happens on older versions of rubygems. what version does `gem -v` show? On Tuesday, March 13, 2012 7:15:26 AM UTC-5, Maik wrote: Hi, I just installed Radiant on Debian 6 via Gems. When I execute radiant --database mysql ~/test-project radiant stops with the following error: WARNING: Invalid .gemspec format in '/var/lib/gems/1.8/specifications/ radiant-1.0.1.gemspec' /usr/lib/ruby/1.8/rubygems.rb:779:in `report_activate_error': Could not find RubyGem radiant (= 0) (Gem::LoadError) from /usr/lib/ruby/1.8/rubygems.rb:214:in `activate' from /usr/lib/ruby/1.8/rubygems.rb:1082:in `gem' from /var/lib/gems/1.8/bin/radiant:18 Any idea what is wrong? I am running Ruby 1.8.7 and rails has version 2.3.14. However, just running rails gives me the same error about the radiant-1.0.1.gemspec as above. Thanks, -Maik
Re: [Radiant] Connection Error using Radiant Clipped Extension 1.0.17 in Radiant 1.0 to upload assets to Amazon S3
are you using the clipped_config.rb initializer as a template? provide the
contents of that file if so. if not run rake
radiant:extensions:clipped:initialize and try using the template from
config/initializers/clipped_config.rb to get setup.
On Friday, March 9, 2012 6:41:48 PM UTC-6, jsmorris wrote:
I triple checked my key and secret and they are correct. I went ahead and
re-entered them and still get the same error. I use the exact same ones to
connect to S3 using other tools.
What does it mean by signing method? What do you mean by credentials? My
amazon s3 key and secret?
Also, the docs mentioned setting the region, but I tried US Standard and I
was unable to save that setting in Radiant.
Jason
On Friday, March 9, 2012 5:15:39 AM UTC-7, Jim Gay wrote:
The error you showed has this message The request signature we
calculated does not match the signature you provided. Check your key
and signing method
Are you sure you are using the correct credentials to connect to s3?
On Fri, Mar 9, 2012 at 12:50 AM, jsmorris jsmor...@gmail.com wrote:
I recently upgraded a project in development from radiant 0.9.1 to
1.0.0 and
wanted to try out the radiant clipped extension to manage assets. I
followed the instruction in the extension's github
page https://github.com/radiant/radiant-clipped-extension. My site
comes
up, but when I attempt to upload an asset I get the below authentication
error. I am at a lost how to troubleshoot what is going on here. Does
anyone have any experience with this and what I could do to fix it?
Thanks,
Jason
Excon::Errors::Forbidden in Admin/assetsController#create
Expected(200) = Actual(403 Forbidden)
request =
{:body=#File:/var/folders/-k/-kHlAirEHaWd-LPqwo6ceU+++TI/-Tmp-/stream20120308-7303-u83ylu-0.gif,
:ssl_verify_peer=true, :connect_timeout=60, :port=443,
:expects=200,
:write_timeout=60, :instrumentor_name=excon,
:path=/%2FUsers%2Fjsmorris%2Fprojects%2Fresitrac%2Fpublic%2Fsystem%2Fassets%2F1%2Foriginal%2FGatorHead.gif,
:host=com, :mock=false, :query=nil, :method=PUT,
:read_timeout=60,
:headers={Authorization=AWS :x,
x-amz-acl=public-read, Date=Fri, 09 Mar 2012 05:28:58 +,
Content-Type=image/gif, Content-Length=1780, Host=com:443},
:retry_limit=4, :idempotent=true, :scheme=https}
response = #Excon::Response:0x1074706f0
@headers={x-amz-id-2=U2YEilrayC4DXSgyeRY6/93kVqcS7TARsnEjb2XQ5OT1C3KKB3xZPSNubgoQH3UG,
Transfer-Encoding=chunked, Date=Fri, 09 Mar 2012 05:28:57 GMT,
Content-Type=application/xml,
x-amz-request-id=891AA234FA919418,
Server=AmazonS3, Connection=close}, @body=?xml
version=\1.0\
encoding=\UTF-8\?\nErrorCodeSignatureDoesNotMatch/CodeMessageThe
request signature we calculated does not match the signature you
provided.
Check your key and signing method./MessageStringToSignBytes50 55 54
0a
0a 69 6d 61 67 65 2f 67 69 66 0a 46 72 69 2c 20 30 39 20 4d 61 72 20 32
30
31 32 20 30 35 3a 32 38 3a 35 38 20 2b 30 30 30 30 0a 78 2d 61 6d 7a 2d
61
63 6c 3a 70 75 62 6c 69 63 2d 72 65 61 64 0a 2f 63 6f 6d 2f 25 32 46 55
73
65 72 73 25 32 46 6a 73 6d 6f 72 72 69 73 25 32 46 70 72 6f 6a 65 63 74
73
25 32 46 72 65 73 69 74 72 61 63 25 32 46 70 75 62 6c 69 63 25 32 46 73
79
73 74 65 6d 25 32 46 61 73 73 65 74 73 25 32 46 31 25 32 46 6f 72 69 67
69
6e 61 6c 25 32 46 47 61 74 6f 72 48 65 61 64 2e 67 69
66/StringToSignBytesRequestId891AA234FA919418/RequestIdHostIdU2YEilrayC4DXSgyeRY6/93kVqcS7TARsnEjb2XQ5OT1C3KKB3xZPSNubgoQH3UG/HostIdSignatureProvidedyB3fQKBjpt+vfDWHCSvdAmIbGmc=/SignatureProvidedStringToSignPUT\n\nimage/gif\nFri,
09 Mar 2012 05:28:58
+\nx-amz-acl:public-read\n/com/%2FUsers%2Fjsmorris%2Fprojects%2Fresitrac%2Fpublic%2Fsystem%2Fassets%2F1%2Foriginal%2FGatorHead.gif/StringToSignAWSAccessKeyId1EVJJH3NN32Z416D20G2/AWSAccessKeyId/Error,
@status=403
RAILS_ROOT: /Users/jsmorris/projects/resitrac
Application Trace | Framework Trace | Full Trace
/Users/jsmorris/.rvm/gems/ree-1.8.7-2011.03@resitrac/gems/excon-0.9.6/lib/excon/connection.rb:229:in
`request_kernel'
/Users/jsmorris/.rvm/gems/ree-1.8.7-2011.03@resitrac/gems/excon-0.9.6/lib/excon/connection.rb:86:in
`request'
/Users/jsmorris/.rvm/gems/ree-1.8.7-2011.03@resitrac/gems/fog-1.1.2/lib/fog/core/connection.rb:20:in
`request'
/Users/jsmorris/.rvm/gems/ree-1.8.7-2011.03@resitrac/gems/fog-1.1.2/lib/fog/aws/storage.rb:381:in
`request'
/Users/jsmorris/.rvm/gems/ree-1.8.7-2011.03@resitrac/gems/fog-1.1.2/lib/fog/aws/requests/storage/put_object.rb:43:in
`put_object'
/Users/jsmorris/.rvm/gems/ree-1.8.7-2011.03@resitrac/gems/fog-1.1.2/lib/fog/aws/models/storage/file.rb:119:in
`save'
/Users/jsmorris/.rvm/gems/ree-1.8.7-2011.03@resitrac/gems/fog-1.1.2/lib/fog/core/collection.rb:50:in
`create'
[Radiant] Re: [ANN] Radiant CMS 1.0
http://git.io/radiant-simple-install has been updated to use 1.0.0 now. On Tuesday, February 28, 2012 9:46:49 AM UTC-6, Jim Gay wrote: I'm proud to be able to release 1.0: http://radiantcms.org/download/ Many good things have gone into this long-awaited release. The 1.0 series will be the last on Rails 2. Only minor fixes will go into any further 1.x releases and our effort will be focused on Rails 3 and further modularization of Radiant. WHAT IS RADIANT CMS? Radiant is a no-fluff content management system made for designers and programmers and is ideal for use on small teams. It is similar to Movable Type or Textpattern, but is much more than a blogging engine. Radiant features: * An elegant user interface * The ability to arrange pages in a hierarchy * Flexible templating with layouts, snippets, page parts, and a custom tagging language (Radius: http://radius.rubyforge.org) * A dynamic extension system * A simple user management/permissions system * Support for Markdown and Textile as well as traditional HTML (it's easy to create other filters) * Operates in two modes: dev and production depending on the URL * A caching system which expires pages every 5 minutes * Built using Ruby on Rails (which means that extending Radiant is as easy as any other Rails application) * Licensed under the MIT-License * And much more... There's even a live demo over on the project Web site: http://radiantcms.org/demo/ WHAT'S NEW IN THIS RELEASE? Radiant now runs on Ruby 1.9! We now support Bundler and have a default way to manage attachments, stylesheets (with support for Sass/SCSS), JS (with support for CoffeeScript), built-in page preview, and many more features. INSTALLATION https://gist.github.com/1540782 CONTRIBUTORS Radiant wouldn't be possible without the help of some fine people. The following people have made contributions to this release: Jason TaylorJohannes Fahrenkrug William RossMark Reginald James John MuhlSamuel Whited Benny Degezelle Josh French Jim Gay Oriol Gual Wes GambleMichal Cichra Michael StalkerAndrew vonderLuft Chris ParrishDirk Kelly Jeff Casimir vanderhoorn John LongMario Visic Gert Goet https://github.com/radiant/radiant/contributors SUPPORT The best place to get support is definitely on the Radiant mailing list. There's a crowd of people there who have been hanging around for many moons now. Newbie questions are welcome! To sign up, go to: http://radiantcms.org/mailing-list/ The Radiant mailing list is also accessible via Ruby forum: http://www.ruby-forum.com/forum/21 Enjoy! -- Jim Gay for the Radiant CMS Dev Team http://radiantcms.org
Re: [Radiant] How to add a before_filter?
vapor is working (and as jason said does what you want) with a 1.0.0.rc4 site so should be fine with rc5 and the eventual 1.x releases. it could use some ui love but it's functional.
Re: [Radiant] Could not find a JavaScript runtime deploying Radiant 1.0.0rc4 to Heroku
Mick, Sorry, I misspoke about rc5. John On Feb 12, 2012, at 5:57 PM, Jim Gay wrote: rc5 of what is out? Mick, I want to figure out a way to gracefully fail and remove coffee-script support if you don't want it. But you should be able to add this to your Gemfile: gem therubyracer Let us know if that doesn't work out. On Sun, Feb 12, 2012 at 1:16 PM, John Moroney j...@juniork.com wrote: Mick, I have seen this horrible thing before. I fixed this by installing the gem therubyracer. Others swear by nodejs. Also, rc5 is out and does seem more stable. Best of luck, John Vancouver, BC On Jan 29, 2012, at 5:13 AM, Mick Hollins wrote: Hi, I'm attempting to deploy Radiant 1.0.0rc4 to Heroku, but I get the following error: Could not find a JavaScript runtime The full log output is here: https://gist.github.com/1698750 Anyone seen this before? Any help would be greatly appreciated. thanks, mick -- Write intention revealing code #= http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
[Radiant] Re: Backup / convert / export a Radiant site to HTML
what about: wget -R http://example.com/
[Radiant] Re: Could not find a JavaScript runtime deploying Radiant 1.0.0rc4 to Heroku
the coffeescript support in sheets needs a javascript runtime...so add therubyracer to your gemfile, bundle update and redeploy.
Re: [Radiant] Re: Newbie to Radiant, rake issue after installing
glad it worked. you might want to check http://git.io/radiant-simple-install for a script you can re-use as opposed to the one off posted here.
Re: [Radiant] Upgrading from 0.9.1 to 1.0.0-rc4
On Thursday, January 12, 2012 9:13:47 PM UTC-6, Jim Gay wrote: On Thu, Jan 12, 2012 at 9:42 PM, Jim Gay j...@saturnflyer.com wrote: On Thu, Jan 12, 2012 at 7:29 PM, Marshal Linfoot mlin...@gmail.com wrote: I'm having trouble with an upgrade to rc4 and wondering if anyone else has run into similar problems. Starting with a cloned copy of 0.9.1 instance, I've followed the guide from Jim Gay, https://gist.github.com/1540782, and can successfully start up an rc4 version of the site. But none of the former paperclipped assets are accessible and same thing for migrated sns styleshhets and javascripts. There are no error messages during the process, only a few warnings about deprecated items. I forgot to mention this: There's a new initializer for the clipped extension which should be generated for you. I've actually seen problems where it wasn't respecting the settings for my S3 bucket. I haven't had time to dig into it, but John Muhl has been working on that part of it. We thought we had it fixed, I have't had time to verify that, but perhaps it's not complete yet. i double checked using the clipped initializer and got both s3 and cloudfiles working by just plugging in my specific info. i should have time tomorrow to triple check it; no doubt i may have missed something with the filesystem option since i don't have any real sites using it. unfortunately i don't think the upgrade from paperclipped to clipped works without some intervention; though just editing the initializer should be all the intervention needed. if you've upgraded to the latest clipped and don't see config/initializers/clipped_config.rb you can manually run the radiant:extensions:clipped:initialize task to get it.
[Radiant] Re: simple install
On Wednesday, January 11, 2012 4:49:02 PM UTC-6, Ross Laird wrote: This works perfectly (for me), and is such a welcome addition. Thanks very much for putting it together. Radiant installation has suddenly gone from, Oh man, here we go again to two lines of pasted automagic code. Wonderful. thanks for testing! what operating system/version did you have success with?
Re: [Radiant] Re: Newbie to Radiant, rake issue after installing
hmm. not sure what the problem is. wget -O radiant-ubuntu-install.sh http://git.io/FkSTZw bash radiant-ubuntu-install.sh works for me.
[Radiant] Re: How to enable Travis CI for an extension
updates are available on the matching wiki page. https://github.com/radiant/radiant/wiki/How-to-enable-Travis-CI-for-an-extension
[Radiant] How to enable Travis CI for an extension
[Travis CI][travis] is a flexible and easy to use continuous integration server; see the [Getting Started page][travis-getting-started] for more details. The flexibility means that there are any number of ways to setup and test your extensions. Here is one way. First you need to add a `.travis.yml` file to the root of your repository. rvm: - 1.8.7 - 1.9.2 - 1.9.3 before_script: ./spec/ci/before_script script: ./spec/ci/script env: - RADIANT_VERSION=0.9.1 DB=mysql - RADIANT_VERSION=0.9.1 DB=postgres - RADIANT_VERSION=1.0.0 DB=mysql - RADIANT_VERSION=1.0.0 DB=postgres notifications: recipients: - y...@example.com The `rvm` array shows the Ruby versions you want to test against; since Radiant 1.0 supports the three latest Ruby releases your extension should too. Likewise the `env` array list Radiant version/database combinations to test against; the Radiant version can be any [tagged version of Radiant][tags]. Next up we need to create the `before_script` referenced above. The `before_script` is run before your tests and sets up a complete Radiant environment within which your tests will be run. cd ~ git clone git://github.com/radiant/radiant.git cd ~/radiant if [[ $RADIANT_VERSION != master ]] then git checkout -b $RADIANT_VERSION $RADIANT_VERSION fi cp -r ~/builds/*/YOUR_REPOSITORY_NAME vendor/extensions/YOUR_EXTENSION_NAME gem install bundler --pre bundle install case $DB in mysql ) mysql -e 'create database radiant_test;' cp spec/ci/database.mysql.yml config/database.yml;; postgres ) psql -c 'create database radiant_test;' -U postgres cp spec/ci/database.postgresql.yml config/database.yml;; esac bundle exec rake db:migrate bundle exec rake db:migrate:extensions Replace `YOUR_REPOSITORY_NAME` and `YOUR_EXTENSION_NAME` in the `before_script` with the actual name of your repo and extension; e.g. `radiant-sheets-extension` and `sheets` respectively. **Don't forget to make this script executable before committing it to your repository**. Finally we need to create the `script` file. This is the script that actually executes your tests. cd ~/radiant bundle exec rake spec:extensions EXT=YOUR_EXTENSION_NAME Again you need to replace `YOUR_EXTENSION_NAME` with the real thing and **make the script executable**. All that's left to do is login to [Travis][travis], enable the commit-hook for you repository and push. Head over to http://travis-ci.org/ and click the Sign in with GitHub link. Once you've authorized through GitHub visit your profile page on Travis, find the extension to enable and flick the switch to on. Now you're ready to commit and push the `.travis.yml`, `before_script` and `script` files and let Travis handle the rest. If you want to know more about all the options you have with Travis the [documentation][docs] is very good. You can see an example of this setup in action on the [Sheets][sheets-repo] extension or check out what it looks like to have your specs run by Travis by visiting the Travis page for [Sheets][sheets-ci]. Once setup Travis will run your tests after every commit unless you add `[ci skip]` to the commit message (which is good practice when pushing documentation or other commits that don't affect functionality). [travis]: http://travis-ci.org/ [travis-getting-started]: http://about.travis-ci.org/docs/user/getting-started/ [tags]: https://github.com/radiant/radiant/tags [docs]: http://about.travis-ci.org/docs/ [sheets-repo]: https://github.com/radiant/radiant-sheets-extension [sheets-ci]: http://travis-ci.org/radiant/radiant-sheets-extension
[Radiant] Re: Updating Radiant via Admin Interface
no
[Radiant] Re: When will 1.0.0 be ready?
there is one open issue and a couple of failing specs but master is really, really close to what will eventually become 1.0.0 (as far as i know there should be no breaking changes from master to 1.0) so you can upgrade to master now and then when 1.0.0 is official upgrading should be little more than changing `gem radiant, :git = git://github.com/radiant/radiant.git` to `gem radiant, ~ 1.0` and running `bundle update`. maybe jim can give you a more concrete answer but my feeling is that current master and 1.0 should be basically identical to users developers.
[Radiant] Re: Newbie to Radiant, rake issue after installing
it's nothing to worry about. a bunch of the gems radiant depends on have that line. if you really want to get rid of the warnings you can use rake 0.8.7 instead of 0.9.x.
Re: [Radiant] setting up Gravitar for a site
On Monday, November 21, 2011 5:40:31 PM UTC-6, Daniel O'Connell wrote: Yeah I guess you would :) Thanks Jim, I have comments running fine installed from gem. I'm having problems now understanding how to get the gravatars picked up for any but the author of page. here is the relavent bit from the comment snippet of a site i recently put together. r:comments:field ... img class=gravatar src=r:gravatar_url/?r=gd=mmr=gs=44 alt= ... /r:comments:field Saw your site saturnflyer and would like to do something similar. Does your fork of comments have features that would make enabling for all commenters easier? i'm pretty sure saturnflyer/radiant-comments is where the gem gets built from.
[Radiant] Re: Application Error / Error H10 when using Radiant on Heroku
i think the two most common problems deploying to heroku are issues with file creation at boot. have you booted production locally and committed all.js to your repo? how about disabling sass compilation? try adding `Sass::Plugin.options[:never_update] = true` to config/environments/production.rb if none of that helps could you post your log output to gist.github.com (or wherever); google groups mangles it pretty badly.
[Radiant] Re: Radiant 1.0.0rc3 rake production db:bootstrap
does using `bundle exec` to run bootstrap help?
[Radiant] Re: radiant gallery
radiant includes if/unless_[first|last] tags: r:unless_last,/r:unless_last you can find out about all the tags available and how to use them from the Available Tags link on the edit pages.
[Radiant] Re: NameError when creating radiant
use rubygems 1.3.7; `gem update --system 1.3.7` or add `require thread` to boot.rb
[Radiant] Re: Linking error
what version of ruby are you using? radiant only supports 1.8.7 at this time.
[Radiant] Re: Uninitialized Constant error Since Upgrading to RC3
how did you perform the upgrade to rc3?
[Radiant] Re: Need help with 1.0 rc2, member extension on Ubuntu 10+passenger+apache
On Monday, September 12, 2011 6:23:04 PM UTC-5, James Martens wrote: Is there any way to see better output from passenger? I know it produces nice looking 500 errors to help trace things, and normally that is how I solve these issues, but I can't seem to get a trace of where things are going wrong... you could try using `script/server` to see if you get more helpful debugging output.
Re: [Radiant] Radiant 1.0 Release Candidate 1
i'm not jim but i was getting some errors with 1.9.2. might have been some extension or might have been in core. i didn't have time just then to track it down but please do try it with 1.9.2 and file issues with anything you find breaking.
Re: [Radiant] Radiant 1.0.0rc1 no rakefile or gemfile
i do the following: * disable all 3rd party extensions * upgrade radiant * rake radiant:update * rake db:migrate * boot and make sure the basics are working * begin upgrading/re-enabling extensions one at a time
Re: [Radiant] radiant-1.0 any time soon?
https://github.com/radiant/radiant/compare/0.9.1...master https://github.com/radiant/radiant/blob/master/CHANGELOG
[Radiant] Re: Moving a Radiant Project and Changing the Database
On Wednesday, March 2, 2011 8:35:48 AM UTC-6, cody eilar wrote: Hello, This question may have already been asked, but I have been having some trouble finding a good answer. I currently have a radiant project running on my local machine using sqlite3 as the database. I now want to move my project to site5 and use a more robust database like mysql. Can somebody point me in the right direction to make sure that I do this correctly? Should moving the project consist of only copying the current project up to the server and then making sure all the correct gems are installed? Should changing the database consist of editing the database.yml, installing mysql and then running a rake db:migrate? Please help. taps: http://adam.heroku.com/past/2009/2/11/taps_for_easy_database_transfers/
[Radiant] Re: LoadError during install
On Sunday, February 20, 2011 1:10:21 PM UTC-6, BIO wrote: 1194 /usr/local/radiant/gardenruby -v ruby 1.9.2p136 (2010-12-25 revision 30365) [x86_64-darwin10.5.0] radiant currently only runs on 1.8.6/7
[Radiant] Re: send multiple emails with mailer?
you can do it with the mailer extension. in the mailer part try: subject: multiple recipients example from_field: email redirect_to: / recipients: - a...@example.com - b...@example.net
[Radiant] Re: if_url in layouts?
On Monday, February 21, 2011 8:07:33 PM UTC-6, craayzie wrote: Thanks for the reply but the url is actually just /contact output r:url/ on the page and you'll see radiant believes otherwise. that said `^/contact` should match as should `con` etc. etc. do you get different results with r:if_url matches='^/contact/$'...? On Feb 21, 4:29 pm, Rachel Soma ms.rach...@gmail.com wrote: Try r:if_url matches=^/contact? There's a / on the end of the url which is why your regex match isn't matching the url [image: Rachel]*Rachel Young* www.rachelsoma.com My profiles: [image: Facebook] http://www.facebook.com/rachelsoma [image: LinkedIn] http://au.linkedin.com/in/rachellyoung [image: Flickr]htpp://www.flickr.com/photos/rachelyoung [image: Twitter] http://www.twitter.com/rachelsoma Contact me: [image: Google Talk/] ms.rachel.soma On Tue, Feb 22, 2011 at 11:22 AM, craayzie fles...@gmail.com wrote: I'm trying to use if_url to conditionally include jquery on my / contact page but it doesn't seem to be working: r:if_url matches=^/contact script type=text/javascript src=http://ajax.googleapis.com/ ajax/libs/jquery/1.5.0/jquery.min.js/script /r:if_url Any ideas what I might be doing wrong?
[Radiant] Re: best code syntax highlighting solution
you should be able to create a setting like `kramdown.coderay_line_numbers = false` or possibly `... = :false` - to see all the available options check out lib/kramdown_filter.rb.
Re: [Radiant] Re: installing scoped_access plugin?
do you have the same problem if you install the extension into vendor/extensions?
[Radiant] Re: Easiest way to remove filters?
disable the extension in environment.rb
[Radiant] Re: How to embed an image with page attachment extension
On Jan 27, 10:09 am, ChrisWolf cw10...@gmail.com wrote: I tried this: r:attachment:image name=mypix.jpg/ but that doesn't work. it should but i haven't tried the official version in the in a while so maybe it got broken. i'll check it when i get some time. in the meantime could you expand on doesn't work? do you get an error? anything look suspicious in the logs?
Re: [Radiant] Crazy,crazy,You have never seen such perfect N*U*D*E ART
stop replying and making it show up in everyone's inbox. most of us have good enough spam filters that this garbage does not make it through...until someone replies... On Tue, Jan 18, 2011 at 8:25 AM, William Ross w...@spanner.org wrote: It was splendid, wasn't it? But it shouldn't have got through. Sorry about that. I've blocked the sender so there shouldn't be another. best, will On 18 Jan 2011, at 09:47, Arthur Gunn wrote: wow, what a truly incredible spam specimen.
[Radiant] Re: best code syntax highlighting solution
(whoops. accidentally sent off list)
looks at my previous posts in this thread. i explained it there. you
only need the kramdown_filter extension and the coderay gem (not the
coderay extension). usage looks like:
def meth options
--p options
end
{:lang=ruby}
where - is replaced with space as you would in regular markdown `pre`
blocks. i don't think it gets easier than that.
On Mon, Jan 17, 2011 at 4:52 PM, craayzie wrote:
My coderay + kramdown markup is really heavy/cumbersome. Is there a
better way?
Here's an example:
# heading
div markdown=block
## sub-heading
/div
r:code language=terminal
code-goes-here
/r:code
Ideally I could just write:
# heading
## sub-heading
$
code-goes-here
$
(using '$' to endicate start/end coderay blocks)
Any advice/guidance on how to best simplify the markup?
Re: [Radiant] Date picker from Radiant admin
On Sun, Jan 16, 2011 at 7:12 AM, Martin Silenus silee...@gmail.com wrote: Can I use date picker script(published_at field) from radiant admin in my own extension? How to do that? Thanks. https://github.com/jlong/dateinputjs
Re: [Radiant] Kramdown vs. markdown filter
i can't remember for sure but i think you can have both installed and kramdown will appear as a distinct filter alongside markdown in the menu. On Thu, Dec 16, 2010 at 4:24 PM, Wes Gamble we...@att.net wrote: Radiant 0.9.1 I see that the kramdown_filter extension just got updated to the kramdown 0.12 gem. If I want to use the kramdown_filter, should I remove the existing markdown_filter extension? Thanks, Wes
Re: [Radiant] Re: Re: best code syntax highlighting solution
On Mon, Dec 13, 2010 at 8:56 AM, Fima Leshinsky flesh...@gmail.com wrote: Looks like coderay is working well. I installed: coderay gem + radiant extension @ https://github.com/phallstrom/code_ray and now I can specify r:code blocks! not sure what the benefits are of kramdown over the existing Markdown radiant filter that comes with the Coffee blog template. If you guys can shed some light on why kramdown is a better option I'd appreciate it. it's not better. it's the same but with kramdown specific options enabled.
Re: [Radiant] best code syntax highlighting solution
On Wed, Dec 8, 2010 at 1:39 AM, craayzie flesh...@gmail.com wrote: I've begun to explore Radiant as a publishing/blogging platform. At the moment, I'm trying to nail down is how to best format command-line output or code as the majority of the content published will be of a technical nature. Can someone point me in the right direction of what I should use to get the desired affect :P I found http://alexgorbatchev.com/SyntaxHighlighter/ which is a JavaScript-based solution. Unfortunately it doesn't appear to support formatting/highlighting command-line output. What's the best Radiant filter / JS library / some-other-solution out there for both command-line output and code syntax highlighting? i like kramdown + coderay.
Re: [Radiant] Contact form debugging as Radiant new user learning opportunity...
On Wed, Dec 8, 2010 at 9:55 AM, rosslaird r...@rosslaird.com wrote: I am a new user to Radiant (coming from Drupal), and so far I've found Radiant to be a great application. I have also received excellent help from the community (here and on github), and this is also great. (Actually, a strong and helpful community is the most important thing of all.) I have almost finished rebuilding my website in Radiant, but I just need to get the contact form working properly. I have installed and setup the mailer extension and the contact form. The form seems to work, but does not redirect me to the thanks page. Also I do not receive the email (I'm working from localhost at the moment, on Ubuntu, so the fact that I do not get the email is not overly surprising. It could be caused by a number of things, though the mailq is empty). The log, however, says Sent mail to em...@address.com, so at least something is working. I am in the process now of debugging this, and I've started to look at various posts that discuss validation, changing environments.rb, and so on. Before I wade too deeply into this process, I thought I'd ask for a bit of help. I don't want to do anything to break the whole system. So: 1. I've seen in various posts that I should add some email info to environments.rb. There is currently no reference to such things in that file. In the following two tutorials (let's hope the url's don't get scrubbed here), different methods of adding email details are offered: http://railsforum.com/viewtopic.php?id=404 http://wiki.rubyonrails.org/rails/pages/HowToSendEmailsWithActionMailer Which of these should I use, or should I do something else? For now, I have simply changed one line in environment.rb, as suggested by the mailer documentation. I changed this: config.frameworks -= [ :action_mailer ] To this: config.frameworks -= [ ] So, I haven't added mailing details (smtp, user, and so on) anywhere. Perhaps that's the place to start. Suggestions most welcome. does https://github.com/radiant/radiant/wiki/mailer-extension help at all?
Re: [Radiant] best code syntax highlighting solution
http://johnmuhl.com/tmp/kramdown-coderay
the kramdown looks like (replace - with space):
def meth options
--p options
end
{:lang=ruby}
just a standard markdown code block followed by {:lang=lang}
http://coderay.rubychan.de/ list the supported languages.
On Wed, Dec 8, 2010 at 12:37 PM, Fima Leshinsky flesh...@gmail.com wrote:
Thanks John - will take a look. Do you have any public pages you can share
as examples?
Re: [Radiant] Re: Radiant as Rails3 engine RADIANT_ROOT
On Tue, Nov 30, 2010 at 2:48 PM, Marc marc.bosc...@gmail.com wrote: I was wondering if it would be possible to fix the rails version to say 2.3.8? radiant has a frozen version of rails in the gem (and repo in case you don't use the gem). so none of your rails gems matter to radiant (you could uninstall them all and radiant will still run).
Re: [Radiant] Re: Radiant as Rails3 engine RADIANT_ROOT
looks like it might be coming from the member extension (or not it was just the first hit in google). https://github.com/Aissac/radiant-member-extension On Tue, Nov 30, 2010 at 3:07 PM, Marc marc.bosc...@gmail.com wrote: That is good to know, and now means I have to work out why I am getting: undefined method `home_path' for #User:0x6fe0ce3b4dd0 when creating the admin user… On Dec 1, 8:01 am, john muhl johnm...@gmail.com wrote: On Tue, Nov 30, 2010 at 2:48 PM, Marc marc.bosc...@gmail.com wrote: I was wondering if it would be possible to fix the rails version to say 2.3.8? radiant has a frozen version of rails in the gem (and repo in case you don't use the gem). so none of your rails gems matter to radiant (you could uninstall them all and radiant will still run).
Re: [Radiant] Running 0.8.1 though having 0.9 gem installed
On Wed, Nov 24, 2010 at 4:49 AM, T.N.T. t...@banza.net wrote: Is is possible to run different Radiant versions in parallel or do I need to deinstall 0.9 completely to be able to run 0.8.1? i find the easiest way to handle it is to lock each project to the version of radiant needed. (from inside your project directory) rake radiant:freeze:gems # locks to the version of radiant you installed through rubygems rake radiant:freeze:edge TAG=0.8.2 # locks to version 0.8.2 - requires git to be in your PATH you could also download an archive of a previous version and unpack it to /your/project/vendor/radiant archives are available at https://github.com/radiant/radiant/downloads with any of these you will end up with a completely isolated version of radiant kept in each project in the vendor/radiant directory.
Re: [Radiant] how to upgrade from 0.8 to 0.9?
On Sat, Nov 20, 2010 at 12:06 PM, Eric ericgh...@gmail.com wrote: The docs/wiki are way out of date and there is no RADIANT_* in fortunately it's a wiki so you could clean it up if it has incorrect information; or point me to the page and as soon as time allows i'll look at it. environment.rb (or environments/*) at all. I've found that 0.8.1 (or some plugin) has disabled ctrl-right arrow, which I use to navigate through text quite often, so I'd like to check whether 0.9 will fix it or if it's a bigger problem. if you have some extension that is highjacking keystrokes upgrading your radiant isn't going to change that (unless 0.9 breaks that extension and you can no longer use it). do you know which extension is causing the problem? if not try disabling all of your extensions and add them back one at a time until you find the culprit. personally i've found managing radiant versions with rubygems a pain in the ass and freeze projects to the version of radiant they need. which i find makes upgrades easier. - trash vendor/radiant - disable all extensions - freeze radiant to new version - run the db:migrate and radiant:update rake tasks - grab the latest versions of extensions - enable them one at a time until everything is working
Re: [Radiant] sheets extension and packing/minification
can you set your server to gzip them? it ought to be nearly as effective as minification. On Fri, Nov 19, 2010 at 3:30 PM, Stan Rawrysz smoo...@gmail.com wrote: Has anyone had any success with packing/minifying/compressing the css and javascript when using the sheets extension or sns extension? We're currently using the sns extension, but I'm looking to update the site to use sheets and am just doing research. Would like to know if anyone has already done any work on the compression front. Thanks, Stan
Re: [Radiant] Forms extension
On Fri, Nov 12, 2010 at 9:34 AM, Marshal Linfoot mlinf...@gmail.com wrote: Has anyone used a forms/mailer extension for Radiant that allows a file to be attached and sent with the form? I have a form working -- users fills in text, selects choices from dropdown, checks radio buttons -- everything works, contents emailed successfully. I'm trying to add the capability for people to select a file (photo) from their computer to be attached to the email but I can't get it to work. If you've got it working, could you please share your solution? try the aissac fork. i've setup mailer with attachments before and i think that was the fork i used (if not poke around the network and you'll find it).
Re: [Radiant] Pull articles from multiple sources
On Mon, Nov 8, 2010 at 6:49 PM, Jordon Bedwell jor...@envygeeks.com wrote: Is there a way to pull archives from multiple urls, something like: r:aggregate urls='/a; /b; /c'.../r:aggregate check the in page tag reference for more aggregate tags (if you're on 0.8 install the radiant/aggregation extension)
Re: [Radiant] Re: trouble running rake for custom extension
On Sun, Nov 7, 2010 at 10:06 AM, Tobi tobold.hornblae...@kaffeeschluerfer.com wrote: Besides the complaint about missing jeweler it's still the same, but thanks for the reply. Anyone else got an idea? Where spec/rake/spectask is supposed to go. And what it should contain? I didn't find it anywhere at my system. seems like something up with rspec. do you have it installed? do you have an appropriate version installed (e.g. something from the 1.3 series)? is that version being loaded or are you getting a newer (or older) version in your environment?
Re: [Radiant] Re: rack/cache issue
On Wed, Nov 3, 2010 at 7:15 PM, Rek2GNULinux rek2gnuli...@gmail.com wrote: I use gentoo so I emerge radiant then I run: radiant --database=mysql I created the mysql databases configure the /config/databases.yml and then I try rake db:bootstrap and I get that error... i don't know anything about gentoo or emerge. do they do anything non-standard to rubygems before releasing them in emerge? it sounds like something is butchering the radiant gem you're getting a hold of (e.g. removing vendor/...). you might try installing manually: wget http://rubygems.org/downloads/radiant-0.9.1.gem gem install radiant-0.9.1.gem
Re: [Radiant] Fresh install (error): comparison of String with 60 failed
On Wed, Nov 3, 2010 at 2:51 PM, Jordon Bedwell jor...@envygeeks.com wrote: Rack 1.2 Rails 3 Ruby 1.9.2 Perhaps you guys and gals can help me figure out how to fix this error: try: Rack 1.1.0 Rails 2.3.8 (Radiant has it vendored so your Rails 3 above is not being loaded; i.e. you don't need to install Rails at all) Ruby 1.8.7 Radiant does not run on any of the software you mentioned.
Re: [Radiant] rack/cache issue
On Wed, Nov 3, 2010 at 7:02 PM, Rek2GNULinux rek2gnuli...@gmail.com wrote: Hello decided to try radiant but I keep getting this error... any idea? rake production db:bootstrap (in /var/www/dev.binaryfreedom.info) rake aborted! no such file to load -- rack/cache probably a bum install. could you explain how you installed radiant and setup your site. and gist or pastie the output of `rake production db:bootstrap --trace`
Re: [Radiant] Quick question about updating extensions with git
On Tue, Oct 19, 2010 at 2:56 PM, Nate Turnage pixeln...@gmail.com wrote: Hey all, It's been a while since I've worked with Radiant and Git, and I now need to update a couple of apps to, at least, 0.8.2. So I was wondering if somebody could help me out by listing the command used to update an extension that was added as a git submodule? Also, how can I specify which branch/tag to use? off the top of my head (but hopefully close) cd vendor/extension/ext git fetch git checkout -b new_branch repo_branch_name cd ../.. rake radiant:extensions:ext:update rake radiant:extensions:ext:migrate git add vendor/extension/ext [other files] git commit -m 'update ext'
Re: [Radiant] Re: How to use the toggle effect on pages?
On Sat, Sep 11, 2010 at 8:16 AM, Allan MacGregor d...@allanmacgregor.com
wrote:
Is there a way to specify the onClick event for radius tags? for
example for a set checkboxes or a dropdown?
radius is just a template language for outputting other formats; (i
guess) most often html. so simply have radius output the html that
makes it easiest for you to script. for example:
r:mailer:form name='x'
divr:checkbox value='a' name='a'/ label for=aA/label/div
divr:checkbox value='b' name='b'/ label for=bB/label/div
divr:checkbox value='c' name='c'/ label for=cC/label/div
/r:mailer:form
outputs:
form action=/contact/check/ method=post
enctype=multipart/form-data id=mailer name=mailer[x]
divinput type=checkbox value=a id=a name=mailer[a]
label for=aA/label/div
divinput type=checkbox value=b id=b name=mailer[b]
label for=bB/label/div
divinput type=checkbox value=c id=c name=mailer[c]
label for=cC/label/div
/form
which you can script however you normally script html.
in plain old javascript style:
var target = function (e) {
e = e || window.event;
return e.target || e.srcElement;
};
document.forms['mailer'].onclick = function (e) {
var t = target(e);
if (t.type == 'checkbox') alert(t.value);
};
or in jquery style:
$('input[type=checkbox]').click(function () { alert(this.value) });
On Sep 10, 5:55 pm, Wes Gamble we...@att.net wrote:
You may want to check out jQuery, which allows you to do effects like
this.
See:http://api.jquery.com/category/effects/for the jQuery API
documentation on the show() and hide() methods.
Download:http://docs.jquery.com/Downloading_jQuery
Tutorials:http://docs.jquery.com/Tutorials
Given:
div class=x
This content will be shown/hidden.
/div
You would use something like
$('.x').show() to show it and $('x').hide() to hide it.
Good luck,
Wes
On 9/10/10 3:32 PM, Horst Rischbode wrote:
Hi,
I want to show (and be able to hide it again) a div on user's demand.
I want to appear it similar to the 'less' 'more' attributes
behaviour of the edit page view.
I'm not familar with haml, so I don't understand, how to get this
working on my gallery pages. Please be patient...
Can anybody point out, which JS libraries to include and how to build
up a simple example with html?
Thanks for any advice!
Horst
Re: [Radiant] Search on Heroku
http://tenderlovemaking.com/2009/10/17/full-text-search-on-heroku/ might help. i've been meaning to use that technique to whip up an extension but haven't got around to it yet. On Tue, Aug 24, 2010 at 3:05 PM, Jeff Casimir j...@casimircreative.com wrote: Hi all, Is anyone using 0.9 with Heroku and making use of a search extension? Unless I'm missing something, Heroku pushes you toward Websolr. The Solr extensions for Radiant if found looked out of date. Anyone solved this problem, or should I start digging/updating the older extension(s)? - Jeff --- Jeff Casimir Jumpstart Lab by Casimir Creative, LLC http://jumpstartlab.com @jumpstartlab on twitter
Re: [Radiant] Addition to wiki (need a little help)
I've made it public now: http://support.github.com/discussions/repos/3873-radiant-wiki Rick's working on it. Please do not use it yet. I'll post here when it's complete. --John On Mon, Aug 16, 2010 at 12:37 AM, john muhl johnm...@gmail.com wrote: is there a public issue for that? i don't to start working on it and end up filing duplicate issues. On Sun, Aug 15, 2010 at 9:47 PM, John W. Long m...@johnwlong.com wrote: Some of the pages haven't transfered over yet. I've notified GitHub and they are working on it. --John On Sun, Aug 15, 2010 at 7:53 PM, john muhl johnm...@gmail.com wrote: On Sat, Aug 14, 2010 at 2:46 PM, Wes Gamble we...@att.net wrote: Can someone change the name of this page to Merging existing extensions and link to it under the Creating Your Own Extensions section? done and done. http://github.com/radiant/radiant/wiki http://github.com/radiant/radiant/wiki/Merging-existing-extensions anyone looking to do some wiki-tending might want to start by fixing the wiki links that the new format broke; e.g. [[url|page title]] is now [[page title|url]]. a global search and replace ought to do the trick. i'll have some time later this week to do some work to get things ready for the forced upgrade in september but help is always appreciated.
Re: [Radiant] Addition to wiki (need a little help)
On Sat, Aug 14, 2010 at 2:46 PM, Wes Gamble we...@att.net wrote: All, I've added a page to the wiki about how to merge two or more extensions here: http://wiki.github.com/radiant/radiant/merging-existing-migrations But I mis-titled it Merging existing migrations when it should be Merging existing extensions I can't figure out how to modify the title/page name. Can someone change the name of this page to Merging existing extensions and link to it under the Creating Your Own Extensions section? i don't think the title can be changed after the page is created. it looks like the new wiki system has this ability though. maybe we should upgrade the radiant wiki to the new system?
Re: [Radiant] forms extensions installed, but no Forms tab appears
On Wed, Aug 11, 2010 at 4:09 PM, Lindsay Morris lmorris...@gmail.com wrote: So I tried another installer: git clone git://github.com/squaretalent/radiant-forms-extension vendor/extensions/forms That seemed happy, and I now have a vendor/extensions/forms directory. Yay! Then: rake radiant:extensions:forms:migrate blew up like this: /home/lindsay/rails_apps/radiant/config/environment.rb:13 config.gem 'radiant-forms-extension' it looks like you're mixing the two types of extension installation; vendor/extensions/xyz and installed as a gem. you only need to do one or the other and since it looks like gems were not working remove the `config.gem 'radiant-forms-extension' line. then re-run the installation task(s).
Re: [Radiant] Search on http://ext.radiantcms.org/
Is sphinx easy to install? We would probably need to get Andrew vonderLuft our sys admin to set it up. But yes, I'm potentially interested in a patch. http://github.com/radiant/radiant-extension-registry --John On Wed, Aug 11, 2010 at 10:17 AM, Christian Aust christian.a...@software-consultant.net wrote: Works, but feels somewhat clumsy. What about using thinking_sphinx for searching the extensions? I'd volunteer to create a patch. Am Mittwoch, den 11.08.2010 um 15:42 schrieb john muhl: http://www.google.com/search?q=0.9+site:ext.radiantcms.org On Wed, Aug 11, 2010 at 7:44 AM, Christian Aust christian.a...@software-consultant.net wrote: Hi all, is there a way to serach for all extensions marked as 0.9-compatible on http://ext.radiantcms.org/? Regards, Christian
[Radiant] Archive Month Index on Radiant 0.9.1
Just ran across interesting problem where using an Archive Month Index page created yesterday with a bunch of items when you viewed the index page for the month it showed itself at the top of the page with a recursion error and then the matching items for the month. The solution was to change the publish date of the index page to be some date ages in the past but it's something to be aware of, John.
Re: [Radiant] Correct way to eliminate page caching in Radiant?
On Wed, Aug 4, 2010 at 11:35 AM, Wes Gamble we...@att.net wrote: I've Googled and seen several approached to turning off page caching in Radiant - what is the most correct way to do this for a production environment? have you tried modifying the response headers? gem install rack-contrib # environment.rb require 'rack/contrib' ... config.middleware.use ::Radiant::Cache config.middleware.use Rack::ResponseHeaders do |headers| headers['Cache-Control'] = 'no-cache' end ...
Re: [Radiant] Re: Problems with installing Radiant extensions
On Tue, Jul 13, 2010 at 2:49 AM, Nikus greeni...@gmail.com wrote: What deatils do you need to know? operating system, radiant version, ruby version, rubygems version, anything else that could help replicate your system. also i just pushed a change to ray that (should have) fixed the error you were having before. could you update to the latest version and let me know if you still get an error. in your situation the easiest way to update might be to simply remove the `vendor/extensions/ray` directory and download or clone the latest version.
Re: [Radiant] What is Radiant 1.0 and which Asset extension to use, was: page_attachments interface enhancements
On Tue, Jun 29, 2010 at 8:50 PM, Jeff Casimir j...@casimircreative.com wrote: I'd like to see radiant follow some of the footsteps from merb and have two gems: radiant-core and radiant-more. So one other idea I had on about this is to add the ability to the extension registry for users to create lists of extensions. If you couple this with the radiant command you could then do something like this on install: radiant -d sqlite3 --extensions jlong:fancypants path/to/radiant/project Which would install all of the gems for extensions from my fancypants list in addition to creating and configuring my Radiant project. Then add a radiant user in the extension registry and radiant-more becomes: radiant -d sqlite3 -e radiant:more path/to/radiant/project -- John Long http://wiseheartdesign.com http://recursivecreative.com
Re: [Radiant] What is Radiant 1.0 and which Asset extension to use, was: page_attachments interface enhancements
On Tue, Jun 29, 2010 at 7:51 PM, Jim Gay j...@saturnflyer.com wrote: On Tue, Jun 29, 2010 at 2:24 PM, Haselwanter Edmund edm...@haselwanter.com wrote: On 29.06.2010, at 19:47, Jim Gay wrote: I'm glad you brought this up for discussion. It just felt right after following the github discussion :-) On Tue, Jun 29, 2010 at 11:59 AM, Edmund Haselwanter edm...@haselwanter.com wrote: A question for clarification: [ .. snippet .. ] wouldn't it be wise to concentrate on just one (nifty) asset extension? I see an asset extension as a vital part of a CMS (= see, it says content ;-) Yes. Check out the prototype http://github.com/radiant/radiant-prototype And there are tickets like http://github.com/radiant/radiant/issues#issue/28 (sns) and quote jlong jlong February 18, 2010 | link There's a little more work to do on this in the prototype, mainly the upload interface. I believe Chris Parish has had ambitions for simplifying his styles 'n scripts extension to serve this purpose. If it is going to make it into 0.9 it should be implemented as an extension that ships with the core. /quote jlong That's exactly how I see it too :-) SNS needs some more thought (which I happen to be doing http://www.saturnflyer.com/blog/jim/2010/06/29/ruby-metaprogramming-is-awesome/ ) but I see that as a necessity for managing a site (along with image/file management of course). having your css and js in the admin interface is a necessity? i tried to love sns but never could find any benefit to not having the files on disk. perhaps the extension has matured since i last looked (an admittedly long time ago). if anybody has a compelling reason why it's better to have that stuff in radiant than on disk i'd be happy to give it another try. the only reason for having your css/js in radiant i could ever dream up was being able to stick radius tags in your css or js but that didn't work with sns...until today. in the past when i ran into a place where i needed that functionality i would just stick that little bit of css/js inline in a layout or snippet; i think i needed to do that once or twice in three years and more sites than i can remember. The greatness behind paperclipped is paperclip (not to take away from all the work that Keith and many others put in to make a really useful extension). I like page_attachments too and recently did a lot of work to change it on my fork with John Muhl's help, but for a recent project I was again looking for an asset manager and even though I did all that work to update page_attachments (and it still needs more) I chose paperclipped because of paperclip. Yes. You are right. And there are some extensions which add to paperclipped. This is some kind of vote of the community, isn't it ;-) Yes, but partly because paperclipped had so much more done. Keith did a great job creating it and it's feature set blows page_attachments out of the water, but as I've heard John Muhl point out, some users find the interface (like the assets bucket) confusing and the simplicity of a list on a page (a la page_attachments) is very easy to understand. it's true. i've tried paperclipped on three occasions and all three times it ended up being pulled due to the commoners not really getting the interface. with p_a they get it almost immediately; it's like attachments in email and everybody seems to understand that. i have an extension tied up in a client site that uses carrierwave http://github.com/jnicklas/carrierwave and provides a similar experience to page_attachments that i could try to get permission to extract and open source if there is any interest in yet another file manager (i can't imagine there would be but who knows) and honestly it doesn't do anything more interesting than p_a but at least it's not dependent on attachment_fu :) and with this comes another question: Ok, I know that Radiant is different. And I love it. I recently did a presentation in my web 2.0 community meeting about radiant. And one statement burned so hard: No end user will use this! Bullshit. It's just not true. I've had plenty of non-technical, non-tech-savvy users enjoying Radiant. Hm. Its not bullshit. It's how some people see it. I had to fight 20 people to suggest that it would be much more easier to educate people to use textile than to have a WYSIWYG Editor. I'm a textile fan. It just would be create to have a solution for this feature request. but ok. there are some extensions out there. must not be in the core neither a core extension Seriously!? No end user will use this! I don't know who, other than end users, actually use any Radiant project I've worked on. ditto what Jim said. it requires more work on the developer's side but once you work with enough clients you get a feel for how non-technical users expect things to work (e.g. no magic page parts, no `r:blahblah` etc) and radiant's minimal core lets you bend it to meet those expectations without
Re: [Radiant] What is Radiant 1.0 and which Asset extension to use, was: page_attachments interface enhancements
On Tue, Jun 29, 2010 at 7:50 PM, Jeff Casimir j...@casimircreative.com wrote: I'd like to see radiant follow some of the footsteps from merb and have two gems: radiant-core and radiant-more. The 'radiant' gem would that sounds like a fine idea; and has been discussed in the past but it wasn't particularly feasible until recently And if someone really wants a stripped down version they can just install radiant-core, barebones but fully functional. radiant-core would be for the hardcore :) seriously though i think you'd have radiant-blog, radiant-portfolio, radiant-catalog etc. springing up then which would be a killer feature in my opinion.
Re: [Radiant] Problems after upgrade from 0.8.1 to 0.9.0
2010/6/25 Artem Zhirkow zhir...@yahoo.com Hi, I just upgraded my website with rake to 0.9.0 version and got application error on the main page of website. Below you can see message from logs: looks like http://github.com/radiant/radiant/issues/closed#issue/128 so you may want to try running from the master for now.
Re: [Radiant] Radiant 0.9 performance
On Thu, Jun 24, 2010 at 12:19 PM, Marshal Linfoot mlinf...@gmail.com wrote: John, I decided to give nginx+passenger a try. Installed the passenger gem and then passenger-install-nginx-module to compile nginx with the passenger module. Little bit of configuring and started it up. i'm pretty much out of ideas about what the problem may be. i've never seen numbers like that ever; not even running in development with webrick. perhaps there is a problem with the slice itself. you could always try taking a snapshot of your setup and boot a new slice using that snapshot and compare performance on the new slice. and 10 minutes later the load avg is back up to 7 and the site is unresponsive. Taking nginx down and restarting litespeed. What the heck is going on??? Desperate for a fix!!! this sounds like you're using the passenger default which is to run up to six application servers. here is an except from an nginx configuration file that i use on a 32bit 256mb slicehost server that is dedicated to running a single site http://gist.github.com/454173. that server has been running for over a month now with no runaway resource usage. The mysql database was loaded using taps to copy from my desktop development environment to the slicehost server. Could the database be corrupted? How can I check? try running in production using your sqlite database.
Re: [Radiant] heroku and long wait after changes
On Sat, Jun 19, 2010 at 2:00 PM, Steven Southard ste...@stevensouthard.com wrote: So what is up with the 5 minute wait to see results after making a change on Heroku? I'm currently using Radiant Edge on the Bamboo Ruby enterprise edition 1.8.7 stack but I've also set up 8.1 using their standard setup. This long wait to see the results of changes kind of ruins Radiant's great user experience. Changes can be seen right away on the back-end which is helpful so is there a way it could be fixed so they could be seen right away on the front-end. see http://docs.heroku.com/http-caching. in other words it's just the way it is. heroku restart or git push heroku master are the only ways i know of to purge heroku's varnish cache.
Re: [Radiant] Building a gem for 0.9.0.rc3 FAIL
you might have better luck with rake radiant:gem On Wed, May 19, 2010 at 3:56 PM, D.Kreft d...@kreft.net wrote: Thanks. Though now I have a different problem: % gem build radiant.gemspec ERROR: While executing gem ... (ArgumentError) /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/version.rb:56:in `initialize': Malformed version number string 0.9.0.rc3 Do I just need to get into the gemspec and hack the version number? -dan On Wed, May 19, 2010 at 1:39 PM, john muhl johnm...@gmail.com wrote: git submodule init git submodule update On Wed, May 19, 2010 at 2:41 PM, D.Kreft d...@kreft.net wrote: I'm trying to build a gem for radiant-0.9.0.rc3, but it's not going too well. Is there some secret mojo I'm missing? % pwd /workplace/octane/src/RubyGem-radiant/radiant-0.9.0.rc3 % gem build radiant.gemspec ERROR: While executing gem ... (Gem::InvalidSpecificationException) [vendor/extensions/archive/app, vendor/extensions/archive/app/models, vendor/extensions/archive/app/models/archive_day_index_page.rb, vendor/extensions/archive/app/models/archive_finder.rb, vendor/extensions/archive/app/models/archive_month_index_page.rb, vendor/extensions/archive/app/models/archive_page.rb, vendor/extensions/archive/app/models/archive_year_index_page.rb, vendor/extensions/archive/archive_extension.rb, vendor/extensions/archive/lib, vendor/extensions/archive/lib/archive_index_tags_and_methods.rb, vendor/extensions/archive/lib/tasks, vendor/extensions/archive/lib/tasks/archive_extension_tasks.rake, vendor/extensions/archive/Rakefile, vendor/extensions/archive/README, vendor/extensions/archive/spec, vendor/extensions/archive/spec/datasets, vendor/extensions/archive/spec/datasets/archive_dataset.rb, vendor/extensions/archive/spec/models, vendor/extensions/archive/spec/models/archive_day_index_page_spec.rb, vendor/extensions/archive/spec/models/archive_month_index_page_spec.rb, vendor/extensions/archive/spec/models/archive_page_spec.rb, vendor/extensions/archive/spec/models/archive_year_index_page_spec.rb, vendor/extensions/archive/spec/spec.opts, vendor/extensions/archive/spec/spec_helper.rb, vendor/extensions/archive/test, vendor/extensions/archive/test/fixtures, vendor/extensions/archive/test/fixtures/pages.yml, vendor/extensions/archive/test/functional, vendor/extensions/archive/test/functional/archive_extension_test.rb, vendor/extensions/archive/test/helpers, vendor/extensions/archive/test/helpers/archive_index_test_helper.rb, vendor/extensions/archive/test/test_helper.rb, vendor/extensions/archive/test/unit, vendor/extensions/archive/test/unit/archive_day_index_page_test.rb, vendor/extensions/archive/test/unit/archive_month_index_page_test.rb, vendor/extensions/archive/test/unit/archive_page_test.rb, vendor/extensions/archive/test/unit/archive_year_index_page_test.rb, vendor/extensions/dutch_language_pack/config, vendor/extensions/dutch_language_pack/config/locales, vendor/extensions/dutch_language_pack/config/locales/nl.yml, vendor/extensions/dutch_language_pack/config/locales/nl_available_tags.yml, vendor/extensions/dutch_language_pack/dutch_language_pack_extension.rb, vendor/extensions/dutch_language_pack/lib, vendor/extensions/dutch_language_pack/lib/tasks, vendor/extensions/dutch_language_pack/lib/tasks/i18n_nl_extension_tasks.rake, vendor/extensions/dutch_language_pack/Rakefile, vendor/extensions/dutch_language_pack/README, vendor/extensions/french_language_pack/config, vendor/extensions/french_language_pack/config/locales, vendor/extensions/french_language_pack/config/locales/fr.yml, vendor/extensions/french_language_pack/config/locales/fr_available_tags.yml, vendor/extensions/french_language_pack/french_language_pack_extension.rb, vendor/extensions/french_language_pack/lib, vendor/extensions/french_language_pack/lib/tasks, vendor/extensions/french_language_pack/lib/tasks/i18n_fr_extension_tasks.rake, vendor/extensions/french_language_pack/Rakefile, vendor/extensions/french_language_pack/README, vendor/extensions/german_language_pack/config, vendor/extensions/german_language_pack/config/locales, vendor/extensions/german_language_pack/config/locales/de.yml, vendor/extensions/german_language_pack/config/locales/de_available_tags.yml, vendor/extensions/german_language_pack/german_language_pack_extension.rb, vendor/extensions/german_language_pack/lib, vendor/extensions/german_language_pack/lib/tasks, vendor/extensions/german_language_pack/lib/tasks/i18n_de_extension_tasks.rake, vendor/extensions/german_language_pack/Rakefile, vendor/extensions/german_language_pack/README, vendor/extensions/italian_language_pack/config, vendor/extensions/italian_language_pack/config/locales, vendor/extensions/italian_language_pack/config/locales/it.yml, vendor/extensions/italian_language_pack/config/locales
Re: [Radiant] Tag context
children:each does this by modifying the tag.locals.page variable: http://github.com/radiant/radiant/blob/master/app/models/standard_tags.rb#L119-120 (it also adds tag.locals.child) -- John Long http://wiseheartdesign.com http://recursivecreative.com On Tue, May 18, 2010 at 4:43 AM, alex a...@ttbc.de wrote: Hi all, I am wondering how to switch page context for self-made radiant tags. Example: r:children:each r:my_tag/ /r:children:each Accessing self within the tag addresses the page itself instead of its children. What do I miss? Thanks, Alex
Re: [Radiant] javascript r: url/
var foo = r:url/; quote the value var foo = /url/; syntax error On Mon, May 17, 2010 at 6:27 PM, Osledy Bazó osledyb...@gmail.com wrote: Hello i need to get the url of a page to usit on a js script.. i'm doing this: http://pastie.org/964651 nothing seems to work can anyone helpme to do this?
