I recently upgraded to 1.1.0 and had no issues. Then I migrated all of my
assets inside the app (from my Public folder) and switched from Mongel as
my new host doesn't support it. I'm having the following issue on both my
host (the reborn TextDrive) and locally on my Mac (10.8.2).
I'm trying
Hi,
an important security update for Rails 2.3 was released, read more about it
here:
http://weblog.rubyonrails.org/2013/1/8/Rails-3-2-11-3-1-10-3-0-19-and-2-3-15-have-been-released/
As I understand Radiant uses a vendor Rails 2.3.14 version. How can one
update Radiant to use the security
Hi all
I'm trying and failing to install radiant on top of JRuby 1.7.2 - this is
my first bash with Ruby, and my reasons for chosing JRuby is I want to see
if I can integrate this very nice looking radiant CMS with some of our
existing servlets. Which no doubt will be my next question if I can
I've recently migrated my site to a host that doesn't like Mongrel. So I'm
trying out Unicorn and Thin. I've also moved all of my assets within the
app (from my Public folder).
Using Webrick I can see all assets displayed on the site appropriately. But
using Unicorn and Thin I cannot:
Hi Mike,
Happy new year! Welcome to Radiant :)
On 8/1/2013 4:04 AM, Mike B wrote:
I'm trying and failing to install radiant on top of JRuby 1.7.2 - this
is my first bash with Ruby, and my reasons for chosing JRuby is I want
to see if I can integrate this very nice looking radiant CMS with
config.assets.compile is a Rails 3 feature and Radiant is currently on Rails 2
Can you give any more details about this?
What URLs do you have and what should they be?
On Sun, Jan 6, 2013 at 12:26 AM, Lou Brothers l...@loubrothers.com wrote:
I've recently migrated my site to a host that doesn't
Hi Jim,
What about us poor sods who are running 0.9 and unable to update Radiant? :)
Kevin
On Wednesday, January 9, 2013 4:01:45 AM UTC-6, Jim Gay wrote:
Radiant no longer keeps vendor/rails in the gem. It's loaded by the
Gemfile.
I've just pushed Radiant 1.1.1 with a dependency on
Kevin,
See the rails security post here with details about getting around this problem.
https://groups.google.com/forum/#!topic/rubyonrails-security/61bkgvnSGTQ/discussion
On Wed, Jan 9, 2013 at 5:25 AM, Kevin Triplett mopacme...@gmail.com wrote:
Hi Jim,
What about us poor sods who are
Yes, I saw that, thanks.
Okay, here's what I did, please tell me if this will not work. :)
Added new file in radiant-0.9.1/config/initializers called rails.rb with
this single line:
ActionController::Base.param_parsers.delete(Mime::XML)
Thanks for your help! :D
On Wednesday, January 9, 2013
Or should that file go in
radiant-0.9.1/vendor/rails/railties/configs/initializers ?
On Wednesday, January 9, 2013 4:53:52 AM UTC-6, Kevin Triplett wrote:
Yes, I saw that, thanks.
Okay, here's what I did, please tell me if this will not work. :)
Added new file in
Thanks for offering assistance. I won't be able to reply again until the
weekend when I'm in front of my development machine.
Lou
On Wednesday, January 9, 2013 2:15:50 AM UTC-8, Jim Gay wrote:
config.assets.compile is a Rails 3 feature and Radiant is currently on
Rails 2
Can you give any
11 matches
Mail list logo
