blup [blup]

Attaching the module files.

... And changing the status.

Well, there are no existing solutions that do what I'm trying to accomplish - the reason I made this module.

For drupal 6, there are several micro-communication modules (shoutbox, facebook style status, privatemsg, etc) which establish a communication between two users, and others (comment, notably) that establish a communication between a user and a node. With the coming of drupal 7 entities, I decided it was time to make a cohesive api that abstracts this relationship and provides a fieldable, customizable entity that attaches to others. This entity is light, and contains the essentials (no title/body, just fieldable), and thus very flexible for developers.

Like i mentioned on my motivation statement, this communication might be between a user and a node, a user and another user, or a user and a micro (which, as it can attach to itself, is nest-able). The possible applications are very extensive and I am already working on further expansions on this idea (like i mentioned, a finer grained access module that could turn 'micros' into private messages (user to user) or private comments (user to node/micro/comment).

Newer version with OG support and without Git directory.

I've done quite a bit of work on this module, and i have several others that are based on its api. Although in alpha phase, it remains a very functional and general solution for the problem i've discussed. I'm still working on integrating it with other modules (Views + OG are done, Panels is next) and making a demo website. Is there a chance I could get a review?

Another week of work...

I've been a member for 2 and a half years and made numerous patches (including core). I've worked on this module for a couple of months now, and I believe I have answered all of the requirements for the application process. I understand not a small module (6300 lines with views, og, and search integration), and I still have a bit of a way to go with certain bug fixes and architectural issues, but 30 days and no admin review seems a bit much. Please let me know if there's anything else I could do to speed up the process.

*bump*

Thanks for the review kiamlaluno. I've attached a reviewed version. Here's a breakdown of your observations:

1. Fixed
2. The module is quite complete. Most of the commented out parts were 'Todo' reminders, but for the sake of clean code I removed all of the reminders and fixed hook_cron.
3. Similar to node.module's hook_form (node_content_form):
   

   /**
    * Implements hook_form().
    */
   function node_content_form($node, $form_state) {
     // It is impossible to define a content type without implementing hook_form()
     // @todo: remove this requirement.
     $form = array();
     $type = node_type_get_type($node);
   
     if ($type->has_title) {
       $form['title'] = array(
         '#type' => 'textfield',
         '#title' => check_plain($type->title_label),
         '#required' => TRUE,
         '#default_value' => $node->title,
         '#maxlength' => 255,
         '#weight' => -5,
       );
     }
   
     return $form;
   }
   

   This hook responds to the hook_forms *_micro_form callback :

   /**
    * Implements hook_forms().
    * All micro forms share the same form handler.
    */
   function micro_forms() {
     $forms = array();
     if ($types = micro_type_get_types()) {
       foreach (array_keys($types) as $type) {
         $forms[$type . '_micro_form']['callback'] = 'micro_form';
       }
     }
     return $forms;
   }
   

4. Although that was copied from node.pages.inc, which does exactly the same thing, I fixed it to your request.
5. I have removed the *.js files altogether as I have no use for them yet - they were left there from when i inspired myself from node. If what you're mentioning is really an issue, you should mention it in the Core issue queue.



I hope the module meets your standards now. I'm sure there are small bugs, but as you can see I'm actively working on improving the module. Thanks for your critiques.