# Upgrading to 0.7.0-rc2

**URL:** <https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624>\
**Category:** Radiant CMS\
**Created:** [January 26, 2009, 1:36am UTC](https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624 "2009-01-26T01:36:57Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [January 26, 2009, 1:36am UTC](https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624/1 "2009-01-26T01:36:57Z")

</div>

I attempted an upgrade to 0.7.0-rc2.

I got most everything worked out after I updated my extensions (reorder  
& copy\_move). However, I get an error when I access the site. Check it  
out at [http://www.benmorrow.info](http://www.benmorrow.info).

It looks like the server is looking at the 0.6.9 gem rather than the  
0.7.0 gem.

I ran both rake radiant:update and rake db:migrate.

Any suggestions?

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [January 26, 2009, 2:27am UTC](https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624/2 "2009-01-26T02:27:39Z")

</div>

Remove radiant 0.6.9. Or better, put radiant itself into your  
application, don’t rely on the radiant gem.

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [January 26, 2009, 4:12am UTC](https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624/3 "2009-01-26T04:12:33Z")

</div>

Joe Van D. wrote:

> Remove radiant 0.6.9. Or better, put radiant itself into your  
> application, don’t rely on the radiant gem.

Ha, it was my bad. I forgot to add the line:

ENV[‘GEM\_PATH’] = File.expand\_path(’~/.gems’) +  
‘:/usr/lib/ruby/gems/1.8’

to my environment.rb, which Dreamhost requires for user-installed gems.

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [January 26, 2009, 10:49pm UTC](https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624/4 "2009-01-26T22:49:13Z")

</div>

I’m using paperclipped with .7rc2 and on my mac’s server is runs  
smooth as butter. I pushed it up to my server (Joyent) and I can’t  
get the delete asset to work right. When I hit delete I get an  
Application error. Three refreshes and the image is gone and  
everything is fine. So in the log it says:

[paperclip] Deleting files for asset  
[paperclip] -\> /users/home/…public/assets/32/cowboy.gif  
Errno::EEXIST (File exists - /users/home/…public/assets/32):

and throws up 500.html

If I look at the files one of the images have been deleted

I could hit back and then try to delete it again and another will be  
deleted until they are all gone and the app will continue like  
everything is fine.

Any ideas why paperclipped isn’t deleting all four images like it  
should?

Thanks,

Steven

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [January 26, 2009, 11:12pm UTC](https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624/5 "2009-01-26T23:12:06Z")

</div>

I have not had time to check it with the new release, but there is a  
branch for it on github.There was a thread a few days ago. I will try  
to get in patched soon.

Keith

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [January 26, 2009, 11:44pm UTC](https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624/6 "2009-01-26T23:44:58Z")

</div>

I really don’t think it is a problem with the new release because it  
works perfectly on my mac’s server. I saw the change that was made  
and tried making that change too but it didn’t help with my problem.  
Maybe something went wrong when I installed it. There is a note in in  
the readme file about installing Settings before running the  
paperclipped migration. By the way, that note could be more helpful  
if it came before you give the paperclipped migration instructions.  
In my case, I had already run paperclipped migrations. For good  
measure I ran the paperclipped migrations again after I had installed  
settings.

Should I just start over or is this fixable? Everything seems to work  
well except deleting files. I’m just not sure if I caused this  
problem by migrating twice or maybe I’m missing something.

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [January 27, 2009, 6:37am UTC](https://www.ruby-forum.com/t/upgrading-to-0-7-0-rc2/158624/7 "2009-01-27T06:37:31Z")

</div>

The setting migration is only for the descriptions in the Settings  
plugin. That has nothing to do with the actual function of the  
paperclipped extension. There was a problem with deleting images if  
the bucket had never been used, I am pretty sure I squashed that  
though. Be sure you have the latest version of the paperclipped  
extension from github and then take a look at the production log from  
your server, that will tell you what the 500 error is. An older  
version of the extension gave me the same problem and the update fixed  
it. Let me know if you need more help.

Keith
