Thanks for this module, so far it looks great!

Since it is based on Entity API, I would imagine that it would support use of Rules. How would I go about adding a user to a group using rules?

Is it possible at the moment at all? Will it be possible in the future?

Thanks heaps for any advice.

Cheers,

Martin

Comments

kristiaanvandeneynde’s picture

Hi there Martin!

First of all, thanks for the kind words.

I'll look into Rules support real soon. It could be supported by Entity API, but I'd have to check.
I usually add some extra sugar on top of Entity API's out-of-the-box stuff, though.

So far I've added extra Views handlers, CTools plugins, UI elements, etc.

Kind regards,
Kristiaan

mkostir’s picture

Thanks Kristiaan,

I had decided to use OG for this project, as I had to move it forward. But I do like the simplicity of Group module and will definitely re-visit it in my future project.

Will give feedback then.

Cheers,

Martin

kristiaanvandeneynde’s picture

Okay Martin,

I was curious how this would work out-of-the-box and found that you can already fiddle around with the following rules actions until I write my own:

  • Create entity (Group Membership)
  • Set data value (Group on Group Membership)
  • Set data value (User on Group Membership)
  • Save entity (Group Membership)

Again, I'll write my own implementation before the first stable release, but this should work already.

kristiaanvandeneynde’s picture

Status: Active » Closed (works as designed)

Closing as this will be in the documentation.

Pierre.Vriens’s picture

hey Kristiaan, as per the "... this will be in the documentation ..." in your last comment: I wonder if there is any documentation somewhere about how to do this. Do you know of any such docu that is available today? Or should we reopen this issue instead to consider it as part of the documentation issue?

kristiaanvandeneynde’s picture

I wonder if there is any documentation somewhere about how to do this.

I had this on my documentation to-do-list back then, but never got around to it. The "How to use this with Rules?" question has been answered in the issue queue before, though. So that answer could go in the centralized documentation.

Or should we reopen this issue instead to consider it as part of the documentation issue?

No. Reopening closed issues just for the sake of tagging them would make the issue queue unwieldy. I'm already having trouble finding the time to answer every issue in a timely manner. You can link closed issues from a related one just fine without having to reopen it.

Pierre.Vriens’s picture