HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Search
-
Re: Migration issues going from 2.0.14 (!) to 3.3
-
Re: Migration issues going from 2.0.14 (!) to 3.3
I am importing data from SMF 2.0.18 version and when I attempt to import in Vanilla, I get following error: There was an error while trying to create the Media table (The specified data type (smallint unsigned) is not accepted for the MySQL database.). How can I fix it? Importing data is stopped at "Define Tables" steps.… -
Re: Migration issues going from 2.0.14 (!) to 3.3
Update succeeded! You pointed me in the right direction. Before running update I dropped all the 'legacy' columns in the Permission table. I determined what the legacy columns were by comparing them to a 'Vanilla' 3.3 install. The 3.3 forum has all the content and seems to work fine! I could not run structure as the admin… -
Re: Migration issues going from 2.0.14 (!) to 3.3
Hi R_J, thanks for answering. OK, I've just installed 3.3 and pointed the config at the old database. Unfortunately the same error occurs: Fatal Error in Gdn_MySQLStructure._defineColumn(); The specified data type (int unsigned) is not accepted for the MySQL database. The error occurred on or near:… -
Re: Migration issues going from 2.0.14 (!) to 3.3
Hi RJ, Thanks! In the time begin I've increased time out settings on Apache and was able to see what goes wrong with the first update try. Before I could not see it because of the 504 error that was returned by Apache. The unsigned int error is shown when I try for a second time. It tells something else, maybe an…
5 results