krileon wrote: You're lucky it wasn't months (like ours). It's a migration. There's nothing easy about it. Checklists like that are site by site based. CB 1.x with all plugins to CB 2.x with all plugins will migrate fine. For example you had CB Facebook Connect and CB Twitter Connect installed at some point which created those fields. Installing CB Connect would've restored them after you had migrated CB 1.x to CB 2.x. You're not doing a 1:1 migration if you're not installing old plugins you already had. Deleting the plugin does not delete its fields to avoid data loss so your issue isn't a symptom of migration.
I know it's frustrating and time consuming, but it's just the nature of the beast. Joomla 1.5 to 3.x wasn't very fun for us lol.
krileon wrote: It's not an upgrade. It's a migration and I can assure you our migration is far less painful than Joomla 1.x to 3.x for example. Each major release of CB (e.g. CB 3.0, 4.0, etc..) are classified as migrations as it's when we do large, possibly breaking, changes. CB is free and we're not forcing anyone to do such migrations, but we need to move forward and moving forward means improving and getting rid of old code. CB 3.0 should be a smoother migration compared to 1.x to 2.x.
krileon wrote: We've no idea what all issues can happen due to a migration. All our migration tests are with simple clear installs with all our products installed. All such tests pass fine. We can't account for every server configuration, every install configuration, etc.. No migration is simple. We had troubles of our own doing ours, but that's just the nature of migrations. Good news is we've gone to great lengths to improve our API usages so hopefully this can't really happen again going forward (e.g. 2.x to 3.x again is a migration.. all majors will be considered migration).
Please Log in or Create an account to join the conversation.