Call to a member function getPlugin()

+1. I posted an issue with the exact same problem before I saw this.

This is really weird. I don't have that problem at all.
Investigating this ...

Ok, I have the problem on a fresh install. Working on a fix.

The fix includes two things:
- An extra check to really see if the pluginWrapper is an object
- The problem with the install was that the default heartbeat templates did not have the correct structure anymore.
Worst case scenario should involve saving all heartbeat templates again.

Since the severity of this bug, I pushed it already.

I uninstalled the previous version, installed the latest dev, cleared cache, updated the database and I'm still getting the same blank screens. Is there something else I need to do?

This should work, the only thing you did not properly is "Delete old entry with heartbeat in database directly" instead of deleting them so the attachments are removed as well.
Are you sure you uninstalled the module as well? Just removing it after disable leaves the tables behind.
I can only say that this type of error means there is something seriously wrong, like drupal does not find the heartbeat entity anymore.

Could not reproduce this error with same steps.

The bundles are the message template (who are deliverd in heartbeat_defaults). This module is enable, right?

Can you give more detail on your installation then?

- Which heartbeat submodules do you have enabled?
- Are the message templates showing on the overview of templates?
- Can you manage the fields overview and display overview per template?

Can you reproduce this from scratch on site with only heartbeat and its dependants?

I am going to try a fresh install with only heartbeat and its dependencies and return with my results. But my current install is still not working.

Ok, I was successful in getting it to work on a fresh install with only the following modules installed and enabled:

heartbeat
ctools
token
pathauto
rules
entity
flag
shoutbox

I even applied your patch here: http://drupal.org/node/1267942 (comment #9 issue_1267942_9.patch) and was able to get polling to work with shoutbox. I do have another question/concern but its best if I address it in another issue.

So now that it's confirmed to work within a new install I'm assuming that the problem I'm having on my production site is within the database tables somewhere.

Yes, EVA seemed to be the problem for me as well

Hmm, So we'll digg into that. I did not know this module so bare with me :)

I installed the dev version of EVA and got the error too. Digging into it...

So, the problem is core throws an exception on extract id's. The problem is within "eva" is that it needs to know which is the entity variable in the build array.
The code beneath in eva explains it all, I attached some code to make it work.

/**
 * Extract an actual entity object from its $build array.
 *
 * This is a bit more complicated than it should be, since core entities, contrib
 * entities, and contrib entities based on EntityAPI all store their junk in
 * different slots of the build array. See http://drupal.org/node/1170198.
 *
 * @param $build
 *   The token string defined by the view.
 * @param $entity_data
 *   The token type.
 *
 * I hate you, Milkman Dan.
 */
function _eva_extract_entity_from_build($build) {
  // EntityAPI often sticks stuff in here.
  if (!empty($build['#entity'])) {
    return $build['#entity'];
  }

  // Other entities stick them here!
  elseif (!empty($build['#' . $build['#entity_type']])) {
    return $build['#' . $build['#entity_type']];
  }

  // Some entities are naughty.
  elseif ($build['#entity_type'] == 'user') {
    return $build['#account'];
  }
  elseif ($build['#entity_type'] == 'taxonomy_term') {
    return $build['#term'];
  }
  elseif ($build['#entity_type'] == 'heartbeat_activity') {
    return $build['#message'];
  }

  return FALSE;
}

Ofcourse this is not the right solution. I will look in heartbeat if I could not take #heartbeat_activity instead of #message ...

#19 worked for me too

Hi all, sorry for the delay.
I changed #message in #heartbeat_activity so eva should auto-find the entity.
Feedback would be great.

Adding some more info