Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I got this error since the last DEV version. It make the streams unavailable and unusable. Is there a workaround ?!?
Fatal error: Call to a member function getPlugin() on a non-object in /home/sitename/www/www/sites/all/modules/heartbeat/modules/heartbeat_plugins/heartbeat_plugins.module on line 358
The problem occur when you display the page of an heartbeat streams.
Comments
Comment #1
sw3b CreditAttribution: sw3b commentedOK, I uninstall alle the module, clear all database that were left, clear all configuration and reinstall all module and still I got the error.
The minute I try to generate some activity the module crash even the stream tab in the user section. If a clear all logs the error is gone and the message "No activity yet" and after an activity is publish the stream crash.
Wish it could help.
Comment #2
Sylense CreditAttribution: Sylense commented+1. I posted an issue with the exact same problem before I saw this.
Comment #3
Stalski CreditAttribution: Stalski commentedThis is really weird. I don't have that problem at all.
Investigating this ...
Comment #4
Stalski CreditAttribution: Stalski commentedOk, I have the problem on a fresh install. Working on a fix.
Comment #5
Stalski CreditAttribution: Stalski commentedThe 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.
Comment #6
Sylense CreditAttribution: Sylense commentedI 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?
Comment #7
sw3b CreditAttribution: sw3b commentedOK,
I uninstall the module
Clear cache
Delete folder of old DEV
Delete old entry with heartbeat in database directly
Re-upload the new DEV
Enable the module
1. After installation it work with no activity
2. After activity i'm getting an error
EntityMalformedException : Property bundle is missing on entity of type heartbeat_activity. in entity_extract_ids() (line 7405 in /home/website/www/www/includes/common.inc).
Comment #8
Stalski CreditAttribution: Stalski commentedThis 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.
Comment #9
Stalski CreditAttribution: Stalski commentedCould not reproduce this error with same steps.
The bundles are the message template (who are deliverd in heartbeat_defaults). This module is enable, right?
Comment #10
sw3b CreditAttribution: sw3b commentedYes the module is enable ! I tried to remove and reinstall again and again. And i cannot get rid of this error.
I have latest DEV version, latest CTOOLS DEV version also.
Comment #11
sw3b CreditAttribution: sw3b commentedI even restore my drupal database to old version where it work and I got the same error...
Comment #12
Stalski CreditAttribution: Stalski commentedCan 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?
Comment #13
Sylense CreditAttribution: Sylense commentedI 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.
Comment #14
sw3b CreditAttribution: sw3b commentedOn my side also I currently trying on brand new fresh install. I let you know after.
Comment #15
Sylense CreditAttribution: Sylense commentedOk, 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.
Comment #16
sw3b CreditAttribution: sw3b commentedI found it ! After starting from scrath 5 time, in french, in english I start removing module. It seems there is a conflict with EVA. I'm using EVA to manage the attachement to nodes for an look alike views gallery.
@Sylense do you use EVA on your side ?!?
After removing EVA the module seems to be working correclty.
Comment #17
Sylense CreditAttribution: Sylense commentedYes, EVA seemed to be the problem for me as well
Comment #18
Stalski CreditAttribution: Stalski commentedHmm, 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...
Comment #19
Stalski CreditAttribution: Stalski commentedSo, 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.
Ofcourse this is not the right solution. I will look in heartbeat if I could not take #heartbeat_activity instead of #message ...
Comment #20
sw3b CreditAttribution: sw3b commentedDo you have an update on this one ?!? I really need EVA and when both are enable the site crash...
Thanks for you work in advance...
Comment #21
sw3b CreditAttribution: sw3b commentedBy the way, adding the lines solve the problem... for now ! ;)
Comment #22
SocialNicheGuru CreditAttribution: SocialNicheGuru commented#19 worked for me too
Comment #23
Stalski CreditAttribution: Stalski commentedHi all, sorry for the delay.
I changed #message in #heartbeat_activity so eva should auto-find the entity.
Feedback would be great.
Comment #24
sw3b CreditAttribution: sw3b commentedThanks so far it look great !
Comment #25
Stalski CreditAttribution: Stalski commentedComment #25.0
Stalski CreditAttribution: Stalski commentedAdding some more info