Maurizio Balestrieri wrote:
> 1) After upgradint to radiant 0.5.1. I got a "failed to update Rails
> version to 1.1.4 in config/environment.rb" message when updating an
> existing radiant instance. Is it harmful at all or just a warning?
>
> electronicbusiness radiant # radiant --upgrade .
> Upgrading Radiant to version 0.5.1...
> Would you like to create backups of files that Radiant replaces? [yN] y
> overwrote ./CHANGELOG
> backup CONTRIBUTORS? [Yn] y
> backed up CONTRIBUTORS as CONTRIBUTORS.20060803.bak
> overwrote ./CONTRIBUTORS
> created ./public/.htaccess
> created ./public/images/layout.png
> backup public/images/new-layout.png? [Yn] y
> backed up public/images/new-layout.png as new-layout.png.20060803.bak
> overwrote ./public/images/new-layout.png
> created ./script/console
> created ./script/version
>> failed to update Rails version to 1.1.4 in config/environment.rb
> you may need to do this yourself
> updated Radiant version to 0.5.1 in config/instance.yml
> Done.
Please post your config/environment.rb. Radiant uses a simple regular
expression to substitute the gem version:
if file_sub(filename, /RAILS_GEM_VERSION\s*=\s*'\d[\.\d]+'/m,
"RAILS_GEM_VERSION = '#{version}'")
See line 294 for the whole method:
http://dev.radiantcms.org/radiant/browser/trunk/radiant/bin/radiant#L294
> 2) I issued again an update command on the same place I did before and
> I got the following "Cannot detect that Radiant is installed in this
> directory!" (below also an "ll" command of the instance directory):
Mmmm. I'll look into this.
--
John Long
http://wiseheartdesign.com
_______________________________________________
Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant
