Re: [Radiant] RubyGems 1.3.1 and Radiant < 0.6.4
Yes, install the appropriate gem version, then `gem unpack` into vendor, move the directory from radiant-0.6.x to radiant. Sean subsor...@gmail.com wrote: Thanks for the replies Mohit and Sean, Presumably from this I can just copy Radiant from the Gem directory to the Vendor directory to do this? Or do I have to freeze Radiant to a specific tag? It would be interesting to hear about a recommended guidelines on how to host and manage multiple radiant sites at some point ... perhaps another day. On 18 Feb 2009, at 02:10, Sean Cribbs wrote: Between 0.6.4 and 0.6.5, we had major changes to boot.rb that paralleled the changes in Rails, including removing the 'require_gem' line. Unfortunately, if you upgrade RubyGems, we cannot guarantee that your old Radiant sites will continue to work. However, if you do as Mohit says and put the old version of Radiant in vendor/radiant (as you should be doing if you aren't keeping all your sites on the same version), the 'require_gem' line will likely never be reached. Sean Mohit Sindhwani wrote: Sean Cribbs wrote: Dominic, Sorry, I don't know how you can get around that issue, except to update your sites to 0.7.x. The other day, I updated diopa.org to 0.7.0 and it is now significantly faster. I imagine you would encounter the same thing. One note about that conversion - I upgraded from 0.6.4 to 0.7.0 and I had to manually replace boot.rb to get it to upgrade. Sean I'm not sure if you can just include your Radiant distribution into the vendor directory. I *just* had a problem with one of my sites (on Radiant 0.6.1 or 0.6.4) returning Rails application failed to start up. On running dispatch.fcgi at the command line, I saw that it was a problem with RubyGems not finding anything called require_gem. In my case, the offending line was Line 28 of boot.rb that would do a require_gem with the version specified. (For some reason, the boot.rb does gem ... for requiring the Radiant gem when no version is specified but uses 'require_gem' when requiring a specific version). After looking at a few things, I found that another site had the same setup and the only difference was that Radiant was included in the vendor/radiant directory. I copied it from one site to the other and volia! It works! Sean may be able to suggest if that would indeed explain a fix, but either way, it's cheap to check. Cheers, Mohit. 2/18/2009 | 9:55 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RubyGems 1.3.1 and Radiant < 0.6.4
Thanks for the replies Mohit and Sean, Presumably from this I can just copy Radiant from the Gem directory to the Vendor directory to do this? Or do I have to freeze Radiant to a specific tag? It would be interesting to hear about a recommended guidelines on how to host and manage multiple radiant sites at some point ... perhaps another day. On 18 Feb 2009, at 02:10, Sean Cribbs wrote: Between 0.6.4 and 0.6.5, we had major changes to boot.rb that paralleled the changes in Rails, including removing the 'require_gem' line. Unfortunately, if you upgrade RubyGems, we cannot guarantee that your old Radiant sites will continue to work. However, if you do as Mohit says and put the old version of Radiant in vendor/radiant (as you should be doing if you aren't keeping all your sites on the same version), the 'require_gem' line will likely never be reached. Sean Mohit Sindhwani wrote: Sean Cribbs wrote: Dominic, Sorry, I don't know how you can get around that issue, except to update your sites to 0.7.x. The other day, I updated diopa.org to 0.7.0 and it is now significantly faster. I imagine you would encounter the same thing. One note about that conversion - I upgraded from 0.6.4 to 0.7.0 and I had to manually replace boot.rb to get it to upgrade. Sean I'm not sure if you can just include your Radiant distribution into the vendor directory. I *just* had a problem with one of my sites (on Radiant 0.6.1 or 0.6.4) returning Rails application failed to start up. On running dispatch.fcgi at the command line, I saw that it was a problem with RubyGems not finding anything called require_gem. In my case, the offending line was Line 28 of boot.rb that would do a require_gem with the version specified. (For some reason, the boot.rb does gem ... for requiring the Radiant gem when no version is specified but uses 'require_gem' when requiring a specific version). After looking at a few things, I found that another site had the same setup and the only difference was that Radiant was included in the vendor/radiant directory. I copied it from one site to the other and volia! It works! Sean may be able to suggest if that would indeed explain a fix, but either way, it's cheap to check. Cheers, Mohit. 2/18/2009 | 9:55 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RubyGems 1.3.1 and Radiant < 0.6.4
Between 0.6.4 and 0.6.5, we had major changes to boot.rb that paralleled the changes in Rails, including removing the 'require_gem' line. Unfortunately, if you upgrade RubyGems, we cannot guarantee that your old Radiant sites will continue to work. However, if you do as Mohit says and put the old version of Radiant in vendor/radiant (as you should be doing if you aren't keeping all your sites on the same version), the 'require_gem' line will likely never be reached. Sean Mohit Sindhwani wrote: Sean Cribbs wrote: Dominic, Sorry, I don't know how you can get around that issue, except to update your sites to 0.7.x. The other day, I updated diopa.org to 0.7.0 and it is now significantly faster. I imagine you would encounter the same thing. One note about that conversion - I upgraded from 0.6.4 to 0.7.0 and I had to manually replace boot.rb to get it to upgrade. Sean I'm not sure if you can just include your Radiant distribution into the vendor directory. I *just* had a problem with one of my sites (on Radiant 0.6.1 or 0.6.4) returning Rails application failed to start up. On running dispatch.fcgi at the command line, I saw that it was a problem with RubyGems not finding anything called require_gem. In my case, the offending line was Line 28 of boot.rb that would do a require_gem with the version specified. (For some reason, the boot.rb does gem ... for requiring the Radiant gem when no version is specified but uses 'require_gem' when requiring a specific version). After looking at a few things, I found that another site had the same setup and the only difference was that Radiant was included in the vendor/radiant directory. I copied it from one site to the other and volia! It works! Sean may be able to suggest if that would indeed explain a fix, but either way, it's cheap to check. Cheers, Mohit. 2/18/2009 | 9:55 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RubyGems 1.3.1 and Radiant < 0.6.4
Sean Cribbs wrote: Dominic, Sorry, I don't know how you can get around that issue, except to update your sites to 0.7.x. The other day, I updated diopa.org to 0.7.0 and it is now significantly faster. I imagine you would encounter the same thing. One note about that conversion - I upgraded from 0.6.4 to 0.7.0 and I had to manually replace boot.rb to get it to upgrade. Sean I'm not sure if you can just include your Radiant distribution into the vendor directory. I *just* had a problem with one of my sites (on Radiant 0.6.1 or 0.6.4) returning Rails application failed to start up. On running dispatch.fcgi at the command line, I saw that it was a problem with RubyGems not finding anything called require_gem. In my case, the offending line was Line 28 of boot.rb that would do a require_gem with the version specified. (For some reason, the boot.rb does gem ... for requiring the Radiant gem when no version is specified but uses 'require_gem' when requiring a specific version). After looking at a few things, I found that another site had the same setup and the only difference was that Radiant was included in the vendor/radiant directory. I copied it from one site to the other and volia! It works! Sean may be able to suggest if that would indeed explain a fix, but either way, it's cheap to check. Cheers, Mohit. 2/18/2009 | 9:55 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RubyGems 1.3.1 and Radiant < 0.6.4
Thanks Sean, Do you mean updating using the instructions for 0.6.5, creating a new site and then migrating the db would have the new boot.rb wouldn't it? If only I could get 0.7.1 working I'd feel better about going forward ;) Does Radiant or it's version of RoR require any specific version of RubyGems (I might just roll back for now)... Cheers, On 16 Feb 2009, at 19:03, Sean Cribbs wrote: Dominic, Sorry, I don't know how you can get around that issue, except to update your sites to 0.7.x. The other day, I updated diopa.org to 0.7.0 and it is now significantly faster. I imagine you would encounter the same thing. One note about that conversion - I upgraded from 0.6.4 to 0.7.0 and I had to manually replace boot.rb to get it to upgrade. Sean subsor...@gmail.com wrote: Hi, I have just updated to RubyGems 1.3.1 from an older version and now my old radiant gems are throwing a couple of errors due to some methods being depreciated: '#search support for String patterns is deprecated' and 'undefined method "require_gem"'. Is there a quick way to avoid having to update a number of Radiant sites to newer versions of radiant that would make them compatible with RubyGems 1.3.1, or is it a case of having to update all the sites and extensions? Presumably I could roll back rubygems and get them working again, any advise for this situation would be appreciated... Thanks Dominic ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RubyGems 1.3.1 and Radiant < 0.6.4
Dominic, Sorry, I don't know how you can get around that issue, except to update your sites to 0.7.x. The other day, I updated diopa.org to 0.7.0 and it is now significantly faster. I imagine you would encounter the same thing. One note about that conversion - I upgraded from 0.6.4 to 0.7.0 and I had to manually replace boot.rb to get it to upgrade. Sean subsor...@gmail.com wrote: Hi, I have just updated to RubyGems 1.3.1 from an older version and now my old radiant gems are throwing a couple of errors due to some methods being depreciated: '#search support for String patterns is deprecated' and 'undefined method "require_gem"'. Is there a quick way to avoid having to update a number of Radiant sites to newer versions of radiant that would make them compatible with RubyGems 1.3.1, or is it a case of having to update all the sites and extensions? Presumably I could roll back rubygems and get them working again, any advise for this situation would be appreciated... Thanks Dominic ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] RubyGems 1.3.1 and Radiant < 0.6.4
Hi, I have just updated to RubyGems 1.3.1 from an older version and now my old radiant gems are throwing a couple of errors due to some methods being depreciated: '#search support for String patterns is deprecated' and 'undefined method "require_gem"'. Is there a quick way to avoid having to update a number of Radiant sites to newer versions of radiant that would make them compatible with RubyGems 1.3.1, or is it a case of having to update all the sites and extensions? Presumably I could roll back rubygems and get them working again, any advise for this situation would be appreciated... Thanks Dominic ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
