# Problems after updating app from 0.6.7 =\> 0.6.9

**URL:** <https://www.ruby-forum.com/t/problems-after-updating-app-from-0-6-7-0-6-9/154614>\
**Category:** Radiant CMS\
**Created:** [December 2, 2008, 5:07am UTC](https://www.ruby-forum.com/t/problems-after-updating-app-from-0-6-7-0-6-9/154614 "2008-12-02T05:07:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nateless](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/96bed5/32.png) [@nateless](https://www.ruby-forum.com/u/nateless)\
**Post date:** [December 2, 2008, 5:07am UTC](https://www.ruby-forum.com/t/problems-after-updating-app-from-0-6-7-0-6-9/154614/1 "2008-12-02T05:07:19Z")

</div>

I have an app that I tried to update from 0.6.7 to 0.6.9 and have run  
into a  
couple of problems.

It started a bit like this. I ran “rake radiant:update” which seemed to  
complete successfully. But when I tried to “rake db:migrate” I was  
greeted  
with the error:  
…  
rake aborted!  
undefined method `[]’ for #Enumerable::Enumerator:0x2329874  
…

So I searched around and saw what looked like a cure here (11th  
response):  
[http://groups.google.com/group/radiantcms-dev/browse\_thread/thread/309b7516b2bb72f9?fwc=2](http://groups.google.com/group/radiantcms-dev/browse_thread/thread/309b7516b2bb72f9?fwc=2)  
…  
unless ‘1.9’.respond\_to?(:force\_encoding)  
String.class\_eval do  
begin  
remove\_method :chars  
rescue NameError  
# OK  
end  
end  
end  
…

# Then I ran “rake db:migrate” the migration died when it got to the sessions table with this error: … == 16 AddSessions: migrating

– create\_table(:sessions)  
rake aborted!  
Mysql::Error: Table ‘sessions’ already exists: CREATE TABLE `sessions`  
(`id`  
int(11) DEFAULT NULL auto\_increment PRIMARY KEY, `session_id`  
varchar(255)  
DEFAULT NULL, `data` text DEFAULT NULL, `updated_at` datetime DEFAULT  
NULL)  
ENGINE=InnoDB

(See full trace by running task with --trace)  
…

So I truncated the sessions table and the rake task completed  
successfully.  
After that, “script/server” started the application with no problem. But  
I  
discovered a new problem, my database had been wiped clean during the  
process, so when I tried viewing the site at 127.0.0.1:3000 I was  
greeted  
with a login screen.

I would really appreciate it if anybody who has run into similar  
problems  
could describe what they did to get through all this.

My setup:

Ruby 1.8.7  
Rails 2.2.2, 2.1.2 (tried both)  
Radiant 0.6.9

Extensions:

Archive  
Blog Tags  
Comments  
Copy Move  
Markdown Filter  
Page Attachments  
Share Layouts  
Subscriber Lists  
Textile Filter  
Wine Pairing Widget (custom extension)

On OSX 10.5, but the application originated in Ubuntu and was lovingly  
transferred over to the mac. Everything worked perfectly when it was  
running  
on radiant 0.6.7 in both OSX and Ubuntu.

Thanks,

Nate

---

<div class="post-metadata">

**Author:** ![nateless](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/96bed5/32.png) [@nateless](https://www.ruby-forum.com/u/nateless)\
**Post date:** [December 2, 2008, 7:55pm UTC](https://www.ruby-forum.com/t/problems-after-updating-app-from-0-6-7-0-6-9/154614/2 "2008-12-02T19:55:41Z")

</div>

Problem happened when you upgraded to Ruby 1.8.7. Use 1.8.6 if you can.