upgrade from version 6.x-3.x-dev to 6.x-4.1 problems [#595928]

I have been struggling with upgrading my March 11th 2009 version of 6.x-3.x-dev to the latest version. I've tried upgrading directly but that didn't seem to work, so I've been trying an incremental upgrade. When I went to 6.x-3.3 that seemed to work fine, however when I go from 6.x-3.3 to 6.x-4.0 all of my heartbeat blocks disappear. They are no longer listed in the blocks page. Additionally, If I navigate to "heartbeat/activity/personal" or "heartbeat/public", as per the documentation, I get blank white screens.

I've tried running the update.php script several times. I've cleared my cache, etc. but the blocks won't show up. I read through the changelog for version 4.0 and there wasn't anything explicit mentioned about removing the blocks (and the code still seems to be there), so I'm not sure what is going on.

Any help on this upgrade issue would be most appreciated.

Comments

Comment #1

gallamine CreditAttribution: gallamine commented 5 October 2009 at 00:57

If I try and directly upgrade from 3.x-dev to 4.0 (i.e. restore database to 3.x-dev version, and then run update.php after putting the 4.0 release in the modules directory) I get the following errors:


    * user warning: Table 'heartbeat_activity' already exists query: RENAME TABLE hb_activity TO heartbeat_activity in /home/admin/domains/.../public_html/alpha/sites/all/modules/heartbeat/heartbeat.install on line 313.
    * warning: include_once(./sites/all/modules/heartbeat/hb_activity/hb_activity.rules.inc) [function.include-once]: failed to open stream: No such file or directory in /home/admin/domains/..../public_html/alpha/sites/all/modules/rules/rules/rules.module on line 1181.
    * warning: include_once() [function.include]: Failed opening './sites/all/modules/heartbeat/hb_activity/hb_activity.rules.inc' for inclusion (include_path='.:/usr/local/lib/php') in /home/admin/domains/.../public_html/alpha/sites/all/modules/rules/rules/rules.module on line 1181.

Perhaps that helps.

Comment #2

Stalski CreditAttribution: Stalski commented 5 October 2009 at 09:06

This will be fixed tonight within next commit. But the changes will be more than that. For the update hooks, I find it really hard to cover all changes (maybe i did not tag correct or something) within update.php. I will try out some more upgrading, maybe by checking the database before the update to know what needs to be done.

Before upgrading, export all rules on heartbeat and export all heartbeat messages that you added custom. Go to the actions of your rules where heartbeat actions are defined and you will see that there are two node id's which can be used.
Before nid_target was used when its a node ... but since drupal sites are all about nodes, i changed nid_target to nid and added nid_target again as extra field to get more control. Especially for organic group for instance.
So this is anoying again but i really have to make heartbeat a full grown and mature API.
You will also see that your blocks and pages will be handled better (string class names instead of numeric delta's) and that you can configure these access types (I call them heartbeat activity streams from now on) to deny some messages from display.

I am working on a demo-site that will show all default heartbeat stuff and you will be able to download a example module there where extra heartbeat implementation will be demonstrated.

I will keep you informed.