Jump to content

Jordan Sharples

Members
  • Posts

    13
  • Joined

  • Last visited

Recent Profile Visitors

211 profile views

Jordan Sharples's Achievements

  1. Progress: Site has been updated: manually applied the update despite the update process saying the database needed to be fixed after having manually applied all the sql fixes
  2. Jim M.: That appears to have done the trick!! Thank you.
  3. How do I do that? The "Upgrade Invision Community" screen shows the tabs for upgrade progress but I can't get past step 1.
  4. I can't upgrade!?!? I've updated all the tables to INNODB all tables and columns now are utf8mb4_unicode_ci (they were already) I've manually ran the huge list of sql queries that the update process recommends (ran it in batches of 20 - 30 lines at a time, noting any errors, most frequently: Warning: #3719 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. Warning: #3778 'utf8mb3_unicode_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead. I've also run the database fixes using the "Fix Automatically" button I click on "Check Again" and it returns the same 764 line sql query list as before!!! The forum is still running . . . so at least the update process hasn't borked like before but I can't progress beyond: "There are some problems with your database which need to be fixed before you can start the upgrade.
  5. I’ve not yet heard back from my host about this, but found this might point to a solution. http://stackoverflow.com/questions/2428738/ddg#4075770
  6. I’ve got a support ticket in with my service provider, I’ll post if I get a solution.
  7. In the process of updating our forum software, I applied the recommended database ‘fix’ of 764 sql queries. It trashed my database. A backup of the database got my site back running. One of the problematic queries was, after creating a new table, altering it: CREATE TABLE `core_modules_new` LIKE `core_modules`; result: created new table ALTER TABLE `core_modules_new` CHANGE COLUMN `sys_module_title` `sys_module_title` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '' , DROP INDEX `identifier`, DROP INDEX `sys_module_application`, CHANGE COLUMN `sys_module_application` `sys_module_application` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '' , ADD UNIQUE KEY `identifier` (`sys_module_application`,`sys_module_key`,`sys_module_area`), ADD KEY `sys_module_application` (`sys_module_application`), DROP INDEX `sys_module_key`, CHANGE COLUMN `sys_module_key` `sys_module_key` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '' , ADD KEY `sys_module_key` (`sys_module_key`), CHANGE COLUMN `sys_module_area` `sys_module_area` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NULL DEFAULT 'front' , CHANGE COLUMN `sys_module_default_controller` `sys_module_default_controller` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NULL ; the result was an un repairable table: #1034 - Incorrect key file for table 'core_modules_new'; try to repair it what gives?
  8. Short version: can’t upgrade, suggested database fixes results in corrupted tables. Details above.
  9. OK! So now my site database has been restored, and the forums are working. https://forums.wscc.mb.ca/ I still need to update the software but approach it with caution. So I downloaded a working version of the database. I initiate the update and it tells me there are problems with the database that need to be fixed. The query list is HUGE! 764 lines of sql queries!!!!! I try some of them manually: UPDATE `core_modules` SET `sys_module_title`='' WHERE `sys_module_title` IS NULL; result: nothing UPDATE `core_modules` SET `sys_module_application`='' WHERE `sys_module_application` IS NULL; result: nothing UPDATE `core_modules` SET `sys_module_key`='' WHERE `sys_module_key` IS NULL; result: nothing CREATE TABLE `core_modules_new` LIKE `core_modules`; result: created new table ALTER TABLE `core_modules_new` CHANGE COLUMN `sys_module_title` `sys_module_title` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '' , DROP INDEX `identifier`, DROP INDEX `sys_module_application`, CHANGE COLUMN `sys_module_application` `sys_module_application` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '' , ADD UNIQUE KEY `identifier` (`sys_module_application`,`sys_module_key`,`sys_module_area`), ADD KEY `sys_module_application` (`sys_module_application`), DROP INDEX `sys_module_key`, CHANGE COLUMN `sys_module_key` `sys_module_key` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL DEFAULT '' , ADD KEY `sys_module_key` (`sys_module_key`), CHANGE COLUMN `sys_module_area` `sys_module_area` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NULL DEFAULT 'front' , CHANGE COLUMN `sys_module_default_controller` `sys_module_default_controller` VARCHAR (32) CHARACTER SET utf8 COLLATE utf8_unicode_ci NULL ; result: the table 'core_modules_new' is now trashed: #1034 - Incorrect key file for table 'core_modules_new'; try to repair it it's not repairable The next steps were to drop the original table 'core_modules_new' and to change the name of the new table to that of the old one . . . obviously I didn't do that. So now I know why my system got borked . . . but I don't know what to do about it! fix-queries.sql
  10. I'll get my host to fix this. phpmyadmin only reports that the table is corrupt and won't fix it.
  11. Thank you Randy! I've already looked at the table in question (and others) using phpMyAdmin, and it confirms that I've got corruptions . . . evidently in more than one table. But I don't know where to start to repair.
  12. I tried to upgrade the site: https://forums.wscc.mb.ca. It said there were a lot of database errors that needed fixing . . . so I clicked "fix" and very shortly the site would only display: An error occurred (500 Error) We're sorry, but a temporary technical error has occurred which means we cannot display this site right now. Incorrect key file for table 'core_sys_lang_words'; try to repair it You can try again by clicking the button below, or try again later. Try again The "Try again" is not an active link, I'm at a loss of where to start. Can you help?
×
×
  • Create New...