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.

upgrade from 1.7 to 2.7 failing at step 'archiving templates'

November 15, 2013 4:49pm

Subscribe [1]
  • #1 / Nov 15, 2013 4:49pm

    ABDC

    71 posts

    I am trying to upgrade a site from 1.7 to 2.7. Because it is a complex multisite installation, has a lot of extensions and uses the image gallery module a lot, I decided to copy the complete installation to a subdirectory and upgrade that first. I figured I needed to do too many template and site changes to be able to upgrade the live site immediately. I had the copy running good on a subdomain, then I tried to upgrade. Now the upgraded stops at the following error:

    An Error Was Encountered
    There was an error moving your existing template files to an archive folder. Please manually move any folders in the form system/expressionengine/templates/<site_short_name>/ to a backup location and then Resume the Update.

    Nothing will make it continue. I can see it has something to do with the multisite module? But what and how do I get further with the upgrade now?

    Many thanks in advance for any insights / pointers… 

  • #2 / Nov 16, 2013 5:41pm

    ABDC

    71 posts

    Since this is the weekend and the site is not active then I decided to try my luck on the original root installed site. This worked! So the problem probably arose from moving the install.

    Now I encountered the corrupted site preferences in database error outlined in several threads, for example here: http://ellislab.com/forums/viewthread/222948/P15

    I solved it by converting the contents of the exp_sites preferences table to 64base, so almost the instructions as provided but slightly different:

    1) Copy the contents of the site_system_preferences column from the exp_sites table.
    2) Paste here [http://blog.tanist.co.uk/files/unserialize/index.php], do NOT check “base64 decode”, and click “Unserialize!”
    3) Scroll down to the bottom of the resulting page to re-serialize it, DO check “base64 encode”, and click “Re-serialize!”
    4) Copy the results, and paste them into the field they came from in the exp_sites table.
    5) repeat for all preferences columns
    6) in cases of MSM: repeat for all sites.

    The ‘site_pages’ column uses a slightly other format than the others which the tanist tool would not reserialize. I used http://www.base64encode.org to reserialize these. I do not yet know if this was successful as I have not managed to enter the CP, but the installer has moved on to another error.

    I now have the following error:

    A Database Error Occurred
    Error Number: 1054
    Unknown column ‘has_publish_fields’ in ‘field list’
    UPDATE `exp_modules` SET `has_publish_fields` = ‘y’ WHERE `module_name` = ‘Pages’
    Filename: <serverpath>/expressionengine/modules/pages/upd.pages.php
    Line Number: 147

    So I am investigating that now.

     

  • #3 / Nov 17, 2013 5:17pm

    ABDC

    71 posts

    Searching for the error “Unknown column ‘has_publish_fields’ in ‘field list’ UPDATE `exp_modules` SET `has_publish_fields` = ‘y’ WHERE `module_name` = ‘Pages’” does not throw up any help from the EE forums. Checking the indicated PHP file I see:

    if (version_compare($current, '2.1', '<'))
      {
       ee()->db->where('module_name', 'Pages');
       ee()->db->update('modules', array('has_publish_fields' => 'y'));
      }
      
      if (version_compare($current, '2.2', '<'))
      {
       $this->_do_22_update();
      }

    Where does the installer get his version nr from? If I check the config it says version 271; why would this file try to update anyway?

    I actually do not use the pages module; just have it installed. Could I just comment out this function? Or somehow uninstall the pages module without access to the control-panel?

    I feel like I am now in update limbo with only access to the database via phpmyadmin and access to the actual installed files, but not to the control panel of front-end of the website.

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

ExpressionEngine News!

#eecms, #events, #releases