Closed (fixed)
Project:
Heartbeat
Version:
6.x-4.x-dev
Component:
Code
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Dec 2010 at 11:04 UTC
Updated:
5 Jan 2011 at 14:40 UTC
Jump to comment: Most recent file
Hi Stalski,
I few days ago I updated to the current dev from December 1st and now I have a problem with the message objects. They all have a nid of 0 which of course is not correct. At least this is the case when printing the $object variable in a custom DS field. I just reviewed the code of HDS and I think that this should happen without DS as well but I didn't have the time to look further into this. Maybe tonight after work. Maybe you're faster...
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | heartbeat.patch | 935 bytes | DrakeRemory |
Comments
Comment #1
DrakeRemory commentedI forgot to mention that this was not the case with 6.x-4.10 and the DB entries are fine.
Comment #2
DrakeRemory commentedHi Stalski,
if found the problem! The nid was reset to 0 in heartbeat_comments_heartbeat_load and therefore not available in $object variable in my custom DS field. My current solution is just using hook_heartbeat_load in a custom module as well but before heartbeat_comments does and saving the nid to nid_bu as a backup. I think this is something hds should do.
Comment #3
Stalski commentedHmm yeah, that was a fix for some other bug. I will have to refactor this. The other bug was that comment box showed up when node comments and commenting was enabled but configured in the node type. For this case, the caching id was set wrong it showed the comment form.
This should be fixed now as well as your bug.
Can you check in dev to see if it works for you too?
Comment #4
DrakeRemory commentedI will do that tonight!
Comment #5
DrakeRemory commentedHi Stalski,
it works. Thanks!
Comment #6
DrakeRemory commentedAlso it would be nice to have all NIDs in that object variable when messages are grouped...
Comment #7
Stalski commentedthat is somethign you can do yourself. Just add the !nid variable in the rules ui (or via code heartbeat_api_log)
Comment #8
DrakeRemory commentedSure I have that one added but in grouped messages I only have the nid of the first message in the $object variable of a custom display suite field. It would be nice to have an array with all nids of the messages that are grouped together. Then I can add images of all nodes below the message. The attached patch provides this feature.
Comment #9
Stalski commentedah like that. I always put the image in the message as well. I group on user to summarize images then.
I will look at your patch as well, could be nice if it does not create extra load.
At this point, new features will only be accepted as the performance is acceptable.