All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

Database Error with 1.2.1 to 2.0.2 upgrade

Damien 18 Jun 2012 04:37 problem, complete

Have followed the instructions to upgrade but twice now (after having restored EE installation from a backup once) I'm getting this error when I try to upgrade. I'm using EE 2.4.0

If I go back to CP home and then try the modules add-on page again, I get this:-



What do I do now?

Replies

  1. Low 18 Jun 2012 06:54

    That's rather strange. Can you give me access to your CP? You can send superadmin login credentials to hi at gotolow dot com.

  2. Damien 18 Jun 2012 09:02

    Sure. Sent you an email. Let me know if you's like FTP access too.

  3. Low 18 Jun 2012 11:21

    Turned out the server in question had MySQL version 4.1 installed, which doesn't support the WHERE clause in a SHOW COLUMNS query.

    I've worked around it on the server and performed a successful upgrade afterwards.

  4. Damien 21 Jun 2012 06:01

    I think you may have a problem with the upgrade process where more than one set is upgraded from using the same custom field short_name, or my upgrade was botched.

    Before the upgrade I had 6x reorder sets. Now I have 3.

    I had a 'News' fieldset with 'article_display_order' and was using this across three channels - Customers, Suppliers and News. I now only have a set for Customers...

    I had another two sets using 'location_display_order' - Contact and Location. The upgrade only created Location.

    The last set had a unique custom field short_name and is ok.

    Luckily I've been able to set them up again by referring to my backup install sets.

  5. Low 21 Jun 2012 08:10

    LR1 looked at channel + field combos. Each combo was listed on the module page, and for each combo, you could edit settings and reorder the entries. However, it could easily be the case that some combos were irrelevant, especially if you're re-using field groups with different channels. Those combos would be listed, but not have settings saved to the DB.

    When upgrading to LR2, all existing settings would be read and migrated to Sets. Combos without settings would be skipped. This is intended behavior, but I understand that it could be confusing.

    I think I need to add some sort of message to the upgrade process to make sure that all relevant combos have settings saved at least once before upgrading.

    Is everything working okay now, or do you need some more help with the add-on?

  6. Damien 21 Jun 2012 08:28

    I think I've got it under control now, thanks.