Upgrading database not working (1.3.9 to 1.5.1)

The cache key file was synced but still no data is coming through.

Here's the htaccess code:

#
# @copyright Copyright 2003-2010 Zen Cart Development Team
# @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
# @version $Id: .htaccess 18695 2011-05-04 05:24:19Z drbyte $
#
# This is used with Apache WebServers
#
# The following blocks direct HTTP requests to all filetypes in this directory recursively, except certain approved exceptions
# It also prevents the ability of any scripts to run. No type of script, be it PHP, PERL or whatever, can normally be executed if ExecCGI is disabled.
# Will also prevent people from seeing what is in the dir. and any sub-directories
#
# For this to work, you must include either 'All' or at least: 'Limit' and 'Indexes' parameters to the AllowOverride configuration in your apache/conf/httpd.conf file.
# Additionally, if you want the added protection offered by the OPTIONS directive below, you'll need to add 'Options' to the AllowOverride list, if 'All' is not specified. 
# Example:
#<Directory "/usr/local/apache/htdocs">
#  AllowOverride Limit Options Indexes
#</Directory>
###############################

# deny *everything*
<FilesMatch ".*">
  Order Allow,Deny
  Deny from all
</FilesMatch>

# but now allow just *certain* necessary files:
<FilesMatch ".*\.(js|JS|css|CSS|jpg|JPG|gif|GIF|png|PNG|swf|SWF|xsl|XSL|svg|eot|ttf|woff)$">
  Order Allow,Deny
  Allow from all
</FilesMatch>

IndexIgnore */*


## NOTE: If you want even greater security to prevent hackers from running scripts in this folder, uncomment the following line (if your hosting company will allow you to use OPTIONS):
# OPTIONS -Indexes -ExecCGI

lafhaha:

Yes, I can log in fine. Everything works, it's just there's no 'old' data from the merge. Even though it is there in the DB.
Um ... in your old site, what was the DB_PREFIX value in your old configure.php files?
And I bet you put something different in your NEW configure.php files, right? (perhaps merely by giving zc_install a different table-prefix instead of using the same one you had in the old database).

The prefix actually names the database tables differently, and if you tell ZC the wrong prefix, then you've told it to look at the wrong tables ... hence not seeing any data.
Update both of your configure.php files to have the correct DB_PREFIX.

And then once you've done that you're going to need to run zc_install to do the database-upgrade step again ... because now you're pointing at the real data which isn't yet upgraded.

OMG OK THINGS ARE HAPPENING.

I don't want to screw this up since the DB prefix thing worked. I'm back to the zc_install step and am about to update the DB. It has automatically filled the prefix area with the one that I found in the OLD 1.3.9 file. (I didn't check that one..I was just comparing the new config Prefix settings - stupid!!) Do I put the same prefix in the box where it asks for a new one or do I leave that blank?

It would be the same prefix that you updated your new configure.php files to which should be the same as your old (1.3.9) configure.php files.

I can't believe that I danced around that issue without asking in a similar fashion. I think I only asked about what the database had for prefix(es) and omitted asking about the file that really cares. :) the Doctor saves the day again.

mc12345678:

It would be the same prefix that you updated your new configure.php files to which should be the same as your old (1.3.9) configure.php files.

I can't believe that I danced around that issue without asking in a similar fashion. I think I only asked about what the database had for prefix(es) and omitted asking about the file that really cares. :) the Doctor saves the day again.

Thank you again for all your help, and Dr too! I was so sure I had checked that file and there it was staring me in the face. You guys rock! :) My shop is working perfectly now!