Error processing a database query after upgrading from 1.2.2 to 1.3.2

[Ssurgul]

I was working just fine and dandy earlier today.  All images working, all thumbnails working, and more.  Life was blissful.  Then I decided to upgrade, and life ceased to be blissful.

After running through the upgrade steps (copying all files needed, while not overwriting the key files, creating the 'edit' directory in albums, and then running the update.php), I suddenly got this:

Fatal error :

There was an error while processing a database query.

After searching for quite some time and finding out how to do manual repairs to the tables (phpMyAdmin repeatedly reported problems creating the temporary tables to run the repair), and then finding out how to set the debug mode to on when that didn't resolve the problem, I came up with this:

While executing query "SELECT extension, mime, content FROM cpg11d_filetypes;" on 0

mySQL error: Table 'cpg.cpg11d_filetypes' doesn't exist

On checking my backups for the database and such, I find that I never had a 'filetypes' table created.  What info/fields do I need to populate one with to get the system back online?  Should I simply downgrade again and get myself out of this problem the less useful way?  And why wasn't this table created back in the 1.2 days or why is it needed now?

Thanks for any help on this.

Marcus

[krkeegan]

you sure you ran update.php and everything said it was fine?

Update.php should have added that table for you. I suggest checking two things. Make sure you coppermine/sql directory contains three files.
Basic
Schema
Update

Then run update.php again and let us know what the line refering to creating cpgXXX_filetypes table says. It should be an OK in green.

Kevin

[Ssurgul]

Well, when I did it the first time, it was the same result as the second time:  the tool came back on the window with an 'Already Done' message, so I figured it was fine.

However, when I pasted the SQL query into the window for phpMyAdmin directly, then I found that there was a creation error for the .frm itself.  Seems that 'Already Done' might be a bad return message if there are errors in processing.

I ended up resetting the permissions on the directory (since everything else was configured fine) and this time when I ran the update, it did give me the green 'OK' down the list on almost all of it, and when I clicked 'Continue' this time, it came back with no problems at all.

Thanks for the highlight help; it did actually help me track down the cause.  I would suggest, though, that the script be modified slightly to kick up error messages, rather than 'Already Done' for future issues of this type.