I just ran update.php after replacing 6.x-2.0-alpha3 with 6.x-3.0-beta1. Is there a simple answer and workaround to these errors I received?
panels module
Update #5204
* <strong>Failed</strong>: ALTER TABLE {panels_page} ADD COLUMN name varchar(255) UNIQUE
* ALTER TABLE {panels_display} ADD COLUMN name varchar(255) UNIQUE
* <strong>Failed</strong>: UPDATE {panels_page} SET name = CONCAT('panel_page_', pid)
* UPDATE {panels_display} SET name = CONCAT('display_', did)
Update #5205
* <strong>Failed</strong>: ALTER TABLE {panels_page} ADD COLUMN arguments longtext
Update #5206
* <strong>Failed</strong>: ALTER TABLE {panels_pane} ADD COLUMN subtype varchar(64)
Update #5207
* <strong>Failed</strong>: ALTER TABLE {panels_page} ADD COLUMN displays longtext
* <strong>Failed</strong>: ALTER TABLE {panels_page} ADD COLUMN contexts longtext
Update #5208
* <strong>Failed</strong>: DELETE FROM {sequences} WHERE name = '{panels_display}_did'
* <strong>Failed</strong>: DELETE FROM {sequences} WHERE name = '{panels_display}_id'
* <strong>Failed</strong>: INSERT INTO {sequences} (name, id) VALUES ('{panels_display}_did', 4)
Update #5209
* <strong>Failed</strong>: ALTER TABLE {panels_page} ADD COLUMN relationships longtext
Update #5210
* UPDATE {system} SET weight = 10 WHERE name = 'panels'
Update #5211
* No queries
Update #5213
* <strong>Failed</strong>: ALTER TABLE {panels_pane} ADD COLUMN cache longtext AFTER configuration
* <strong>Failed</strong>: ALTER TABLE {panels_display} ADD COLUMN cache longtext AFTER panel_settings
Update #5214
* <strong>Failed</strong>: CREATE TABLE {panels_object_cache} ( sid varchar(64), did integer, obj varchar(255), timestamp integer, data text, KEY (sid, obj, did), KEY (timestamp) ) /*!40100 DEFAULT CHARACTER SET utf8 */
Update #5215
* <strong>Failed</strong>: ALTER TABLE {panels_pane} ADD PRIMARY KEY (pid)
Update #5216
* <strong>Failed</strong>: ALTER TABLE {panels_pane} ADD COLUMN shown int(1) DEFAULT 1 AFTER subtype
* <strong>Failed</strong>: ALTER TABLE {panels_display} ADD COLUMN title varchar(128) AFTER cache
* <strong>Failed</strong>: ALTER TABLE {panels_display} ADD COLUMN hide_title int(1) AFTER title
* ALTER TABLE {panels_display} DROP COLUMN name
* <strong>Failed</strong>: ALTER TABLE {panels_pane} ADD COLUMN visibility text AFTER access
Update #5217
* <strong>Failed</strong>: ALTER TABLE {panels_page} ADD COLUMN switcher_type varchar(128) AFTER no_blocks
* <strong>Failed</strong>: ALTER TABLE {panels_page} ADD COLUMN switcher_name varchar(128) AFTER no_blocks
* <strong>Failed</strong>: ALTER TABLE {panels_page} ADD COLUMN switcher_options longtext AFTER switcher_type
Update #5218
* Update #5218 only has changes for PostgreSQL. There are no updates for MySQL databases - since you're running MySQL, you should consider this update successful.
Update #5219
* You are strongly encouraged to re-export any panels generated with a version of Panels prior to Release Candidate 2, as several fields were (incorrectly) being ommitted from all exports, and this updater is unable to update any panels already exported with missing fields.
Update #5299
* DELETE FROM {panels_pane} WHERE pid = 0
* <strong>Failed</strong>: ALTER TABLE {panels_pane} DROP PRIMARY KEY
* <strong>Failed</strong>: ALTER TABLE {panels_pane} CHANGE pid `pid` INT NOT NULL auto_increment, ADD PRIMARY KEY (pid)
* <strong>Failed</strong>: ALTER TABLE {panels_display} DROP PRIMARY KEY
* <strong>Failed</strong>: ALTER TABLE {panels_display} CHANGE did `did` INT NOT NULL auto_increment, ADD PRIMARY KEY (did)
Comments
Comment #1
merlinofchaos commentedClearly I need to cut some useless stuff out of the upgrade path. These errors appear to be harmless. I don't think they'll impact thefunctionality of the module in any way.
Comment #2
Daniel Norton commentedWell, the upgrade totally destroyed my database, the panels displays were all screwy and nothing worked at all.
I'm back on Panels 2, which seems much more stable.
Comment #3
merlinofchaos commentedBy the way, I'd like to quote from the release notes:
I bring this up because the tone of the title you picked irritates me, when I was very up front that this release could be buggy and cause data problems.
Re-reading this, I'm not sure how some of these could have failed if you actually have a working site with panels 2. This is partly because you didn't include the actual error messages, so I only know that the queries failed but not why. If you could paste that information it might be helpful in getting this fixed.
Another piece of information that could be helpful is looking in your 'system' table and telling me what the schema_version for the 'panels' module is, plus telling me exactly what version of Panels 2 you have installed that it is being updated from.
Comment #4
kwixson commentedTrying out the upgrade path from Panels 2 alpha 3 to Panels 3 beta 1. I'm on a fresh MAMP install on the local machine, the most recent versions of everything. The available updates page is a field of green. I only have the modules installed necessary for this test (panels, views, etc.), plus CCK, filefield, imagefield, imageapi, imagecache because I'm testing to make sure Panels 3 handles node context content with image fields properly, which 2 does not. Before executing the upgrade I enable CTools, Delegator, Views content panes just in case.
Upgrade fails.
An error occurred. http://localhost:8888/update.php?id=2&op=do
Fatal error: Call to undefined function panels_get_relationship() in /Users/kwixson/Sites/default/sites/all/modules/panels/panels.install on line 287
Complete error report attached. Please advise.
Comment #5
devinhedge commentedSame exact errors and effect here. It totally hosed my database. I'm glad I backed up the database before trying out 3.0 Beta1 even if it was my staging server. I'd call this one critical since it kills Drupal's ability to function.
#UPDATE: Just wanted to apologize for not having any errors or screenshots. It was late. I was in a hurry to make my weekly upgrades. I'm willing to try again if you still need more information.