Activity integration is broken

The problem is likely that I haven't upgraded integration with the Activity module yet and it's still using the D6 API.

I am also looking for integration between statuses and activity module.

Are we gonna support activity integration? Because it has dev release alone for D7.

Just looked -- it's been over a year since the last commit to Activity 7.x-1.x and 7.5 months since the last commit to 6.x-2.x. Activity was always hard to integrate with because there was rarely a stable release and API changes in dev weren't documented. So, no -- let's drop Activity integration. If someone picks it up and starts developing it again, we can always add the integration back.

However, that means we need to make sure we support another activity stream solution. I wrote Activity Log but I haven't ported it to D7 (and although it's usable in D6 I would really like to rewrite it pretty substantially -- and I don't have time to do that in the foreseeable future). That leaves Message and Heartbeat. I think that both of them should just work without any explicit integration courtesy of Rules integration, but I'm not 100% sure. (However Heartbeat permanently caches activity messages, so using submodules like Comments and Flag wouldn't work with it.)

I think we can go for message, cause it supports entity and rules(not a required dependency).

In 2.x we are planned to go for statuses as entity, so message will be a better option for us.

Changing the status to "needs work", since we decided to drop this integration. Any one of us can go ahead and delete this integration submodule.

Let's do this instead.

Are you guys planning flag friend integration?

We stopped support for activity. For statuses we have a separate module, so we just disabled it. But for fbss_comments activity integration code was written in fbss_comments.module and its not looking fine.

Can we remove it?

Yep

While we're at it, there is actually Activity integration code in the Tags submodule too

Marked #1563456: Fatal error: Call to undefined function db_fetch_object() in C:\wamp\www\sites\all\modules\statuses\submodules\fbss_comments\fbs as duplicate

@IceCreamYou

Re: Fatal error: Call to undefined function db_fetch_object() in C:\wamp\www\sites\all\modules\statuses\submodules\fbss_comments\fbss_comments.module on line 843

Your post: drupal/node/1563456

Can you kindly identify lines 840 to 849 to be deleted in fbss_comments.module (like typing out the first line and the last one?)

Thank you very much. :)

this

@IceCreamYou. Thank you.

Committed fix to dev

I got the same problem in the activity submodule and at least at the moment it isn't fixed yet:

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'op' in 'where clause': SELECT aid FROM {activity} WHERE type = :type AND op NOT LIKE 'fbss_deleted%' AND eid = :eid; Array ( [:type] => statuses [:eid] => 3 ) in fbss_activity_statuses_delete() (line 12 of /home/jschoder/Documents/projekte/nginx/veggie3/sites/all/modules/statuses/submodules/fbss_activity/fbss_activity.module).

That code should never be executed if this is a new installation or if you followed the upgrade instructions. If you continue have this problem please open a separate support request.