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.
Make sure you run updates to have the latest database structure and note that some things require the latest CTools and Rules dev version to work without problems.
Mainly bugfixes on data types, rules integration, user relationship integration, exportables.
The most innovating thing is the Node.js integration by miles. It's still in early stages but it works. Note that there are access levels that are not checked so messages end up that shouldn't be. The heartbeat_nodejs is thus very experimental.
Big fix in comment cache and translation system for heartbeat comments.
a couple of minor to major other bugfixes reported in issue queue. See changelog for more details.
- Refactored heartbeat comments and shouts to sanitize the user input.
When shouts are displayed, the content is now sanitized with filter_xss
to filter the user input.
Actions:
- Upgraded heartbeat.install so the default allowed tags are more secure.
There is a left-over img attack but the code where this filtering is done,
is managed by a higher level permission. Before heartbeat messages,
heartbeat comments (and shouts) were sanitized with this tags match. It is
- moved connectedheartbeat to friendlist_activity module where it belongs.
- Improved performance for user loads and message template loads.
- fixed some bugs on http://drupal.org/project/issues/heartbeat.
- Added throbber to ajax loads.
- improved views integration module.
- Added some examples and documentation on heartbeat.menhireffect.be
- Friendlist_activity module will now take three user relations defining modules as api to make a choice on what defines heartbeat user relations. Friendlist / flag_friend / User relationships
- Added node relation for heartbeat views. we can now filter on node type as well.
- Cleared d.o. issues and support request untill satisfied.
- Refactored hds to follow releases of display suite
- Added check box on the stream configuration page so we can choose to have filters on block and/or page in stead of always enabled at once.
- Changed friendlist_activity to take options to define which user relation
api will be used.
- Debug and fixround through the issue queue on drupal.org
- Updated views integration back to normal
- Improved scalability of a stream bigtime by adding a variable to maximize
the sql. This is a rather weird configuration as it takes a little of playing
with numbers.
- Changed friendlist_activity to take options to define which user relation
api will be used.
- Debug and fixround through the issue queue on drupal.org
- Updated views integration back to normal
- Improved scalability of a stream bigtime by adding a variable to maximize
the sql. This is a rather weird configuration as it takes a little of playing
with numbers.
Fixed bugs on beta1
Added features for display suite for instance
Changed core to take more dynamic settings and settings from other contribs / custom modules
Added an example module to clear a lot of things up for my fellow contributors.
Views integration works again, although it will never will be as powerfull as heartbeat built-in blocks and pages.
Fixed some bugs
Changed menu so all heartbeat admin pages are gathered together.
Changed the manner how heartbeat include files and classes. It is not as nice as an autoload but it will be more performant
The api function logger is better than before because it includes an extra node id , the node target. This can be used for node references or organic groups for instance.
The display is even more configurable now. You can set global configuration, alter settings per stream and configure each message template specific.
Added a hook to filter messages, that allows us to filter the current stream with a callback, leaving out all messages that don't concern us.
With "shouts" module on, you can add comments to heartbeat activity messages. Another option is added for messages in node context, we can enable "node comments". This uses the normal comments we are familiar with. This setting exists per message type in the attachments section.
Added Ajax paging and settings for each stream per block and per page. The number of messages displayed can be set and after all filters and access checks, the number is calculated. "older messages" are shown with a pager on timestamp offset, making sure that all the messages are fetched that remain. A cron hook with a global setting will delete "too old" messages, to avoid bad streams.
This release is the first release where heartbeat fungates as API and not as (POC) module with too many features and possible features.
Heartbeat activity streams are very customizable. We have attachments (comments, flags, ...) and lots of settings on a per-message basis to create the desired displays.
Cleaned up lots of pieces of code
Added simple flag integration onto heartbeat activity messages
Added documentation in the module as well as at blog.menhir.be
- Solved lots of bug fixes from issues on drupal.org and project based issues
- Improved views integration with a heartbeat row style plugin (recommended in stead of using all fields)
- Added some features requests
TODO:
- base function to call from custom code to log into heartbeat
- add a view page for personal page based on the uid given in url
Fixed a lot of stuff and added some features. The views will be blocks for the moment and i don't know if all will be fetchable with views2.
The blocks for now are private and public heartbeat. The settings determine how you display and filter everything.
In this release, i added more default event triggered actions. Even more important, the output strings that show up in a users heartbeat page, are translatable.
This version is a release with a proof of concept. The intension is to log a users activity on the site based on occuring events. This module depends on rules and tokens. This is no disadvantage because every module can define their own rules and events.