Upgrade to v1.0.x from ancient beta0.7.x

rolandash

Hi,

I am performing a radical upgrade from beta0.7.x, to latest v1.0.x;
I have backup of old databases, and the 0.7.x flarum folder; and i would like to restore these old posts into the new database;

So far i have installed a fresh new flarum 1.0. Then I tried to import from the dumped old databases (.sql), but the result is a failure, and the new database is still empty. Seems the new databases in v1.0 has more columns than previous version.

So what should i do to resolve this problem? Can it be achieved?

Thank you!
/Roland

luceos

rolandash install 1.0, drop the database, uninstall all extensions (even core ones), import your database, run php flarum migrate, a forum should now show up again. Install extensions you need one by one by checking their compatiblity first (http://extiverse.com).

rolandash

thank you luceos

I executed following steps after a fresh installation of v1.0.4

mysql> source db_dump.sql; this drops newly created database, and import my old database from previous dump file;

then do a migrate and i got following errors:

php flarum migrate
Migrating Flarum...
Migrated: 2018_01_11_093900_change_access_tokens_columns
Migrated: 2018_01_11_094000_change_access_tokens_add_foreign_keys
Migrated: 2018_01_11_095000_change_api_keys_columns
Migrated: 2018_01_11_101800_rename_auth_tokens_to_registration_tokens
Migrated: 2018_01_11_102000_change_registration_tokens_rename_id_to_token
Migrated: 2018_01_11_102100_change_registration_tokens_created_at_to_datetime
Migrated: 2018_01_11_120604_change_posts_table_to_innodb
Migrated: 2018_01_11_155200_change_discussions_rename_columns
Migrated: 2018_01_11_155300_change_discussions_add_foreign_keys
Migrated: 2018_01_15_071700_rename_users_discussions_to_discussion_user
Migrated: 2018_01_15_071800_change_discussion_user_rename_columns
Migrated: 2018_01_15_071900_change_discussion_user_add_foreign_keys
Migrated: 2018_01_15_072600_change_email_tokens_rename_id_to_token
Migrated: 2018_01_15_072700_change_email_tokens_add_foreign_keys
Migrated: 2018_01_15_072800_change_email_tokens_created_at_to_datetime
Migrated: 2018_01_18_130400_rename_permissions_to_group_permission
Migrated: 2018_01_18_130500_change_group_permission_add_foreign_keys
Migrated: 2018_01_18_130600_rename_users_groups_to_group_user
Migrated: 2018_01_18_130700_change_group_user_add_foreign_keys
Migrated: 2018_01_18_133000_change_notifications_columns
Migrated: 2018_01_18_133100_change_notifications_add_foreign_keys
Migrated: 2018_01_18_134400_change_password_tokens_rename_id_to_token
Migrated: 2018_01_18_134500_change_password_tokens_add_foreign_keys
Migrated: 2018_01_18_134600_change_password_tokens_created_at_to_datetime
Migrated: 2018_01_18_135000_change_posts_rename_columns
Migrated: 2018_01_18_135100_change_posts_add_foreign_keys
Migrated: 2018_01_30_112238_add_fulltext_index_to_discussions_title
Migrated: 2018_01_30_220100_create_post_user_table
Migrated: 2018_01_30_222900_change_users_rename_columns
Migrated: 2018_07_21_000000_seed_default_groups
Migrated: 2018_07_21_000100_seed_default_group_permissions
Migrated: 2018_09_15_041340_add_users_indicies
Migrated: 2018_09_15_041828_add_discussions_indicies
Migrated: 2018_09_15_043337_add_notifications_indices
Migrated: 2018_09_15_043621_add_posts_indices
Migrated: 2018_09_22_004100_change_registration_tokens_columns
Migrated: 2018_09_22_004200_create_login_providers_table
Migrated: 2018_10_08_144700_add_shim_prefix_to_group_icons
Migrated: 2019_10_12_195349_change_posts_add_discussion_foreign_key
Migrated: 2020_03_19_134512_change_discussions_default_comment_count
Migrated: 2020_04_21_130500_change_permission_groups_add_is_hidden
Migrated: 2021_03_02_040000_change_access_tokens_add_type
Migrated: 2021_03_02_040500_change_access_tokens_add_id
Migrated: 2021_03_02_041000_change_access_tokens_add_title_ip_agent
Migrated: 2021_04_18_040500_change_migrations_add_id_primary_key
Migrated: 2021_04_18_145100_change_posts_content_column_to_mediumtext

In Connection.php line 703:
                                                                                                             
  SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2-viewForum' for key 'dronetag_gro  
  up_permission.PRIMARY' (SQL: update `dronetag_group_permission` set `permission` = REPLACE(permission,  '  
  viewDiscussions', 'viewForum') where `permission` LIKE %viewDiscussions)                                   
                                                                                                             

In Exception.php line 18:
                                                                                                             
  SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2-viewForum' for key 'dronetag_gro  
  up_permission.PRIMARY'                                                                                     
                                                                                                             

In PDOStatement.php line 117:
                                                                                                             
  SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2-viewForum' for key 'dronetag_gro  
  up_permission.PRIMARY'                                                                                     
                                                                                                             

migrate

How should i handle these errors?

rolandash

and this is what i currently have in table 'dronetag_group_permission' after import from old DB

select * from dronetag_group_permission;
+----------+---------------------------------+
| group_id | permission                      |
+----------+---------------------------------+
|        2 | viewDiscussions                 |
|        2 | viewForum                       |
|        3 | discussion.flagPosts            |
|        3 | discussion.likePosts            |
|        3 | discussion.reply                |
|        3 | discussion.replyWithoutApproval |
|        3 | discussion.startWithoutApproval |
|        3 | flagrow.upload                  |
|        3 | searchUsers                     |
|        3 | startDiscussion                 |
|        3 | viewUserList                    |
|        4 | discussion.approvePosts         |
|        4 | discussion.editPosts            |
|        4 | discussion.hide                 |
|        4 | discussion.hidePosts            |
|        4 | discussion.lock                 |
|        4 | discussion.rename               |
|        4 | discussion.sticky               |
|        4 | discussion.tag                  |
|        4 | discussion.viewFlags            |
|        4 | discussion.viewIpsPosts         |
|        4 | user.suspend                    |
|        4 | user.viewLastSeenAt             |
+----------+---------------------------------+
23 rows in set (0.00 sec)

SychO

rolandash Looks like it's a bug with upgrading from older betas, the only way you can fix this right now is by manually running in mysql:

delete from dronetag_group_permission where permission in ('viewDiscussions', 'viewUserList');

and then rerunning the migrations.

rolandash

That fixed it.

The forum shows up now.

Thank you SychO for the hint!

giulio

I came here to post this same issue and the solution. Given how it's all there already, let me just reiterate that this is still active and should probably be fixed. I was upgrading from ancient 0.1.0-beta.6. to 1.0.0 at last!