I had a working version of 6.x-2.10 Drupal Commons with CiviCRM attached.

Responding to status reports, I downloaded Drupal Commons 6.x-2.12 from Acquia.

I replaced the Drupal Core and the Profiles code. Ran update.php which found no DB changes to make.

Now when I access any page at the site I get this:

Fatal error: Call to undefined function og_get_group_context() in /my-site-path/profiles/drupal_commons/modules/features/commons_core/commons_core.form.inc on line 484

Which reads:

  if ($form_state['group'] = og_get_group_context()) {
    // If a node is being viewed, add the nodes type within the group as a search
    // context option.

    $group_title = $form_state['group']->title;
    // Truncate the title, if needed

Drupal is at 6.28, 2013-01-16.

Not my first upgrade rodeo. Replaced all the files. Got the Fatal Error.

Anyone got any idea why this is happening, how to clear it up?

CommentFileSizeAuthor
Screen shot 2013-01-28 at 3.15.01 PM.jpg152.29 KBCyberflyer

Comments

blacklabel_tom’s picture

blacklabel_tom commented

Have you checked the version of Organic groups that commons is now running?

It could be that OG has been updated, but commons is still referencing a deprecated function.

Cheers

Tom

Cyberflyer’s picture

Cyberflyer commented
Status: Active » Postponed

Tom, thanks for the reply.

The version of OG in the Commons Profile is: version = "6.x-2.4"

Commons relies on its own unique set of contributed modules, including OG. They code to specific dev releases and you never know if upgrading to the recommended version in the control panel is safe or not.

I went through a bunch of procedure, putting the updated code in place and restoring the old database after running the update.php code produced the error.

I got it running. I don't like how and don't know why.

I'm increasingly dissatisfied with Drupal Commons as the upgrade process always seems to break the install.

Am changing the status to posponed as I think the real issue here is running the Update.php routine and the error is false. It claimed it made no changes, but site was broken. When I restored the pre-update Drupal 6 DB, it came up and ran.

Go figure.