For all of you that thought this project was dead, well you were
mostly right...Back from a long hibernation Activity is rubbing
its eyes and stretching its arms as the long cold winter gives
way to springtime (ok let's pretend we're in the southern
hemisphere where this would be true).

There are a lot of changes to the codebase to the point where
it's going to be easier to branch the 5.x series to 5.4 as many
of the token patterns have changed (more or less changed to
be more internally consistent) and as of yet there is no upgrade
path written for updating existing records from 5.3 or lower.

Please do not install 5.4 on a production site! If you want to help
test it out please try out a fresh install so that any problems can
be ironed out before attempting to write upgrade functions.

The Drupal 6 version of Activity is also now ready. This also does not
have a complete upgrade from 5.x written so it's best to test out
on a fresh install.

Contrib modules in 5.4:

buddylistactivity
buddylist2activity (although minimally tested)
commentactivity
flagactivity
nodeactivity
user_relationshipsactivity
views_bookmarkactivity
votingapiactivity

Contrib modules in 6.1:

commentactivity
flagactivity
nodeactivity
user_relationshipactivity
votingapiactivity

Issues that these releases should address in some form:

Tasks:

#230944: Drupal 6 port

Feature Requests:

#211809: block to show activity of user relationships
#307468: How to edit/delete activities for user and admin
#231331: Separate filtering settings for activity recording and display
#237240: privacy?
#247413: Don't log activity if no string set for action
#247394: Better Group of Token Settings
#253737: per relationship tab? and bit a more?

Support Requests:

#304102: Changing Views Bookmark (deprecated) to Flag
#310901: can not save activity page
#285051: Unable to save the activity message phrase
#239259: Activity on user profiles?
#252040: Filtering out Usernode
#291144: Customizing the activity stream to show on individual profile pages
#290959: Views Bookmarks Activity: "[operation]ed" token cannot be replaced?
#284750: Not logging activity for anonymous users
#261024: How to translate the [operation] ?

Bug Reports:

#289781: commentactivity does not work with parent node author
#310551: activity_time_limit is not obeyed in activity module
#215145: I can see just: [author] [operation]d the [node-type] [node-title-link]
#256204: user relationship activity not working?
#278942: Token values in buddylistactivity are over written
#277994: Nothing shows up on Activity page
#276598: Buddylist buddy requests generate "activity" but no text
#245716: User Relationship tokens defined incorrectly
#219911: buddylistactivity
#234601: buddylistactivity Block: Tokens Not Being Applied Correctly

CommentFileSizeAuthor
#18 activity.zip57.28 KBdavidburns
#18 activity_5.4_to_6.5.patch75.66 KBdavidburns
#14 nodeactivity-config-types.patch3.89 KBdgtlmoon

Comments

sirkitree’s picture

sirkitree commented

jaydub, thanks for the overview post! Extremely helpful! Now to come up with an attack plan. =) Bugs first, support requests (that require no coding, only feedback), then feature requests once we iron out the listed bugs. Sound okay? Anyone else wanna jump in and tackle a few of these?

sirkitree’s picture

sirkitree commented

another task that will get rid of a lot of confusion and tickets:
#314592: automatic filtering

jaydub’s picture

jaydub commented

5.4 and 6.1 versions now also have support for activity
generated by the Favorite Nodes module.

#314661: integrate with "favorite_nodes" for d6 users?

Stalski’s picture

Stalski commented

I will need this module for my next project and I will try to help you and jaydub with it. In a week i will jump into the module and look at the issues and pending patches. Keep me informed as I will do the same :)

greetz,
Stalski

jaydub’s picture

jaydub commented

I've posted announcements in most of the issues mentioned in
the parent post to let them know of the new versions to try
out. Hopefully we can get some folks to respond and try out
a snapshot. If all goes well then we're looking at closing out
20-30 issues when it's all said and done.

Nigeria’s picture

Nigeria commented

So what happens to all ou us that have 5.3 or lower install...is that the end of life as we know it!!!

jaydub’s picture

jaydub commented

well it means that if you want the new features and fixes and a smoother path
to the Drupal 6 version then yes it's going to be better to start looking at
5.4 than 5.3.

Creating an upgrade path for existing activity records in a 5.3 install isn't the
easiest thing in the world but it's a consideration.

The best thing to do is help test out 5.4 so that we can actually -really- this time
get a stable release that can be supported longer term. 5.3 was never really able
to make it to a stable release.

Nigeria’s picture

Nigeria commented

The only problem I ever have with Drupal is the speed with which the core and contributed modules change leaving orphaned modules and/or functionality in their wake. All in the name of "innovation".

Acquia seems to want to solve that problem for core modules. Who is going to lead the charge for contributd modules developers.

It's always VERY hard selling stuff into an enterprise if you can not guarantee support for functionality, which sometimes becomes mission critical, beyond a month or two.

jaydub’s picture

jaydub commented

well to be fair, most of us developing contrib modules are doing
this in our spare time at our own expense. Not everyone has
corporate backing...

Nigeria’s picture

Nigeria commented

First of all let me say that I appreciate EVERYBODY's effort. Drupal is what it is today because of the numerous FREE hours that its followers devote to it. They are to be commended.

It is easier however to champion a cause to the uninitiated if there is the assurance that their own effort will not be thwarted by not being able to upgrade.

Innovation, being what it is, sometimes require radically surgery to be undertaken on the patient. The real question really is surgery always neccesary!

To cut a long story short though, please consider upgrade options. Upgrade options make the modules more useful and attractive to use.

As most developers already now, the real asset in any system is the data that it collects. Throwing away that data in the name of innovation is a big pill to swallow.

--
Ade Atobatele

jaydub’s picture

jaydub commented

for your specific situation, what activity contrib modules are
you using? If I can take one module as a test case and see
what would need to be updated in a single activity record for
that module I can have an idea of what we are facing with
updating records.

Flying Drupalist’s picture

Flying Drupalist commented

You've written everywhere that this shouuld not be tested on a production site b/c of etc... Is this still the case for new users thinking about trying out this module? Thanks.

jaydub’s picture

jaydub commented

If you are installing this for the first time then the warning doesn't apply
in the sense that you won't have any previous activity records that might
not display the same as in the previous version of activity. However the
new branch is not frozen yet so I would not install on a production site
yet as there are still going to be some changes before an alpha/beta
is released.

hope that helps

dgtlmoon’s picture

dgtlmoon commented
StatusFileSize
new nodeactivity-config-types.patch3.89 KB

How do i post a new functionality patch? i've got a configurable node types and actions patch for nodeactivity but theres no where to post a new item on the project page?

jaydub’s picture

jaydub commented

#14 can you describe what your patch is attempting to do? The new branches of activity already include configurable node token types and node operation types which is what you seem to be trying to add.

icecreamyou’s picture

icecreamyou commented

When/where can other developers find documentation for integrating other modules with Activity 5.4.x/6.1.x?

jaydub’s picture

jaydub commented

#292181: Improved API documentation

is a slightly out of date version of the developer docs. If you start with that as a base and refer to some of the current contrib modules in the 5.4 or 6.1 branch you should be able to make some progress.

davidburns’s picture

davidburns
he/him
Primary language English
Location Philadelphia
commented
StatusFileSize
new activity_5.4_to_6.5.patch75.66 KB
new activity.zip57.28 KB

I ran the 5.4 branch through deadwood and then through coder. Went through manually and fixed a couple other things.
Here's the patch against 5.4 and a zip of all files.

jaydub’s picture

jaydub commented

#18 not sure you were aware but there is already a 6.x branch so patching 5.4 to turn it into a d6 module is not necessary...thanks for the effort!

paganwinter’s picture

paganwinter commented

Hi all.
Let me start by saying that this is a fantastic module.

However I am also looking at a module which lets me record User activity from an Admin perspective.
I need to track User's activity based on everything that he does on the site:
Comments on a node, Flagging on content, Node activity, User activity, User Relationships activity, VotingAPI activity.
All of these are readily provided by this module.

On top of all this I need a way to track which pages a User visits, how many times in all and for how long etc.
What is the best way of achieving this, by extending this module?

Also, I need a way to get reports on a per user basis for all the activities of the user. How do I go about getting this?
Can someone point me to the documentation of the various tables that this module uses?

sirkitree’s picture

sirkitree commented

Hi, can you please open this up as a separate issue? It's very off topic here. Also make sure you mention which version of Drupal you'll be using.

paganwinter’s picture

paganwinter commented

Sorry for the mess up. I realize that now.

(Anyways I have created a module that takes bits of the core Statistics module as well as the User Activity module to achieve this.)

jaydub’s picture

jaydub commented
Status: Active » Closed (fixed)

Closing this issue in favor of #379614: Create a 6.x-1.0 release which is an update of the status of the issue queue in advance of a new release.