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.
Hi!
Have upgraded my whole site to D7 mostly because of fabulous 'Heartbeat'.
I seem to have a few errors please ..
In admin/reports/status report:
The following token types are not defined but have tokens:
$info['types']['heartbeat_activity']
When the siteactivity block is enabled with all permissions set correctly:
'you are not allowed to see this activity'
I rebuilt permissions, cleared cache and then got:
You cannot serialize or unserialize PDO instances in cache_set() (line 137
Most appreciate any suggestions :)
Comment | File | Size | Author |
---|---|---|---|
#3 | Screenshot at 2012-02-10 15:31:16.png | 6.31 KB | rogical |
Comments
Comment #1
Stalski CreditAttribution: Stalski commentedHmm, this won't have much to do with heartbeat I hope. i am afraid I can't help you much on that.
There is no upgrade path currently for heartbeat.
I would suggest to start over with heartbeat since it's data is totally different. The activity you would lose anyway.
Concrete suggestion:
- disable heartbeat
- uninstall heartbeat completely
- install it again, all modules I guess (with display suite, tokens, rules already enabled)
- configure the streams you want to use
- configure built-in templates and create new ones. (As of D7, these are fully exportable and depending on CTools)
- Go to permissions and configure the permissions for heartbeat (maybe user profile, view content, things like that)
As activity is all about "new" or "changed" data, it is "less bad" not having an upgrade path. But I do feel your pain. I hope you can live with the solution.
Comment #2
Stalski CreditAttribution: Stalski commentedI nver had this porblem and I really can't reproduce it. Don't know where it's coming from, sorry
Comment #3
rogical CreditAttribution: rogical commentedSame issue:
For the suggestion:
- disable heartbeat
- uninstall heartbeat completely
Then all activities would be deleted, this is quite not operational in a production site.
Comment #4
Stalski CreditAttribution: Stalski commentedi'll check it
Comment #5
Stalski CreditAttribution: Stalski commentedI did what described and nothing happened, no message, no error in the watchdog ...
Can you specify where I should see this message and how?
Comment #6
rogical CreditAttribution: rogical commentedThis is a bit strange, I've used heartbeat several times, and just happened to get this error, don't know how to get rid of it.
I think we can keep this postponed as there may be same error in other users.
Comment #7
sw3b CreditAttribution: sw3b commentedI got the same on all my setup... it's not a big deal but it should not be there...
Comment #8
Anonymous (not verified) CreditAttribution: Anonymous commentedGetting same error message:
The following token types do not have any tokens defined:
$info['tokens']['heartbeat']
Comment #9
bigsyke CreditAttribution: bigsyke commentedSame issue here. I've reinstalled using the latest 7.x dev.
Comment #10
PedroMiguel CreditAttribution: PedroMiguel commentedgot the same error as OP, I'm using the latest dev.
I Truncate (empty) every cache on DB (even urelated caches just to be sure) and the problem is not on caches.
Comment #11
fraweg CreditAttribution: fraweg commentedI have the same error..
Best regards
Frank
Comment #12
fraweg CreditAttribution: fraweg commentedHi,
has anyone solved this problem?
Best regards
Frank
Comment #13
Stalski CreditAttribution: Stalski commentedFixed and pushed to git. The heartbeat token belongs to to its data type.
Comment #14
rogical CreditAttribution: rogical commentedThanks, it works.
Comment #15
sw3b CreditAttribution: sw3b commentedNice work thanks !
Comment #16
Stalski CreditAttribution: Stalski commentedComment #17
hallsy CreditAttribution: hallsy commentedi am getting this error as well now. how do i get rid of it?
I am on drupal 7.20.
thanks