Summary: | Errors with upgrade from 3.00.00.070 to 3.14.02.000 | ||
---|---|---|---|
Product: | Koha | Reporter: | David White <dswhite42> |
Component: | Installation and upgrade (web-based installer) | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | gmcharlt, indradg, liz |
Version: | 3.14 | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
David White
2014-01-28 06:06:32 UTC
I'll just add my own workarounds to these: * Convert everything to InnoDB prior to running the upgrade script. * Of these ALTER TABLE DROP FOREIGN KEY errors, the only one that seems to actually generate a red warning message is the patronimage one. I solved this by pre-creating the "patronimage" table with the patronimage_fk1 foreign key, so the script can happily drop it * Rewrote the /optional/ pathnames to /mandatory/ * Altered the sample_notices_message_transports.sql to delete these lines: (4, 'email', 0, 'reserves', 'HOLD') (4, 'sms', 0, 'reserves', 'HOLD') (5, 'email', 0, 'circulation', 'CHECKIN') (5, 'sms', 0, 'circulation', 'CHECKIN') (6, 'email', 0, 'circulation', 'CHECKOUT') (6, 'sms', 0, 'circulation', 'CHECKOUT') These will allow the script to run at the right time, and the 6 lines above will be created later by updatedatabase.pl later in the script anyway (when the appropriate entries in the 'letters' table have also been created). Sorry, one other bug: * When attempting to run "misc/maintenance/remove_items_from_biblioitems.pl", a number of SQL statements fail because C4/Biblio.pm tries to update columns that don't exist in 3.00.00.070 . Specifically, any attempt to "UPDATE biblioitems" that refers to the "ean" and "agerestriction" column fails. * workaround: temporarily remove references to those columns in C4/Biblio.pm, and restore them after "remove_items_from_biblioitems.pl" has completed. Probably we'll keep this around (and open) for posterity, but I suspect that we won't be fixing these issues. Thanks for adding your workarounds, they will probably help someone else someday! I think 3.14 is old enough now that this report doesn't need to stay open. |