Thread

Hi,

Just want to verify something…

I was looking through the SCM data, post conversion from 1.6.8 to EE2 yesterday (to build 20101220), and got a fatal error, similar to this one.  The three new fields were missing from the exp_simple_commerce_items table.  No errors were detected when the upgrade to EE2 was done, so I thought all was well.

The problem described in the post above made it clear that the SCM wasn’t updated for some reason, so…
1. Backed-up the 3 SCM tables
2. Uninstalled the SCM module
3. Installed it
4. Then did a side by side comparison to see which fields were missing (they were customer_email_template_unsubscribe, current_subscriptions, and member_group_unsubscribe). 
5. I then restored my back-up of those 3 tables and added the 3 missing fields to the items table.

Everything seems fine now.  I can edit items in the CP without fatal errors, but I just want to run this by you guys to see if there is something else that should be checked.

Would there be an issue in the future, with the tables not having the fields in the same order?  Are there any other behind the scenes hooks that may have been missed by my recovering from this in this way?

Would there be an issue in the future, with the tables not having the fields in the same order?  Are there any other behind the scenes hooks that may have been missed by my recovering from this in this way?

If it’s working as expected now I wouldn’t worry about it. The field order shouldn’t matter, just the name, and the only changes made are to the database: whether you do them automatically or manually doesn’t matter at the end of the day.

Thanks, Ingmar.  I’ll stop worrying about that one now! :ahhh:

Excellent 😊 Please post again as needed.