Getting the following errors when trying to update:
The following updates returned messages
metatag_opengraph module
Update #7103
Failed: PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'revision_id' in 'field list': SELECT entity_type, entity_id, revision_id, language, data FROM {metatag} WHERE data LIKE '%og:video%'; Array ( ) in metatag_opengraph_update_7103() (line 71 of .../sites/all/modules/metatag/metatag_opengraph/metatag_opengraph.install).
metatag_twitter_cards module
Update #7100
Failed: PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'revision_id' in 'field list': SELECT entity_type, entity_id, revision_id, language, data FROM {metatag} WHERE data LIKE '%twitter:image:src%'; Array ( ) in metatag_twitter_cards_update_7100() (line 18 of .../sites/all/modules/metatag/metatag_twitter_cards/metatag_twitter_cards.install).
Does anyone have any suggestions? I have done a decent amount of searching with no luck. Trying to upgrade from 7.x-1.0-beta7 to 7.x-1.8. Is there a specific upgrade path I need to take?
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | metatag-n2654530-11.patch | 1.37 KB | damienmckenna |
Comments
Comment #2
damienmckennaOh. Did the updates for the main Metatag module run first? I might have to make the submodule updates wait until the main module's have finished.
Comment #3
deja711 commentedAdenn, I got similar issue. I am upgrading from 7.x-1.7 to 7.x-1.8, and got this:
My memory limit was set to 192M:
cat /etc/php5/apache2/php.ini | grep memory_limit
memory_limit = 192M
Then I have increased memory to 256M:
cat /etc/php5/apache2/php.ini | grep memory_limit
memory_limit = 256M
And that appeared it was not enough, although i think upgrade got further:
At this point new release 7.x-1.9 came out, and I have tried that
release with increasing memory limit to 512M:
And got this:
Comment #4
deja711 commentedDamien, we posted in the same time. Good point, this is what I got for upgrade list:
metatag module
7039 - Reload some meta tag caches.
7040 - Fix robots meta tags that might have been broken when they were imported from Nodewords.
7041 - Rerun update 7018 that was fixed to run correctly when using Entity Translation. This may take some time.
7100 - Delete a deprecated variable and clear all Metatag caches.
7101 - Update i18n strings for all meta tags to use the new format.
metatag_opengraph module
7103 - Change og:video to og:video:url in all metatags.
7104 - Rename the 'og:video' meta tag to 'og:video:url' in the configs.
7105 - Clear the Metatag cache to pick up changes to og:video.
7106 - Clear the Metatag cache to pick up changes to og:audio:secure_url.
Comment #5
damienmckennaFYI the revision_id value was added in 1.0-beta8, so I guess it would be possible for the submodules to run before the field was added in metatag_update_7015. I'll work on that.
As for running out of memory, it may be worthwhile adding something to your settings.php file to bump the memory limit when the site is in maintenance mode (i.e. updates are being ran). For the max_allowed_packet error, check these docs: https://www.drupal.org/node/379976
Comment #6
deja711 commentedNo problem, for debugging this issue, I have increased memory limit temporary to 256MB. By changing PHP memory limit via /etc/php5/apache2/php.ini and setting
memory_limit = 256M
Actually I have tried 512M as well, which is over kill, but what the hell, wanted to try.
Note that was the case with version 1.8. With version 1.9 i got different error.
Checking stuff for max_allowed_packet size now
Comment #7
deja711 commentedOK i have max_allowed_packet set to 16M which happen to be the same as in https://www.drupal.org/node/379976. I'll try 32M next.
Do you have any requirement or suggestion what max_allowed_packet should be?
Comment #8
damienmckenna@deja711: I think I usually set max_allowed_packet a little larger than 16m so that a 16mb chunk (the max for a large text field) can be set in one query. However, I suspect a problem happened before that query failed.
Comment #9
damienmckennaComment #10
damienmckennaComment #11
damienmckennaThis makes Twitter Cards update 7100 and OpenGraph update 7103 wait until Metatag update 7100 has finished, which should cover our needs.
Comment #12
damienmckennaComment #13
damienmckennaCommitted. Sorry about the problems updating.
Comment #15
deja711 commentedDamien, thank you again for sanity check. I will try and test this, and will post results regardless of outcome.
Comment #16
Adenn commentedI tried the .10 release with the same issue. I went in an manually added the column in the table for revision_id, per the settings in the install script, and then the update went through without any issues. I know this isn't the best practice but it worked. I am not sure why the install script doesn't check for the column and create it if it isn't there, I haven't dug into the script that much to find out.
Comment #17
damienmckenna@Adenn: The update script shouldn't have to check if the column exists because the column should have been added by metatag_update_7015.. gah.
Comment #18
deja711 commentedDamien, I tried version 10 release and works with php memory_limit = 320MB & mysql max_allowed_packet = 32MB. Anything below that (for both) fails for me. This is one heavy update you got there. :)
Comment #19
damienmckennaWhat's weird is that it isn't *that* big.. out of interest were any messages logged in watchdog?
Comment #20
deja711 commentedYes, messages worked, detected bunch. Here is shorter output:
metatag 01/24/2016 - 19:43 Update 7102: No nodes need the translation entity... admin
metatag 01/24/2016 - 19:41 Update 7018: 5584 records were updated in total. admin
metatag 01/24/2016 - 19:41 Update 7018: 5581 records were updated in total. admin
metatag 01/24/2016 - 19:41 Update 7018: 5571 records were updated in total. admin
...
metatag 01/24/2016 - 19:35 Update 7018: 21 records were updated in total. admin
metatag 01/24/2016 - 19:35 Update 7018: 11 records were updated in total. admin
metatag 01/24/2016 - 19:35 Update 7018: 1 records were updated in total. admin
metatag 01/24/2016 - 19:35 Update 7018: 5584 records to update. admin
metatag 01/24/2016 - 19:35 Update 7040: 0 records were fixed. admin
metatag 01/24/2016 - 19:34 Update 7040: 5714 records to examine. admin
Comment #21
damienmckenna@deja711: Ok, those are fine. Thanks.