Upgrade from 1.0.2 -> 1.2 causing 404's

I had a running installation of 1.0.2, and wanted to upgrade so I could use some comment catptcha stuff in some of the new themes I've seen.

I deleted everything from my zenphoto root EXCEPT the albums folder, and the older .htaccess, and the cache folder (as well as a cache_bak which was owned by nobody ... couldn't delete it).

I uploaded all the dirs from the new distro to my wbeserver. I navigated to setup.php, and that responded with the usual checking info. So far, so good. Well, after I clicked "Go", I get a 404 thrown back from my Wordpress.

I evaluated the older htaccess, and the newer one included with 1.2. I've tried both, and they both 404. Static content (License.txt, README.html) are being served from /zenphoto correctly.

I'm sure there's something drastically wrong with my .htaccess, but I just can't figure it out! Here's the contents:

`

# htaccess file version 1.1.6.0

# Update the above and the define in setup.php when you make changes to the rewrite rules!

# NOTE: Change the RewriteBase below to the absolute path to your zenphoto directory. (Or let setup.php do it for you!)



RewriteEngine On

#### !!! Change this to the web path (eg: http://www.yourwebsite.com/photos --> /photos) !!!

RewriteBase /zenphoto

####

RewriteRule ^admin/?$ zp-core/admin.php [R,L]

RewriteCond %{REQUEST_FILENAME} -d

RewriteRule ^albums/?(.+/?)?$ $1 [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]

RewriteCond %{REQUEST_FILENAME} -d

RewriteRule ^.*$ - [R,L]

RewriteRule index\.php$ index.php [L,QSA]

RewriteRule ^page/([0-9]+)/?$ index.php?page=$1 [L,QSA]

RewriteRule ^page/([A-Za-z0-9\-_]+)/?$ index.php?p=$1 [L,QSA]

RewriteRule ^(.*)/page/([0-9]+)/?$ index.php?album=$1&page=$2 [L,QSA]

RewriteRule ^(.*)page/([A-Za-z0-9\-_]+)/?$ index.php?album=$1&p=$2 [L,QSA]

#### Rewrite rule addtion for search

RewriteRule ^page/([A-Za-z0-9\-_]+)/fields([0-9]+)/(.*)/([0-9]+)/?$ index.php?p=$1&searchfields=$2&words=$3&page=$4 [L,QSA]

RewriteRule ^page/([A-Za-z0-9\-_]+)/fields([0-9]+)/(.*)/?$ index.php?p=$1&searchfields=$2&words=$3 [L,QSA]

RewriteRule ^page/([A-Za-z0-9\-_]+)/archive/(.*)/([0-9]+)/?$ index.php?p=$1&date=$2&page=$3 [L,QSA]

RewriteRule ^page/([A-Za-z0-9\-_]+)/archive/(.*)/?$ index.php?p=$1&date=$2 [L,QSA]

RewriteRule ^page/([A-Za-z0-9\-_]+)/tags/(.*)/([0-9]+)/?$ index.php?p=$1&searchfields=4&words=$2&page=$3 [L,QSA]

RewriteRule ^page/([A-Za-z0-9\-_]+)/tags/(.*)/?$ index.php?p=$1&searchfields=4&words=$2 [L,QSA]

RewriteRule ^page/([A-Za-z0-9\-_]+)/(.*)/([0-9]+)/?$ index.php?p=$1&words=$2&page=$3 [L,QSA]

RewriteRule ^page/([A-Za-z0-9\-_]+)/(.*)/?$ index.php?p=$1&words=$2 [L,QSA]

RewriteRule ^(.*)/image/(thumb|[0-9]{1,4})/([^/\\]+)$ zp-core/i.php?a=$1&i=$3&s=$2 [L,QSA]

RewriteRule ^(.*)/image/([^/\\]+)$ zp-core/i.php?a=$1&i=$2 [L,QSA]

####

# Catch-all - everything else gets handled in PHP for compatibility.

RewriteRule ^(.*)/?$ index.php?album=$1 [L,QSA]



`

One interesting note: if I try to navigate to .../zenphoto/admin, I'll see the browser's address bar redirect to .../zenphoto/zp-core/admin.php, and I'll still get the 404.

Is it possible something got borked on the DB side, and the errors aren't being propagated?

Comments

  • don't think i got those, but damn did i ever get a lot of error pages. it was ridiculous. i was so aggravated, i just cleaned house and reinstalled from scratch and just reuploaded all my images :P hehe
  • Well according to
    http://www.zenphoto.org/2008/08/installation-and-upgrading/#2
    Its 'easy' to upgrade... "With anything after ZenPhoto 1.1.3, upgrading is super easy!"

    If you have a version before 1.1.3 Im not sure what you have to do in order to upgrade...

    I would personally delete all files, everything except albums... and download the latest zenphoto... I would basically do a fresh start, your files may be too out of date to do a full and complete upgrade... This is just speculation on my part...
  • This sounds like a problem some servers have with the zenphoto .htaccess file in version 1.2. We have made a change in the nightly build that fixed the problem for those people that were having it. You could give the nightly build a try.

    BTW, if you are using the distributed .htaccess file un modified it really is not necessary to post it. If you have modified it the best thing is to describe your changes. It would be really easy for us to miss seing a change in all that code listing.
  • My apologies for the full htaccess -- I just wanted to be as thorough as possible with describing my specific errors. I'll give the nightly htaccess a try and report back.
Sign In or Register to comment.