I mentioned it earlier that I've got some party activity code here, it's nothing special, just something to try out party and to demonstrate what can be done with party.

Documentation on how to install/use it is included, if you're interested in trying it out, you probably should install both, party_activity and party_activity_example.

Note further that with this version this code doesn't know how to get the party ID so it's using the drupal user ID instead and treats it like the party ID.

CommentFileSizeAuthor
#5 party_activity.tgz6.3 KBmatthias_mo
#5 party_activity_example.tgz1.23 KBmatthias_mo
party_activity_example.tar_.gz1.24 KBmatthias_mo
party_activity.tar_.gz6.3 KBmatthias_mo

Comments

yautja_cetanu’s picture

yautja_cetanu commented

Wow didn't notice this! Will investigate it as soon as possible.

yanniboi’s picture

yanniboi commented

So I get this error when I install the above version of party_activity replacing the current version that comes with the 7.x-1.x-dev branch of party:

  • Error messageFieldException: Attempt to create field name <em class="placeholder">body</em> which already exists and is active. in field_create_field() (line 85 of /home/thetribesonline/public_html/party_activity/modules/field/field.crud.inc).

Should the two modules be somehow complementing each other or should I be installing party_activity in a specific way?

matthias_mo’s picture

matthias_mo commented

Should the two modules be somehow complementing each other or should I be installing party_activity in a specific way?

First, be aware that when you're doing a git clone/git pull from the party sources it already contains a party_activity module, I think it's from rlmumford (party/modules/party_activity).
His version and my implementation of party_activity happened independently and have nothing in common.
So you first have to make sure that Drupal sees only one of these 2 implementations.

The other thing is that I should have used variable names with name space prefixes to avoid collisions, so guess I'll have to post a reworked version.
The error message you reported simply says that a webforms field is about to be created but there is already one with the same name in the database...

rlmumford’s picture

rlmumford
Primary language English
Location Manchester
commented

Can you post that again, for some reason I can't extract this with WinRAR. Looks very interesting though.

matthias_mo’s picture

matthias_mo commented
StatusFileSize
new party_activity_example.tgz1.23 KB
new party_activity.tgz6.3 KB

I changed the naming of the body field and created new tar's. I hope this time they don't get corrupted.

yanniboi’s picture

yanniboi commented

Fantastic. matthias_mo I did exactly that, but I thought I'd just check to be sure... will have another look!

rlmumford’s picture

rlmumford
Primary language English
Location Manchester
commented

This is some good work, and it looks like there is some useful middle ground we can find between the two modules.

It seems like the main difference is that the partY_activity in the party project builds an activity entity whereas this module uses particular node types. I really like some of the rules integration stuff though. do you think you could bring some of that into the party_activity module?

out of interest, why did you got with a custom table rather than an entity_reference field to map Activities to Parties?