Unsupported

This module attaches a node to every user. Unlike Usernode this module does not use the author as link between user and node.

At Tribute Media we have many sites in various stages of development. Sometimes upon returning to them I have noticed that Update Status has not checked for updates for up to 4 weeks. I then notice that the "drupal_http_request_fails" flag is set.

It is my understanding that when the variable "drupal_http_request_fails" is set the only way to get Drupal to re-attempt to make a request if to manually reset the variable. Drupal doesn't even check anymore until I reset the flag.

This module allows the user to configure when to check if the flag is set, and reset the flag. The interval is configurable from 1 minute to days or weeks.

When the interval times out the module checks "drupal_http_request_fails" to see if it is set to TRUE - meaning that no HTTP requests are being attempted - this module will reset the flag and log to the watchdog table. If the variable is set to FALSE - meaning that there is no problems making HTTP requests - it logs this to the watchdog table as well.

translation_tabs module adds extra tabs on top of the node form, so that users can easely go to the translation, or add a new translation. Without going to translate every time.

OG Node Approval offers content review between group members allowing them to approve or reject content. When creating or updating content simply choose the audience for the content (including multiple groups), save the node, and the module will insert group members from those respective audiences into the a node approval table.

2.x:

• After a configured threshold of members approves the node content OG Node Approval integrates with the Flag module flagging the node as globally "approved".
• OG Node Approval provides tokens of state collection on a node with which you can integrate into Rules or some other workflow module.
• OG Node Approval provides hook_ona to act on operations such as global approve/reject and user approve/reject. It passes in a state collection array much like the above tokens to do workflow or custom approval methods via a custom module
• The easy user interface has been split into a sub-module, OG Node Approval UI that you may enable if you don't want to code your own custom interface. Without enabling this module there is no way to approve or reject nodes.