[Radiant] restart server on site5

2010-02-03 Thread Ming Pan
Hi,

I've been using the web hosting service provided by site5.com, and it
seems to be working well with radiant cms. But I've never figured out
the right way to restart server, which is often required while
adding new extensions or changing environment.rb. I searched around
and tried many things like to touch public/dispatch.fcgi, touch
tmp/restart.txt, kill ruby process, ...,  but never knew which one
worked or not or worked properly. Anyone knows about that? And how to
determine the server has been restarted properly? For example,
anything to look for in the log file?

I'm asking this question because I'm having trouble with the mailer
extension and I suspect that I'm not restarting the server properly.

Thanks.

ming
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


Re: [Radiant] restart server on site5

2010-02-03 Thread john muhl
http://wiki.github.com/radiant/radiant/installing-on-site5 says they
support passenger so if you're using that then `touch tmp/restart.txt`
should do the trick. if not you'll have to figure out what application
server you are using before anyone can tell you how to restart it.

On Wed, Feb 3, 2010 at 11:15 AM, Ming Pan fallspin...@gmail.com wrote:
 Hi,

 I've been using the web hosting service provided by site5.com, and it
 seems to be working well with radiant cms. But I've never figured out
 the right way to restart server, which is often required while
 adding new extensions or changing environment.rb. I searched around
 and tried many things like to touch public/dispatch.fcgi, touch
 tmp/restart.txt, kill ruby process, ...,  but never knew which one
 worked or not or worked properly. Anyone knows about that? And how to
 determine the server has been restarted properly? For example,
 anything to look for in the log file?

 I'm asking this question because I'm having trouble with the mailer
 extension and I suspect that I'm not restarting the server properly.

 Thanks.

 ming
 ___
 Radiant mailing list
 Post: Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
 Radiant: http://radiantcms.org
 Extensions: http://ext.radiantcms.org

___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org

Re: [Radiant] restart server on site5

2010-02-03 Thread Ming Pan
Thanks John. I'm also a bit puzzled by what application server I'm
running on. I turned on the Phusion Passenger in my .htaccess file,
and my page won't render properly if I don't. So I assume I'm running
on Phusion Passenger. When I checked server processes, I saw a lot of
user having this process:

/usr/bin/ruby dispatch.fcgi

But I don't have this process at all, and got confused about what happened.

ming

On Wed, Feb 3, 2010 at 12:25 PM, john muhl johnm...@gmail.com wrote:
 http://wiki.github.com/radiant/radiant/installing-on-site5 says they
 support passenger so if you're using that then `touch tmp/restart.txt`
 should do the trick. if not you'll have to figure out what application
 server you are using before anyone can tell you how to restart it.

___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


Re: [Radiant] Radiant Installation Failing Using Ruby 1.9.1/1.8.7

2010-02-03 Thread Jim Gay
I'll double check, but it basically just changes the requirements on
cucumber to = rather than ~
I want to throw any bug fixes I can in there too, such as
http://github.com/radiant/radiant/issues/#issue/79

On Wed, Feb 3, 2010 at 6:48 AM, Sean Cribbs seancri...@gmail.com wrote:
 Jim,

 Is that intermediate version ready to go?  If so, we can release it this
 weekend after I get home, or John can help you release it before then.

 Sean

 On 2/2/10 11:17 PM, Jim Gay wrote:
 Uninstall cucumber and it should work on 1.8.7. Radiant is not 1.9.1 ready 
 yet.

 I want to release an intermediate version that doesn't have this
 problem with cucumber.

 On Tue, Feb 2, 2010 at 11:09 PM, Conrad Taylorconra...@gmail.com  wrote:

 Hi, Radiant installation is failing with ruby 1.8.7 (2010-01-10 patchlevel
 249) [i686-linux] because I'm getting the following error message:

 $ rake production db:bootstrap (in /home/conradwt/rails.dir/examples/test)
 rake aborted!
 undefined method `feature_pattern=' for #Cucumber::Rake::Task:0xb77941d8
 /home/conradwt/.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10 (See
 full trace by running task with --trace)

 and

 $ rake db:bootstrap (in /home/conradwt/rails.dir/examples/test) rake
 aborted!
 undefined method `feature_pattern=' for #Cucumber::Rake::Task:0xb770b914
 /home/conradwt/.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10 (See
 full trace by running task with --trace)

 Next, I'm seeing much better success using Ruby 1.8.7 with the clone of the
 github project instead of the radiant gem.

 Lastly, I have tried using Ruby 1.9.1 with the clone of the github project
 but it required changes to the script files because

 they were referencing an incorrect path for the boot file.  The fix was to
 revert the files back to the Rails standard script

 files (i.e. 2.3.5).  Then Radiant appears to be functional on the admin and
 generates an error message on the client for Ruby

 1.9.1.  However, it continued to work on both the client and admin for Ruby
 1.8.7.

 -Conrad

