Results 1 to 8 of 8
  1. #1
    Join Date
    Apr 2006
    Posts
    96
    Plugin Contributions
    0

    Default Upgrading to 1.3.9h problem

    A while ago two of my sites were hacked. I was able to finally clean them (I hope!) and now I'm trying to upgrade. One of the sites upgraded OK, the other one I'm stuck. I did follow directions correctly (again, I hope!) but I can't get it to work at all. Before the upgrade, I placed the site in Maintenance mode.

    Here's what I did:
    1. Created a new folder
    2. Created new database
    3. Transferred old one into new DB
    4. Upgraded
    5. Made changes to two config files

    Now I go to the directory where the new site is supposed to be and I get a blank page, url is: http://xxxxxxx.com/xxx/index.php?mai...or_maintenance
    I try to go to admin (I changed the admin folder name) and I get this error: 0 DB_ERROR_NOT_CONNECTED
    in:
    [db_cache table]
    If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.

    I put in the right username and pwd in config files so I don't know what's going on and I've about have it with this!
    Last edited by Kim; 30 Nov 2011 at 08:04 AM.

  2. #2
    Join Date
    Jan 2004
    Posts
    66,364
    Blog Entries
    7
    Plugin Contributions
    274

    Default Re: Upgrading to 1.3.9h problem

    0 DB_ERROR_NOT_CONNECTED -- this is a result of the database information being incorrect in the configure.php files. The DB_SERVER, DB_DATABASE, DB_USERNAME, DB_PASSWORD, DB_PREFIX must all be correct for the server you're on.

    If it's happening only on the admin side, then your /renamed-admin/includes/configure.php file has the wrong information.
    .

    Zen Cart - putting the dream of business ownership within reach of anyone!
    Donate to: DrByte directly or to the Zen Cart team as a whole

    Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
    Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.

  3. #3
    Join Date
    Apr 2006
    Posts
    96
    Plugin Contributions
    0

    Default Re: Upgrading to 1.3.9h problem

    That's what I thought, too - and it's true, my CPanel was messing up with db usernames. Fixed it.

    BUT, my troubles have not ended. I'm able to login to admin but it says my DB needs upgrading to 1.3.9 - I thought I had already done that! How can I do it now?

    And my store still doesn't show, it's a blank page with the url saying "index.php?main_page=down_for_maintenance" - although from the admin panel it is not in maintenance mode.

  4. #4
    Join Date
    Jan 2004
    Posts
    66,364
    Blog Entries
    7
    Plugin Contributions
    274

    Default Re: Upgrading to 1.3.9h problem

    Sounds like your non-admin configure.php has different DB settings than your admin configure.php file.
    .

    Zen Cart - putting the dream of business ownership within reach of anyone!
    Donate to: DrByte directly or to the Zen Cart team as a whole

    Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
    Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.

  5. #5
    Join Date
    Apr 2006
    Posts
    96
    Plugin Contributions
    0

    Default Re: Upgrading to 1.3.9h problem

    Quote Originally Posted by DrByte View Post
    Sounds like your non-admin configure.php has different DB settings than your admin configure.php file.
    "// define our database connection" is the same on both files

    Also, I did delete the install files but the admin area is telling me I need to upgrade my DB. What should I do?

  6. #6
    Join Date
    Jan 2004
    Posts
    66,364
    Blog Entries
    7
    Plugin Contributions
    274

    Default Re: Upgrading to 1.3.9h problem

    is the same on both files
    Did you check the files ON THE SERVER? Or just the copy on your PC?
    .

    Zen Cart - putting the dream of business ownership within reach of anyone!
    Donate to: DrByte directly or to the Zen Cart team as a whole

    Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
    Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.

  7. #7
    Join Date
    Apr 2006
    Posts
    96
    Plugin Contributions
    0

    Default Re: Upgrading to 1.3.9h problem

    No wonder they call you the doctor! :) You're right, for some strange reasons, that config file wasn't going through an FTP client. Had to do an upload through cPanel. I also did the "upgrade database" through zc_install. THANK YOU!
    Last edited by shqipo; 2 Dec 2011 at 06:04 AM.

  8. #8
    Join Date
    Jul 2009
    Location
    Maryland
    Posts
    65
    Plugin Contributions
    0

    Default Re: Upgrading to 1.3.9h problem

    I upgraded to 1.39h as the instruction said.

    The only thing different I did is that once I had the test store working on a new DB which was restore from original DB and upgraded, I decided to use that as my new original DB.

    I moved the test store files to the root directory including the config files that point to the new DB (making sure the config files were modified to the correct root paths). Everything seems to be working well, but when I tried to disconnect my test store from the new DB, it brings down the upgraded store as well.

    So I change the configs of the test store to point to the old DB, yet it somehow linked to the upgraded store because now on the upgraded store it give me a mesage I need to patch the DB (even though the new DB has already being upgraded).

    Does this makes sense?

    Basically I have the upgraded store working and just want to delete my test store files without affecting my upgraded store.

    Thanks,
    Last edited by JE2009; 27 Jan 2012 at 06:54 PM.

 

 

Similar Threads

  1. Problem upgrading
    By Beau91324 in forum Upgrading to 1.5.x
    Replies: 4
    Last Post: 25 Jul 2014, 01:00 AM
  2. v139d Problem Upgrading
    By kitcorsa in forum Upgrading to 1.5.x
    Replies: 10
    Last Post: 23 Aug 2013, 03:55 PM
  3. Upgrading problem from 1.3.7 to 1.3.8
    By rtfulk in forum Upgrading from 1.3.x to 1.3.9
    Replies: 1
    Last Post: 29 Oct 2009, 07:16 PM
  4. Replies: 3
    Last Post: 19 Jun 2008, 12:44 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
disjunctive-egg
Zen-Cart, Internet Selling Services, Klamath Falls, OR