redirect loop after install -- nonexistent admin/upgrade

Hello,

I've made it most of the way through a new install of omeka 1.3 on a fresh red hat EL 4.4 server with php 5.3.2, accessing a mysql 5.0 database on another server.

I filled in the boxes on the "install" page, and was informed that all is well and I can delete the install directory.

However, when I go to omeka in the browser I get a message telling me I cannot access until upgrade is complete. When I go to omeka/admin I hit a redirect loop. There's nothing in apache error log, but the access log (copied below in part) indicates that the site is trying to get to admin/upgrade, which does not exist in the download I used.

I am not upgrading from another version, just doing a new install. Any ideas are appreciated!

Thanks very much,
Anna

apache access log:
ip - - [05/Jan/2011:11:42:52 -0500] "GET /omeka/admin/users/login HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/upgrade HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/users/login HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/upgrade HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/users/login HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/upgrade HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/users/login HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/upgrade HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/users/login HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"
ip - - [05/Jan/2011:11:42:53 -0500] "GET /omeka/admin/upgrade HTTP/1.1" 302 26 "-" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12"

I'm having the exact same problem on Red Hat EL 6. Has anyone made any progress on understanding why a clean install needs to see an upgrade folder?

Thanks

Bobb Menk

Did either of you encounter any errors during the installation, or re-use an old database for your install?

What you're seeing is Omeka falsely detecting that you need to upgrade your site, and the upgrade script itself detecting that Omeka is up-to-date.

Could you post the value of your "omeka_version" option from the "omeka_options" table?

As to the other part of your question, "admin/upgrade" is actually a valid Omeka URL.

Apart from the installer, most Omeka URLs don't directly correspond to files and folders on disk.

My timezone problem (see http://omeka.org/forums/topic/timezone-error-message-on-install) made Omeka declare itself installed, which could account for this in my case.

I did a "select * from omeka_options" got only one record name of omeka_version with an empty value field.

What's the next step?

Thanks for your help.

Bobb Menk

That empty version field is likely the source of your problem.

The timezone problem you were having made the install abort when only half-finished.

The easiest thing for you to do is probably to drop and re-add your database (or point db.ini at a new, untouched database), and run the installer again.

Drop the existing and re-adding a new copy appears to have worked - I can now login as admin and start exploring.

Thanks.

Bobb Menk

Worked for me, too -- I had first encountered the same timezone error as Bobb, discussed in http://omeka.org/forums/topic/timezone-error-message-on-install. Thanks very much, John and Bobb!

Anna