___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


Re: [Radiant] Radiant Installation Failing Using Ruby 1.9.1/1.8.7

2010-02-03 Thread Conrad Taylor
On Tue, Feb 2, 2010 at 11:17 PM, Jim Gay j...@saturnflyer.com wrote:

 Uninstall cucumber and it should work on 1.8.7. Radiant is not 1.9.1 ready
 yet.

 I want to release an intermediate version that doesn't have this
 problem with cucumber.


Actually, I didn't have to uninstall Cucumber to get everything working in
Ruby 1.8.7.

-Conrad

On Tue, Feb 2, 2010 at 11:09 PM, Conrad Taylor conra...@gmail.com wrote:
  Hi, Radiant installation is failing with ruby 1.8.7 (2010-01-10
 patchlevel
  249) [i686-linux] because I'm getting the following error message:
 
  $ rake production db:bootstrap (in
 /home/conradwt/rails.dir/examples/test)
  rake aborted!
  undefined method `feature_pattern=' for
 #Cucumber::Rake::Task:0xb77941d8
  /home/conradwt/.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10
 (See
  full trace by running task with --trace)
 
  and
 
  $ rake db:bootstrap (in /home/conradwt/rails.dir/examples/test) rake
  aborted!
  undefined method `feature_pattern=' for
 #Cucumber::Rake::Task:0xb770b914
  /home/conradwt/.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10
 (See
  full trace by running task with --trace)
 
  Next, I'm seeing much better success using Ruby 1.8.7 with the clone of
 the
  github project instead of the radiant gem.
 
  Lastly, I have tried using Ruby 1.9.1 with the clone of the github
 project
  but it required changes to the script files because
 
  they were referencing an incorrect path for the boot file.  The fix was
 to
  revert the files back to the Rails standard script
 
  files (i.e. 2.3.5).  Then Radiant appears to be functional on the admin
 and
  generates an error message on the client for Ruby
 
  1.9.1.  However, it continued to work on both the client and admin for
 Ruby
  1.8.7.
 
  -Conrad
 --
 Jim Gay
 http://www.saturnflyer.com
 ___
 Radiant mailing list
 Post: Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
 Radiant: http://radiantcms.org
 Extensions: http://ext.radiantcms.org

___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


Re: [Radiant] restart server on site5

2010-02-03 Thread Joel Oliveira
If you monitor your production log file while you're attempting all the
various restart options that might tell you when you bounce it correctly.

Like John said, with passenger it's usually touch tmp/restart.txt ... if you
view the logfile with `tail -f log\production.log` in one shell and attempt
a restart with `touch tmp/restart.txt` it might tip you off to whether it
worked.

- Joel

On Wed, Feb 3, 2010 at 12:40 PM, Ming Pan fallspin...@gmail.com wrote:

 Thanks John. I'm also a bit puzzled by what application server I'm
 running on. I turned on the Phusion Passenger in my .htaccess file,
 and my page won't render properly if I don't. So I assume I'm running
 on Phusion Passenger. When I checked server processes, I saw a lot of
 user having this process:

 /usr/bin/ruby dispatch.fcgi

 But I don't have this process at all, and got confused about what happened.

 ming

 On Wed, Feb 3, 2010 at 12:25 PM, john muhl johnm...@gmail.com wrote:
  http://wiki.github.com/radiant/radiant/installing-on-site5 says they
  support passenger so if you're using that then `touch tmp/restart.txt`
  should do the trick. if not you'll have to figure out what application
  server you are using before anyone can tell you how to restart it.
 
 ___
 Radiant mailing list
 Post: Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
 Radiant: http://radiantcms.org
 Extensions: http://ext.radiantcms.org

