Re: [Radiant] Mongrel_Cluster Issue on Ubuntu 6.10 using Radiant

2007-07-05 Thread Matt Parrish
Did you type $ sudo rake db:migrate when you should have run $ sudo rake production db:migrate Matt Parrish http://www.pearware.org On Jul 5, 2007, at 11:15 PM, Ben Minton wrote: > I have installed the latest version of Radiant using > > $ sudo gem install --include-dependencie

Re: [Radiant] RadiantOnRails NameError for no_login_required

2007-06-21 Thread Matt Parrish
Hi Lindsay, What we determined from Luke's error is that you probably have the file RAILS_ROOT/app/controllers/application.rb, which shouldn't be there. Delete that file and see if it works. Thanks, Matt Parrish http://www.pearware.org On Jun 21, 2007, at 5:05 AM, Lindsay Palli

Re: [Radiant] RadiantOnRails NameError for no_login_required

2007-06-11 Thread Matt Parrish
rge.org/var/svn/radiantonrails/trunk vendor/ extensions/radiant_on_rails Then you need to configure config/database.yml and follow the instructions in vendor/extensions/radiant_on_rails/README. Try this out and let me know if your still having issues. I just did it and it is working for me. Ma

Re: [Radiant] RadiantOnRails extension

2007-06-02 Thread Matt Parrish
ht > work: > > 1) Load the "#{RAILS_ROOT}/config/routes.rb" file as text. > 2) Find and strip out the lines that contain the beginning and end of > the block. > 3) eval the file in the local context of the define_routes block. > > Not elegant, I know, but effect

Re: [Radiant] RadiantOnRails extension

2007-06-02 Thread Matt Parrish
/routes.rb Matt Parrish http://www.pearware.org On Jun 2, 2007, at 11:00 AM, Sean Cribbs wrote: > Here's another option, one you may have considered already. > > Extension routes are loaded before the Radiant routes and all of > this is > taken care of by Radiant::Initial

Re: [Radiant] RadiantOnRails extension

2007-06-02 Thread Matt Parrish
ension is like the first solution, except that I have the user create a class RailsRoutes with a define_routes method that my extension calls. I think the second solution here would be preferred. Matt Parrish http://www.pearware.org On Jun 2, 2007, at 9:52 AM, Sean Cribbs wrote: > The stoc

Re: [Radiant] RadiantOnRails extension

2007-06-02 Thread Matt Parrish
zation in plugins/radiant/init.rb. I haven't looked at it >> yet, but I'm guessing there will be a few challenges to getting this >> to work properly. One challenge I immediately see is getting >> Radiant's routes to coordinate with the Rails ones in config/ >&g

Re: [Radiant] Assets Manager extension?

2007-06-02 Thread Matt Parrish
about calling it "Freeze mode", or "Frozen mode"? Maybe it sounds a bit funny. But I think it's very clear. Just my $0.02. :) Matt Parrish http://www.pearware.org On Jun 1, 2007, at 6:29 PM, John W. Long wrote: > Sean Cribbs wrote: >> 1) To set constant

Re: [Radiant] RadiantOnRails extension

2007-06-02 Thread Matt Parrish
m guessing there will be a few challenges to getting this to work properly. One challenge I immediately see is getting Radiant's routes to coordinate with the Rails ones in config/routes.rb. Matt Parrish http://www.pearware.org On Jun 1, 2007, at 9:17 PM, Meekish wrote: > Loren Johnso

Re: [Radiant] RadiantOnRails extension

2007-06-01 Thread Matt Parrish
t be a few minor changes to the Radiant code to get things working cleanly in instance, gem and plugin modes. Matt Parrish http://www.pearware.org On Jun 1, 2007, at 7:24 AM, Loren Johnson wrote: > > You're absolutely right, sorry I hadn't looked closely enough. > > Y

[Radiant] RadiantOnRails extension

2007-05-31 Thread Matt Parrish
/trunk Or, to install the extension, follow the instructions from the Radiant website (http://dev.radiantcms.org/radiant/wiki/Extensions) using the name 'radiant_on_rails' for the extension_name. Matt Parrish http://www.pearware.org On May 30, 2007, at 4:49 PM, John W. Long wrote

Re: [Radiant] Radiant integration with another Rails app?

2007-05-30 Thread Matt Parrish
for use with 0.6.1 and work with Loren on getting it to a Plugin-ized version within Radiant SVN repository. Loren, congrats on the promotion to Radiant Core team member! :) Matt Parrish http://www.pearware.org On May 30, 2007, at 4:49 PM, John W. Long wrote: > Loren Johnson wrote: &g

Re: [Radiant] Radiant integration with another Rails app?

2007-05-30 Thread Matt Parrish
n existing Rails app. Matt Parrish http://www.pearware.org On May 30, 2007, at 2:01 PM, Mario T. Lanza wrote: >> I'm also very interested in allowing Rails pages to leverage Radiant >> layouts, and that is the next thing I plan to work on. > > I'm very happy to se

Re: [Radiant] Radiant integration with another Rails app?

2007-05-30 Thread Matt Parrish
wrote: > Matt Parrish wrote: >> I'm working right now to get a project created on RubyForge and >> trying to come up with a reasonable name for the extension. How does >> 'RadiantFromRails' sound? >> >> I'm up for getting together with you an

Re: [Radiant] Installation issue

2007-05-28 Thread Matt Parrish
This is just a guess here, but make sure you are running the migrate in the right environment. I think for production, you should run rake production db:migrate On May 28, 2007, at 6:23 PM, Cameron wrote: > John - FYI, I ran into the same issue. > > Radiant 0.6.1 > FreeBSD 6.2 > MySQL 4.1.22

Re: [Radiant] Radiant integration with another Rails app?

2007-05-28 Thread Matt Parrish
o set a date and time for you, Sean and myself > (and anyone else interested) to meet-up in #radiantcms IRC on this > topic... > > Glad there is something already happening on this front! > > Loren > > > > On May 28, 2007, at 10:13 AM, Matt Parrish wrote: > >> Hi

Re: [Radiant] Radiant integration with another Rails app?

2007-05-28 Thread Matt Parrish
Hi Loren, Nice to talk to you again! ;) I'm working on the same thing right now. I currently have a Radiant extension that allows Radiant to live in /vendor while having a Rails app at it's current location with only a slight modification required for config/routes.rb to work properly. It

Re: [Radiant] JavaScript in a Page?

2007-05-28 Thread Matt Parrish
Hi Oliver, You have two typical options in this case. The first is to give your element an id, just like you did for the element. Then you could use that id in your javascript. The other method, though, is probably what you want. You could keep your html and javascript the way it is,