ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Updating to 1.6.7 resulted in site disappearing

March 07, 2009 5:32pm

Subscribe [4]
  • #1 / Mar 07, 2009 5:32pm

    Girlyshoes

    91 posts

    I’m getting the exact same message regarding the duplicate column. Same column. I was running 1.6.2 successfully until I tried to update. Then I got as far as from 1.6.2 to 1.6.4.

    I’ve re-installed and wiped and renamed and wiped and re-installed and now I can’t even get to my control panel, because it’s not recognizing my password. I tried to reset the password, but that was a bad idea because I can’t get into the system at all.


    Mod Edit: Split from http://ellislab.com/forums/viewthread/107907/

  • #2 / Mar 07, 2009 5:42pm

    Greg Aker

    6022 posts

    Girlyshoes:

    I’m splitting your post off into it’s own thread so we can concentrate on you individually.

    So we are on the same page, you ran update.php, and then when that didn’t work, you wiped everything and reinstalled?

    Do you have a backup of your database from before the initial update try?

  • #3 / Mar 07, 2009 5:44pm

    Girlyshoes

    91 posts

    probably not. I backed up a lot of stuff first. I don’t recall a specific db backup. I only recently updated to 1.6.2, and probably had a back up at that time (it worked beautifully, that time)... I can check my cpanel and see if there’s something there.

  • #4 / Mar 07, 2009 5:47pm

    Girlyshoes

    91 posts

    I do have backup dbs for my site(s), not sure how recent.

  • #5 / Mar 07, 2009 5:51pm

    Greg Aker

    6022 posts

    Is there any way you can examine the back to see if you can figure out how old it is?

    -greg

  • #6 / Mar 07, 2009 6:21pm

    Girlyshoes

    91 posts

    No. I mean, maybe a real computer coder could, but when I downloaded it and unzipped it, it looked like it was from today at 4. Which it may be, or it may not be. I just don’t know. I upgraded my system to Mac Leopard a couple of weeks ago, and backed up everything I could lay my hands on, then. I’m going through an external hard drive now to see if there’s anything there. Oh, just shoot me. On the other hand, my host might have a backup that I could get?

    ETA: the last db back up I can find with a date is from 2007… head::desk

  • #7 / Mar 07, 2009 7:21pm

    Girlyshoes

    91 posts

    And the wonderful hosting folks have a backup of all my files from last Sunday night. Which databases(s) do I need to restore?

  • #8 / Mar 08, 2009 10:35am

    Girlyshoes

    91 posts

    It took all day and a data base restore from my site host, but I’m now upgraded to 1.6.7

    That’s the good news. The bad news is that my site no longer recognizes my log in. The page that I’m supposed to go to to reset my password displays as a blank page. In fact, every page displays as a blank page, except for the off-line page, which tells the world that I’m down. Since noon yesterday.

    And the mods quit reading/replying to my query in the update thread around 4 yesterday afternoon, so I’ve just been mucking around on intuition and instinct. I suspect a bad path, or a conflicting extension (based on other people’s problems).

    I have to go off-line from about 10 EDT to 7pm EDT. Can I get some help here?

  • #9 / Mar 08, 2009 3:26pm

    Greg Aker

    6022 posts

    Do they have a backup of your database from any time before you tried the update?

  • #10 / Mar 08, 2009 3:39pm

    Lisa Wess

    20502 posts

    Hi, Girlyshoes.  I have merged your two threads.  We are here to help but as it is a weekend, there is different coverage than you would experience on a business day.  I do ask your patience as we work through this upgrade.

    When you say:

    The bad news is that my site no longer recognizes my log in.

    Do you get an error? Does the page just reload?  A blank page?  More info on the symptoms will guide us on helping you more.

    As for the blank pages, can you create a new plain text file and call it phpinfo.php - put this code in it:

    <?php
    
    // Show all information, defaults to INFO_ALL
    phpinfo();
    
    ?>

    Now visit it in your browser and look for display_errors - let us know what that value says.

    You might also temporarily add this line to your config.php:

    $conf['allow_extensions'] = "n";

    to see if that will allow you access; it rules out an extension being the issue.

  • #11 / Mar 08, 2009 11:05pm

    Girlyshoes

    91 posts

    I added the allow extensions line to my config file with no results. And for what ever reason, after booting up to 1.6.7 this morning, I am now seeing the 1.6.2 build on my log-in page tonight. Which still won’t log me in.

  • #12 / Mar 08, 2009 11:35pm

    Lisa Wess

    20502 posts

    If you open up /system/config.php, can you let us know what app_version says?

  • #13 / Mar 08, 2009 11:45pm

    Girlyshoes

    91 posts

    It was showing 162, and I edited it to 167, which now shows up in the log on page. Which still just resets itself when I put in my password. And I added the ext/no line to the config file, with no visible results.

  • #14 / Mar 09, 2009 4:19am

    John Henry Donovan

    12339 posts

    Girlyshoes,

    Open your config.php and add the line

    $conf['cookie_domain'] = "";

    The try to login to CP

    Also can you follow up on the info Lisa was asking for from your phpinfo.php

    Now visit it in your browser and look for display_errors - let us know what that value says.

  • #15 / Mar 09, 2009 10:50am

    Girlyshoes

    91 posts

    I’m at work, behind a firewall and with a watchful boss who (go figure) won’t let me work on my personal sites from here. I can tell you that the phpinfo.php file didn’t do anything. It didn’t display anything.

    And the tech support at HostGator say this:

    Thank you for contacting HostGator.

    For the index.php file on the girlyshoes.com/Girlyblog/ if you are trying to use that it is looking for a file that is not there.

    require ‘./core/core.system’.$ext;

    The index.html file is the one that is saying.

    This site will be offline momentarily while we perform some updates.
    We apologize for any inconvenience.

    As for the login there ia also a file it is looking for that is not there.

    No such file or directory in /home/mizshoes/public_html/HAL/DAVE/extensions/ext.tag_submit.php on line 33

    Had you removed these files by chance?


    I don’t think I removed those….

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases