You are here

Home » API reference » Organic groups 6.2

README.txt in Organic groups 6.2

Same filename in this branch
  1. 6.2 README.txt
  2. 6.2 modules/og_actions/README.txt
  3. 6.2 modules/og_notifications/README.txt
Same filename and directory in other branches
  1. 6 modules/og_actions/README.txt
The og_actions module is a collection of actions. Their most common use case is in conjunction with the Views Bulk Operations module. Together, these modules make a terrific admin dashboard for putitng content into and out of groups, and adding removing members from groups. 

Requirements:
og.module

Suggested:
trigger.module OR
workflow.module OR
rules.module OR
views_bulk_options.module

Actions
There are 11 actions in this module. Here is a sampling.

Non-configurable actions:
-------------------------
"Make the node publicly visible" -- This action will make the node visible to the public. This has the same effect as checking the "Public" box on node creation.

"Make the node private to its groups" -- This action has the opposite of "Make the node publicly visible."  This action is equivalent to unchecking the "public" box on node editing.

"Remove the node from all groups" -- This is action will remove all group ties to this node. This will occur even if you have selected "Audience Required" in your organic group settings.

Configurable actions:
---------------------
"Add the node to the specified group..." -- This action allows an administrator to select a group and add nodes to it. Any currently published, organic group node type will be listed. In large lists, this could potentially be a very long list. This action could potentially add a node that is in the excluded content type list.

"Remove the node from the specified group..." -- This action removes the node from the selected groups. Potentially, it could remove the last group from the node, even if "Audience Required" is selected in organic groups.

Notes
If you are using workflow.module with this module, you may find that your actions are not taking effect during node creation. To fix this bug use the following SQL query in your database:

UPDATE SYSTEM SET weight = 10 WHERE name = "workflow"

This will ensure that og adds its data to the node before workflow attempts to act on it. You could alternatively set workflow's weight in the system table using the weight module.

File

modules/og_actions/README.txt
View source 
  1. 

  2. The og_actions module is a collection of actions. Their most common use case is in conjunction with the Views Bulk Operations module. Together, these modules make a terrific admin dashboard for putitng content into and out of groups, and adding removing members from groups. 

  3. 

  4. Requirements:

  5. og.module

  6. 

  7. Suggested:

  8. trigger.module OR

  9. workflow.module OR

  10. rules.module OR

  11. views_bulk_options.module

  12. 

  13. Actions

  14. There are 11 actions in this module. Here is a sampling.

  15. 

  16. Non-configurable actions:

  17. -------------------------

  18. "Make the node publicly visible" -- This action will make the node visible to the public. This has the same effect as checking the "Public" box on node creation.

  19. 

  20. "Make the node private to its groups" -- This action has the opposite of "Make the node publicly visible."  This action is equivalent to unchecking the "public" box on node editing.

  21. 

  22. "Remove the node from all groups" -- This is action will remove all group ties to this node. This will occur even if you have selected "Audience Required" in your organic group settings.

  23. 

  24. Configurable actions:

  25. ---------------------

  26. "Add the node to the specified group..." -- This action allows an administrator to select a group and add nodes to it. Any currently published, organic group node type will be listed. In large lists, this could potentially be a very long list. This action could potentially add a node that is in the excluded content type list.

  27. 

  28. "Remove the node from the specified group..." -- This action removes the node from the selected groups. Potentially, it could remove the last group from the node, even if "Audience Required" is selected in organic groups.

  29. 

  30. Notes

  31. If you are using workflow.module with this module, you may find that your actions are not taking effect during node creation. To fix this bug use the following SQL query in your database:

  32. 

  33. UPDATE SYSTEM SET weight = 10 WHERE name = "workflow"

  34. 

  35. This will ensure that og adds its data to the node before workflow attempts to act on it. You could alternatively set workflow's weight in the system table using the weight module.