___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


Re: [Radiant] Radiant Installation Failing Using Ruby 1.9.1/1.8.7

2010-02-03 Thread Jake Skedgell
This 0.8.2 bug fix release would be very welcome.

There is also a problem with the bundled Rails that conflicts with the new
Rack 1.1.0. I don't know how easily that could be fixed. It's not really a
Radiant bug.

Any idea when we can expect 0.9 to be finished?

Jake Skedgell


On Wed, Feb 3, 2010 at 5:48 PM, Jim Gay j...@saturnflyer.com wrote:

 I'll double check, but it basically just changes the requirements on
 cucumber to = rather than ~
 I want to throw any bug fixes I can in there too, such as
 http://github.com/radiant/radiant/issues/#issue/79

 On Wed, Feb 3, 2010 at 6:48 AM, Sean Cribbs seancri...@gmail.com wrote:
  Jim,
 
  Is that intermediate version ready to go?  If so, we can release it this
  weekend after I get home, or John can help you release it before then.
 
  Sean
 
  On 2/2/10 11:17 PM, Jim Gay wrote:
  Uninstall cucumber and it should work on 1.8.7. Radiant is not 1.9.1
 ready yet.
 
  I want to release an intermediate version that doesn't have this
  problem with cucumber.
 
  On Tue, Feb 2, 2010 at 11:09 PM, Conrad Taylorconra...@gmail.com
  wrote:
 
  Hi, Radiant installation is failing with ruby 1.8.7 (2010-01-10
 patchlevel
  249) [i686-linux] because I'm getting the following error message:
 
  $ rake production db:bootstrap (in
 /home/conradwt/rails.dir/examples/test)
  rake aborted!
  undefined method `feature_pattern=' for
 #Cucumber::Rake::Task:0xb77941d8
  /home/conradwt/.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10
 (See
  full trace by running task with --trace)
 
  and
 
  $ rake db:bootstrap (in /home/conradwt/rails.dir/examples/test) rake
  aborted!
  undefined method `feature_pattern=' for
 #Cucumber::Rake::Task:0xb770b914
  /home/conradwt/.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10
 (See
  full trace by running task with --trace)
 
  Next, I'm seeing much better success using Ruby 1.8.7 with the clone of
 the
  github project instead of the radiant gem.
 
  Lastly, I have tried using Ruby 1.9.1 with the clone of the github
 project
  but it required changes to the script files because
 
  they were referencing an incorrect path for the boot file.  The fix was
 to
  revert the files back to the Rails standard script
 
  files (i.e. 2.3.5).  Then Radiant appears to be functional on the admin
 and
  generates an error message on the client for Ruby
 
  1.9.1.  However, it continued to work on both the client and admin for
 Ruby
  1.8.7.
 
  -Conrad
 
 ___
 Radiant mailing list
 Post: Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
 Radiant: http://radiantcms.org
 Extensions: http://ext.radiantcms.org

___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


Re: [Radiant] Radiant Installation Failing Using Ruby 1.9.1/1.8.7

2010-02-03 Thread john muhl
On Wed, Feb 3, 2010 at 4:18 PM, Conrad Taylor conra...@gmail.com wrote:
 On Wed, Feb 3, 2010 at 4:31 PM, Jake Skedgell jjskedg...@gmail.com wrote:

 This 0.8.2 bug fix release would be very welcome.

 There is also a problem with the bundled Rails that conflicts with the new
 Rack 1.1.0. I don't know how easily that could be fixed. It's not really a
 Radiant bug.

 Any idea when we can expect 0.9 to be finished?

 Jake Skedgell


 Does anyone know which version of Rails is being used with the current
 github version
 of Radiant?

http://github.com/radiant/radiant/tree/master/vendor/rails/
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


Re: [Radiant] Radiant Installation Failing Using Ruby 1.9.1/1.8.7

