Closed (cannot reproduce)
Project:
Heartbeat
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 May 2012 at 15:51 UTC
Updated:
30 May 2012 at 07:13 UTC
Hello,
for a very long time I have a problem with heartbeat and javascript. I have tested for days and hours an posted my problem here (http://drupal.org/node/1548890). I have only problems with heartbeat. Other modules like "Gallery Formatter" works fine. Now I have figured out that this problem happens when the heartbeat-block is on the same site as a shoutbox-block. I have test it with a fresh drupal 7 on several machines (win7/debian/ubuntu). I can reproduce this problem on all machines.
Hopefully this can help to solve this problem.
Best regards
Frank
Comments
Comment #1
Stalski commentedIt seems the integration of heartbeat is not very well with shoutbox, which I won't support anymore in favour of the activity status plugin that comes with the heartbeat_plugins module.
Are you sure you have the shoutbox patches applied to your shoutbox module?
Comment #2
fraweg commentedHello,
How can I do shoutbox things with the "activity status plugin"?
What patches do you mean? I have test it with the alpha and the dev version.
Best regards
Frank
Comment #3
Stalski commentedHi,
The short explanation: A heartbeat activity message is a drupal entity that is bundled in heartbeat templates. The heartbeat plugins module allows you to put a template entity form directly above a stream.
By default heartbeat plugins ships with a default template "heartbeat_tweet". For now you need to add a textarea field yourself at the Fields UI screen. Then at the Display screen for that template, you drag the normal message to hidden and the added textarea field to the visible portion (E.g. content). After that, you can select the "heartbeat tweet" template to prepend the stream the same way as you would do with the shoutbox.
Extra nice feature here is that you can add as much fields as you want (media for instance).
I changed the description of #1250324: Alpha version of shout box released for D7, What can we do to make it work with heartbeat? so you see what I mean. Heartbeat and shoutbox don't work out the box together. There are patches of me for instance that are not yet included in shoutbox. Heartbeat already implements a js-hook that shoutbox should expose. With those patches, that works ... your choice to still use it or not.
I'll close this as I can see now that you did not know about the patches that you need. There are issues at heartbeat and at shoutbox for this.
I hope you can find your way now
Comment #4
fraweg commentedHello,
thank you for your fast and detailed answer. I will test this solution.
But I think we misunderstood each other. I did not use the shoutbox plugin in heartbeat or a patch to make this 2 modules work together. This issue is there if you use the heartbeatblock (for me it was the user relation activity block) and shoutboxblock (out of the box as they are) an the same site.
Best regards
Frank
Comment #5
Stalski commentedYeah, I know what you mean.
The problem is that the javascript hook is invoked whenever a shoutbox form is on a page. If then a stream is on that page too, it will react on that hook.
This is not very good indeed, I'll need to check the shoutbox code again.