Problems upgrading to Typo 4.1.1

Hi everybody,
I downloaded and installed the latest version, 4.1.1, via the gem.
But now when I go to my Typo blog, the CSS doesn’t work and it won’t
accept my username and password to get into the admin panel. Also, it
shows all my old posts, but when I look in the database (with a MySQL
frontend), there are a bunch sample posts. Weird. Can anyone help me
out?

Thanks in advance.

Eamon F. [email protected] writes:

Hi everybody,
I downloaded and installed the latest version, 4.1.1, via the gem.
But now when I go to my Typo blog, the CSS doesn’t work and it won’t
accept my username and password to get into the admin panel. Also, it
shows all my old posts, but when I look in the database (with a MySQL
frontend), there are a bunch sample posts. Weird. Can anyone help me
out?

What version did you upgrade from?

You should probably try running the migrations by hand. From the root
directory of your typo installation, do:

RAILS_ENV=production rake db:migrate

Bounce the server (or the dispatch.fcgi processes) and see where that
gets you.

I’m upgrading from 4.0.3.

Hmm, I tried running “RAILS_ENV=production rake db:migrate” and then
restarting the server, but it didn’t have any effect… Any other
things I can try?

Yeah; I connected the production, dev, and test all to the same
database.

Are you defnitely connecting to the production database (not devel or
test)?

On 11/05/07, Eamon F. [email protected] wrote:

Yeah; I connected the production, dev, and test all to the same
database.

On Saturday 12 May 2007 17:15, Dick D. wrote:

That’s a really bad idea.

Especially test and production. Run the unit tests just once and blam.

TX

OK. I’m really new to Rails, so I have just a little more than no
idea what the test/dev/production environments are about. I’ll try
creating a new database for test.

That’s a really bad idea.

On 11/05/07, Eamon F. [email protected] wrote:

Yeah; I connected the production, dev, and test all to the same
database.

On May 11, 2007, at 1:47 AM, Dick D. wrote:

Are you defnitely connecting to the production database (not devel
or test)?

Eamon F. [email protected] writes:

Le 12 mai 07 à 23:10, Eamon F. a écrit :

Yeah; I connected the production, dev, and test all to the same

Also, it
shows all my old posts, but when I look in the database (with a
MySQL
frontend), there are a bunch sample posts. Weird.

test database is for tests and wiped everytime rake test is ran and
filled with test data
development databsae is for… developpment
production test is for production

Rails application really should have at least 2 (test + dev / prod)
databases

Frédéric de Villamil
[email protected] tel: +33 (0)6 62 19 1337
http://fredericdevillamil.com Typo : http://typosphere.org

Aha, okay. Thanks.

OK, I found my problem. For some reason, when I install 4.1.1 using
the gem and it automatically migrates the database, the migration is
all wrong. So if I first backup my old database, install 4.1.1 (which
will automatically try to migrate the database), restore the old
database, and then migrate it myself using rake db:migrate,
everything seems to work fine.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs