Hello,

reporting a little bug:

Activity privacy settings: (.../user/*/activity/settings)

only the last activity created is display.

:)

(using the last dev. version)

Comments

sirkitree’s picture

Not really sure what you mean here. can you give me a screenshot of this page as well as a screenshot of /admin/setting/activity

junro’s picture

StatusFileSize
new152.18 KB
new154.7 KB

ok, here the screenshots :)

sirkitree’s picture

Ok thank you. I'll have to test this out myself. It looks like the logic on the user setting may only be reporting one template per module. Will check into.

sirkitree’s picture

Status: Active » Postponed (maintainer needs more info)

Is this still happening for you with the latest dev? I just tried and here are my results.

/admin/settings/activity/list
Only local images are allowed.

/user/*/activity/settings
Only local images are allowed.

junro’s picture

Title: Activity privacy settings: only the last activity created is display. » Display only one activity in Activity privacy settings for same types with same triggers

ok I find the problem, It don't work only with activities with same options:

Same Activity Types and same Nodeapi Triggers.

junro’s picture

Title: Display only one activity in Activity privacy settings for same types with same triggers » Only one activity is displaying in Activity privacy settings for same types with same triggers
junro’s picture

Forgot to say I'm using the latest dev. version (June 19th)

sirkitree’s picture

So you're trying to get more than one message for something like nodeapi insert? For what purpose? I'm not sure that makes sense to do.

Scott Reynolds’s picture

Status: Postponed (maintainer needs more info) » Active

Sure it makes sense.

Create three node types and three separate messages for each node type for nodeapi insert. This bug was introduce by the types patch.

junro’s picture

That's it! :) I didn't really use Activity module before the types patch.

Scott Reynolds’s picture

Status: Active » Fixed

Hmm this is kindof hairy. A template -> action is uniquely identified really only by the $aid assigned to it. The problem is, when the admin wants to change the 'types' property of the template, they have to delete the template and create a new one. Thus, creating a new $aid and thus, eliminating the users previous setting.

But that is a different problem.

Committed this:http://drupal.org/project/cvs/177860

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.