RE: [Radiant] Latest stable version schema
Thanks team- I'm going to write an RFP for migration of my older site. I'll send it to the group if anyone is interested. I've tried twice and haven't been successful at getting my current database schema to match up to the newer radiant. I don't have a lot of older gems, but I'd like to add more when I upgrade. Met vriendelijke groet, Adam Waterson Online Marketing Manager __ Planon International B.V. Wijchenseweg 8 6537 TL Nijmegen The Netherlands M: +31 (0) 6 514 75 514 E: [email protected] O: +31 (0) 24 7501 548 W: www.planonsoftware.com -Original Message- From: [email protected] [mailto:[email protected]] On Behalf Of Mohit Sindhwani Sent: Tuesday, January 22, 2013 3:52 AM To: [email protected] Cc: Michael Starke Subject: Re: [Radiant] Latest stable version schema Hi Adam, On 22/1/2013 4:06 AM, Michael Starke wrote: > The dilemma with outdated information about extensions is something I > bump into more often than i would like to. My solution is to search > rubygems for a recent gem, if there is none, look for a github repo > and take the time to sift through all the forks and find the > "best-patched" one. Try looking for big radiant contributors (Jim Gay, > John Muhl, William Ross, etc.). Sticking to their versions most of the > time does the trick. Sometimes I go the extra mile and fork and gemify > them myself. > > This solution is nothing to die for and if you're depending on a lot > of (possibly stale) extensions you might not get lucky. Since so far > we fared well with this method. It's time consuming but worth the > effort if you can catch up with radiants versions. I'm updating an old site to 1.1.1 and have a lot of older extensions that I was using. If you are migrating, post the list of extensions that you were using and I can let you know which ones I've verified. On the other hand, if you're starting out, just post in what you want to do and I can let you know if I'm doing something similar and what extension/ fork I'm using for it. Best Regards, Mohit.
Re: [Radiant] Latest stable version schema
Hi Adam, On 22/1/2013 4:06 AM, Michael Starke wrote: The dilemma with outdated information about extensions is something I bump into more often than i would like to. My solution is to search rubygems for a recent gem, if there is none, look for a github repo and take the time to sift through all the forks and find the "best-patched" one. Try looking for big radiant contributors (Jim Gay, John Muhl, William Ross, etc.). Sticking to their versions most of the time does the trick. Sometimes I go the extra mile and fork and gemify them myself. This solution is nothing to die for and if you're depending on a lot of (possibly stale) extensions you might not get lucky. Since so far we fared well with this method. It's time consuming but worth the effort if you can catch up with radiants versions. I'm updating an old site to 1.1.1 and have a lot of older extensions that I was using. If you are migrating, post the list of extensions that you were using and I can let you know which ones I've verified. On the other hand, if you're starting out, just post in what you want to do and I can let you know if I'm doing something similar and what extension/ fork I'm using for it. Best Regards, Mohit.
Re: [Radiant] Latest stable version schema
Hi Adam, considering the security question - 2.3.15 rails should do the trick. I do not know what version of radiant is the minimum, but we're using 1.0.1 with rails 2.3.15 The dilemma with outdated information about extensions is something I bump into more often than i would like to. My solution is to search rubygems for a recent gem, if there is none, look for a github repo and take the time to sift through all the forks and find the "best-patched" one. Try looking for big radiant contributors (Jim Gay, John Muhl, William Ross, etc.). Sticking to their versions most of the time does the trick. Sometimes I go the extra mile and fork and gemify them myself. This solution is nothing to die for and if you're depending on a lot of (possibly stale) extensions you might not get lucky. Since so far we fared well with this method. It's time consuming but worth the effort if you can catch up with radiants versions. -Michael On 21.01.2013 20:28, Adam Waterson wrote: Hey guys- What’s the most recent Ruby | Rails | Radiant combination that patches the security risk? Ruby 1.9.1 | Rails 2.3.15 | Radiant 1.1.1 ? Also is there a more up-to-date extensions list somewhere? Last time I checked there were many on the radiant site that are a bit out of date. Met vriendelijke groet, Adam Waterson Online Marketing Manager __ Planon International B.V. Wijchenseweg 8 6537 TL Nijmegen The Netherlands M: +31 (0) 6 514 75 514 E: [email protected] O: +31 (0) 24 7501 548 W: www.planonsoftware.com -- ___m i c h a e l s t a r k e geschäftsführer HicknHack Software GmbH www.hicknhack-software.com ___k o n t a k t +49 (170) 3686136 [email protected] ___H i c k n H a c k S o f t w a r e G m b H geschäftsführer - maik lathan | andreas reischuck | michael starke bayreuther Straße 32 01187 dresden amtsgericht dresden HRB 30351 sitzt - dresden
Re: [Radiant] Latest stable version schema
Radiant 1.1.1 patches it, but you can create an initializer with "ActionController::Base.param_parsers.delete(Mime::XML)" in other versions On Mon, Jan 21, 2013 at 2:28 PM, Adam Waterson wrote: > Hey guys- > > > > What’s the most recent Ruby | Rails | Radiant combination that patches the > security risk? Ruby 1.9.1 | Rails 2.3.15 | Radiant 1.1.1 ? > > > > Also is there a more up-to-date extensions list somewhere? Last time I > checked there were many on the radiant site that are a bit out of date. > > > > > > > > Met vriendelijke groet, > > > > > > Adam Waterson > > Online Marketing Manager > > __ > > > > Planon International B.V. > > Wijchenseweg 8 > > 6537 TL Nijmegen > > The Netherlands > > > > M: +31 (0) 6 514 75 514 > > E: [email protected] > > O: +31 (0) 24 7501 548 > > W: www.planonsoftware.com > > -- Write intention revealing code #=> http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
