I attempted to update OG on my site from 7.x-1.5 to 7.x-2.3 according to the security notice and got:

Project og was updated successfully. Installed version is now 7.x-2.3.
Backups were saved into the directory                                [ok]
/home/jbd/drush-backups/msfdrupal/20130903213510/modules/og.
PHP Fatal error:  Call to undefined function og_field_property_callback() in /var/www/drupal-7.14/sites/all/modules/entity/modules/field.info.inc on line 30
Drush command terminated abnormally due to an unrecoverable error.   [error]
Error: Call to undefined function og_field_property_callback() in
/var/www/drupal-7.14/sites/all/modules/entity/modules/field.info.inc,
line 30
The external command could not be executed due to an application     [error]
error.
Backups were restored successfully.                                  [ok]

Found other similar errors that were more than a year old and unresolved. I thought that someone else would surely run into this error by now since it is an advertised security update.

Comments

fonant’s picture

I get this too. None of the fixes from earlier reports work for me...

lautermash’s picture

Same here.

BruceDawson’s picture

Note: I would have expected drush (or something) to either:

  1. Abort because an upgrade to a different "major" was needed instead of an mere update.
  2. Abort or ask to install the additional modules that were needed.
  3. Install the necessary modules automatically.
joverstreet’s picture

Same issue from 1.4 to 2.3. Any solutions yet?

Thanks...

Anonymous’s picture

Same here. My workaround was instead of using drush up, I did drush dl, then drush updatedb. Seems to have worked. It might be related to this issue of drush: https://github.com/drush-ops/drush/issues/132

brandy.brown’s picture

Thank you! #5 worked great for me. Coincidentally, if you've already drush up'd, you can still just run drush dl.

emjayess’s picture

I've got a project that I upgraded to og 2.7 around a month ago... upgrade was smooth and seemingly without a hitch, and the site's been running smoothly since. Now (on a pre-production clone of the site) suddenly this error has popped up, and has rendered the whole site as well as the drush interface useless. I don't understand how this could've happened?!?

kyletaylored’s picture

Issue summary: View changes

I've been getting this on a recent upgrade from 1.x to 2.x, and it's been a pain ever since because all drush commands fail, including cache-clear.

The trick is, manually clear/truncate the cache_field table. This should allow you to then run drush commands and continue with database updates.