Re: [Radiant] Re: Radiant and Rails 3
I'll second this advice. I may not know enough about your needs, but with a CMS, it doesn't seem importance what version of Rails or Ruby a CMS runs on, since a full-blown app is not what Radiant CMS is designed for. That's exactly right. But I've been told that a Rails app can be written and included into a Radiant site as a plugin, although I haven't done that (yet). That can be done successfully, I've worked with 3 or 4 apps like that. It can also lead to code really hard to maintain. Radiant is a really powerful CMS but in my experience as soon as you start tweaking it adding features (as extensions) based around users (signed up users, not the Radiant members) everything become exponentially harder. 1) you are stuck with Rails 2 2) problems when you want to have static pages mixed up with dynamic content, this requires radius_tags to pull in dymanic content which are really powerful but not really like maintaining Rails views. Or you can have your dynamic app pulling in CMS content doing something like a Page.find. 3) you must source control the content where those radius_tags are used, which means it will be harder to do diffs on templates Basically you have to find out how much of the CMS you use, and how much of 'new features' you will have to add. If the latter is bigger, my suggestion is to go with a custom built probably with help from Refinery CMS to get the CMS jump started. HTH, Enrico
Re: [Radiant] Accessing Rails generators from a Radiant app
Hi,
I was looking for another devise thread on the ML and I found yours.
Add this to script/generate to load an unpacked gem generators:
gems_path = File.expand_path(File.join(RAILS_ROOT, %w(vendor gems)))
sources Rails::Generator::PathSource.new(:gems (vendor/gems),
#{gems_path}/*/**/{,rails_}generators)
I had exactly the same problem.
HTH
Enrico
On Wed, Dec 8, 2010 at 11:47 PM, Mario Aquino mario.e.aqu...@gmail.com wrote:
I am just getting started on a new radiant site. I generated it via the
radiant shell command (v0.9.1 gem). I would like to use devise as the
authentication mechanism for the site. I came across a wiki page explaining
how to do it:
https://github.com/radiant/radiant/wiki/Using-Devise-as-an-authentication-system-for-Radiant-end-users
The wiki page calls for following the devise instructions for gem
installation and then generator usage for creating a custom user model
(along with other instructions for setup). My problem is that I can't seem
to access the devise_install generator (or any other generator that isn't
included with radiant). When I run script/generate, I see:
Installed Generators
Builtin: extension, extension_controller, extension_mailer,
extension_migration, extension_model, instance, language_extension
None of either the Rails generators or generators provided by gems I have
installed in my environment are visible to me. Is there some step I need to
do to be able to see non-radiant generators?
Thanks in advance,
--Mario
--
Enrico Teotti
IT consultant, accessible web sites and web applications
currently working @ http://www.redant.com.au
Sydney, NSW, Australia
enrico.teo...@gmail.com
mobile (AU) +00610416748450
http://teotti.com
Re: [Radiant] Re: undefined method `match' - when testing extension features with cucumber and webrat
Hi Stan, today when I was running my cuke features on a Rails app I had exactly the same problem you had. undefined method `match' for #Array:0x10a770a78 (NoMethodError) This was a fresh install, the same features were running fine on my office workstation. These are the gems of my Rails (2.3.4) app: http://pastie.org/1396577 And after two hours of hammering my head, and right before deciding to stop working in IT and open a bar on a lonely beach on a remote island... I found out that the error was caused by: rack (1.2.1) rolling it back to rack 1.0 (and even 1.0.1) solved the problem for me. It's not a Radiant related problem, but I really hope by posting my solution I'll save some time to the future generation (I hope nobody) who might incur in this cryptic problem, Regards, Enrico -- Enrico Teotti IT consultant, accessible web sites and web applications currently working @ http://www.redant.com.au Sydney, NSW, Australia enrico.teo...@gmail.com mobile (AU) +00610416748450 http://teotti.com
Re: [Radiant] Re: Using Devise as an authentication solution for end users with Radiant - updated
Hi, thanks a lot for your post. Did you have to run: ruby script/generate devise_views or did you manage to add the views to the load path? Without those views inside the extension I am getting a Template is missing when I submit the forgot password for example. Ta, enrico