2010-02-03 Thread Conrad Taylor
On Wed, Feb 3, 2010 at 5:20 PM, john muhl johnm...@gmail.com wrote:

 On Wed, Feb 3, 2010 at 4:18 PM, Conrad Taylor conra...@gmail.com wrote:
  On Wed, Feb 3, 2010 at 4:31 PM, Jake Skedgell jjskedg...@gmail.com
 wrote:
 
  This 0.8.2 bug fix release would be very welcome.
 
  There is also a problem with the bundled Rails that conflicts with the
 new
  Rack 1.1.0. I don't know how easily that could be fixed. It's not really
 a
  Radiant bug.
 
  Any idea when we can expect 0.9 to be finished?
 
  Jake Skedgell
 
 
  Does anyone know which version of Rails is being used with the current
  github version
  of Radiant?


The script files for the project appear to be out of date being that they
differ from
the standard files script files in Rails 2.3.5.

-Conrad


 http://github.com/radiant/radiant/tree/master/vendor/rails/
 ___
 Radiant mailing list
 Post: Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
 Radiant: http://radiantcms.org
 Extensions: http://ext.radiantcms.org

___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


[Radiant] Radiant Shortcut Extension

2010-02-03 Thread subsor...@gmail.com
Has anyone had any luck in getting this extension working with radiant 0.8?

I'm getting this error when I try to visit the homepage when it is set as a
Shortcut Finder as per instructions:

NoMethodError (undefined method `include?' for nil:NilClass):
  vendor/extensions/shortcut/app/models/shortcut_finder_page.rb:5:in
`find_by_url'
  radiant (0.8.1) app/models/page.rb:177:in `find_by_url'
  radiant (0.8.1) app/controllers/site_controller.rb:41:in `find_page'
  radiant (0.8.1) app/controllers/site_controller.rb:19:in `show_page'
  radiant (0.8.1) vendor/plugins/haml/rails/./lib/sass/plugin/rails.rb:19:in
`process'

shortcut_finder_page.rb:

class ShortcutFinderPage  Page
  def find_by_url(url, live = true, clean = true)
url = clean_url(url) if clean
slugged_url = url.gsub!(%r{^/},'').gsub!(%r{/$},'')
unless slugged_url.include?('/')
  children.find_by_class_name('ShortcutDisplayPage')
else
  super
end
  end
end


I noticed there is a call to response::cache in shortcut_display_page.rb
whose removal allows for the displaying of the shortcut pages to work as
intended; it is just that the homepage is causing an error with this line:

unless slugged_url.include?('/')

If I add  slugged_url.nil? to get around the error it will display the
homepage but will also display all subpages as shortcuts regardless of their
shortcut setting...

Does anyone know how to go about fixing this problem?

Thanks as always,

Dominic
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org


Re: [Radiant] Radiant Installation Failing Using Ruby 1.9.1/1.8.7

2010-02-03 Thread Ben Evans
Regarding your errors getting Radiant working due to a Cucumber version
mismatch, I was able to install the older version of Cucumber along side the
newer version and everything started working.

I just ran this command:

gem install cucumber -v 0.3.104

Hope this helps people work around the issue until Radiant updates their
release.

Subject:
[Radiant] Radiant Installation Failing Using Ruby 1.9.1/1.8.7
From:
Conrad Taylor conra...@gmail.com
Date:
Tue, 2 Feb 2010 23:09:43 -0500
To:
radiant@radiantcms.org

Hi, Radiant installation is failing with ruby 1.8.7 (2010-01-10 patchlevel
249) [i686-linux] because I'm getting the following error message:

$ rake production db:bootstrap (in /home/conradwt/rails.dir/examples/test)
rake aborted!
undefined method `feature_pattern=' for
#Cucumber::Rake::Task:0xb77941d8*/home/conradwt/*.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10
(See
full trace by running task with --trace)

and

$ rake db:bootstrap (in /home/conradwt/rails.dir/examples/test) rake
aborted!
undefined method `feature_pattern=' for
#Cucumber::Rake::Task:0xb770b914*/home/conradwt/*.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10
(See
full trace by running task with --trace)

Next, I'm seeing much better success using Ruby 1.8.7 with the clone of the
github project instead of the radiant gem.

Lastly, I have tried using Ruby 1.9.1 with the clone of the github project
but it required changes to the script files because

they were referencing an incorrect path for the boot file.  The fix was to
revert the files back to the Rails standard script

files (i.e. 2.3.5).  Then Radiant appears to be functional on the admin and
generates an error message on the client for Ruby

1.9.1.  However, it continued to work on both the client and admin for Ruby
1.8.7.

-Conrad
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org