[D7] Mini Blocks

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

Looks not bad, but as for me it's not a good solution to write a HTML code in PHP functions, would be much better to use a theme() function and create a templates for your blocks.

There are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxcfischer832405355git

I'm a robot and this is an automated message from Project Applications Scraper.

38 | WARNING | Only string literals should be passed to t() where possible
Can be fixed by this way:
Just use this:

$label   = (arg(3) == 'edit') ? t('Edit') : t('Add');

And

'#title' => $label . ' mini block',

Rather this one:

$label   = (arg(3) == 'edit') ? 'Edit' : 'Add';

And

'#title' => t($label . ' mini block'),

87 | WARNING | Only string literals should be passed to t() where possible
I don't think that this can be fixed, so you should remove t() or ignore this warning.

11 | WARNING | Unused variable $k.
Just remove $k variable from the foreach.

Hope this help you.

Regards, Valentine.

> boxes — Boxes are meant to add functionality TO blocks, while Mini Blocks intentions are to remain completely independent without affecting the core functionality of blocks.

It's true that boxes can add functionality, but you can also have plain boxes that only hold content. And these have named block IDs.

Looks good for me :)

  // Create an object of type SelectQuery.
  $query = db_select('mini_blocks', 'mb');

  // Add extra detail to this query object: a condition, fields and a range.
  $query
    ->condition('mb.mb_id', $block, '=')
    ->fields('mb', array('mb_id', 'mb_value', 'uid', 'mb_date'))
    ->range(0, 1);
  $result = $query->execute()->fetchAll();

Don't use a dynamic query here: it's a simple query and it needs to be fast.

function mini_blocks_add() {
  $add_edit = (arg(3) == 'add') ? "Add" : "Edit";

Don't use arg() here: pass a parameter in from hook_menu().

Also, you could completely dispense with this function by using drupal_get_form() as the hook_menu() callback, and making your theme function tie in with the form builder.

function mini_blocks_admin_add($form = NULL, &$form_state = NULL, $defaults = array()) {

That's not the standard signature for form builder params. It's also good practice to suffix a form builder with _form for clarity.

  $label   = (arg(3) == 'edit') ? t('Edit') : t('Add');

Same as above: pass this in.

  $form['add_block'] = array(
    '#type' => 'fieldset',

There's no need for a fieldset at the top level of the form.

  // Must be unique unless editing.
  if (
    arg(3) != 'edit'
    ||
    $key != $key_original
    ) {
    if (count(mini_blocks_load($key)) > 0) {
      form_set_error('mini_block_key', t('Key has already been used'));
    }
  }

What if I'm editing block foo, and change its key to bar, and bar exists?
Don't use arg() -- instead, set a hidden form value is_new or something -- see how entity forms handle this.

    drupal_goto('admin/structure/mini-blocks', array('query' => array('msg' => 'success')));

The query string seems weird.

Also, don't use drupal_goto() in a form submit: use the form redirect system.

        'mb_date' => REQUEST_TIME,

You're updating the date on the block too. Is this then an updated timestamp rather than a created timestamp? Ditto the uid: that's the last user to edit. Both of these are unlike how other things work in Drupal, so worth commenting on to prevent confusion.

<article id="main-mini-blocks-add">
  <h2 style="font-size: 24px;"><?php print $add_edit; ?> Mini Block</h2>
  <p><?php print l(t("« List Mini Block"), 'admin/structure/mini-blocks'); ?></p>
  <?php print $form; ?>
</article>

It's not usual at all to use a tpl file for something like a form, especially if all you're doing it printing out the form!

Also, you're repeating the page title, and showing a link to the list page that's pointless because you have the breadcrumb and the tabs.

As for the view all TPL:

- You shouldn't make the 'Add Mini Block' in the theme -- use the menu system for this. See MENU_LOCAL_ACTION.
- use theme_table(), not raw HTML

When I install the module and go to the admin page, I get these errors:

    Notice: Undefined variable: rows in include() (line 18 of /Users/joachim/Sites/_sandbox/drupal-project-reviews/mini_blocks/theme/mini_blocks_view_all.tpl.php).
    Warning: Invalid argument supplied for foreach() in include() (line 18 of /Users/joachim/Sites/_sandbox/drupal-project-reviews/mini_blocks/theme/mini_blocks_view_all.tpl.php).

Lastly, I don't think you've really addressed the problem of module duplication. This looks exactly like boxes to me, except that miniblocks don't get exposed to the blocks system. (Which raises the question: why the name 'miniblocks' if they're not usable as blocks?) I would describe this more as a system that lets you have named snippets. Though if the point of the machine ID is portability (which is a good thing, I agree), then you really should consider using CTools to make the actual snippets exportable.

Oh, and lastly, there's no sanitizing of the mini block values: so mini_blocks_get_value() returns potentially dangerous output.

EDIT: Ok there is sanitizing of the mini block ID -- but for that you should probably be using the built-in machine_name form element, which does things for you.

<?php print htmlentities(substr($row['mb_value'], 0, 200), ENT_QUOTES)

Similarly, here you should be using the built-in Drupal sanitizing functions such as check_plain().

And you're not sanitizing mini_blocks_get_value(), which is presumably what users would be calling to get the value to output.

Searching for 'snippets' found me:

https://www.drupal.org/project/snippet
https://www.drupal.org/project/markup_snippets (D6 only)

That first one looks like it might cover a lot of your functionality and more -- sorry! :/

Thank you for your reviews. When finishing your review comment also set the issue status either to "needs work" (you found some problems with the project) or "reviewed & tested by the community" (you found no major flaws).

manual review:

1. please add the differences to existing projects to the project page so that user can make an educated choice what module to use.
2. mini_blocks_schema(): doc block is wrong, this should be documented as hook implementation. See https://www.drupal.org/coding-standards/docs#hookimpl
3. mini_blocks_schema(): the db_table_exists() call is wrong here, since the schema might get loaded for other purposes.
4. db_table_exists(): why is the serial id column necessary? Please add a comment.
5. mini_blocks_load(): instead of the foreach() loop just use ->fetchObject() to get one result row.
6. mini_blocks_get_value(): what is $block here? The machine name? Please add @param docs, see https://www.drupal.org/coding-standards/docs#param
7. mini_blocks_admin_add_form_validate(): do not check for required form fields here, use the #required property of the form API in mini_blocks_admin_add_form() instead. See https://api.drupal.org/api/drupal/developer!topics!forms_api_reference.h...
8. mini_blocks_overview(): "'date' => 'Date',": all user facing text must run through t() for translation, same for the other table headers.
9. "t('Type in the unique name of a mini block to') . ' ' . $action . ' ' . t('its value'),": don't concatenate variables into translatable strings, use placeholders with t() instead. See https://api.drupal.org/api/drupal/includes!bootstrap.inc/function/t/7
10. mini_blocks_menu(): 'admin/structure/mini-blocks/edit/%' should be 'admin/structure/mini-blocks/edit/%mini_blocks' so that block object is loaded automatically for you and passed to the page callback. See https://api.drupal.org/api/drupal/modules!system!system.api.php/function...
11. Project page: "Module always defaults to allow PHP code, so apply permissions with caution.": what does that mean? Where is PHP code allowed? One difficulty with this module is that it never outputs anything and leaves that to the developer - so they need to sanitize the output appropriately. Would be nice to have an example on the project page besides the l() case where check_plain() is done automatically. Something like $output .= filter_xss_admin(mini_blocks_get_value("my_test_block"));

So the project page with the missing similar modules and the misuse of t() with concatenating variables to it (can easily cause XSS security issues) are blockers right now. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.

> One difficulty with this module is that it never outputs anything and leaves that to the developer - so they need to sanitize the output appropriately.

Oh yes, that reminds me of something I thought of: you might want to consider one of:

- bundling an input format with this module that allows insertion of snippets
- providing snippets as tokens, so that another module that provides a token input format can be used (I'm sure that exists!)

> came with more requirements than I wanted (snippets is a great example: panels is a huge module that is required)

Wow, that's a weird choice they've made there!

I do think you should reconsider the module name though -- miniblocks is very confusing!

I am reviewing it..

Automated Review

Yes

Manual Review

Individual user account

Yes: Follows the guidelines for individual user accounts.

No duplication

Yes: Does not cause module duplication and/or fragmentation.

Master Branch

Yes: Follows the guidelines for master branch.

Licensing

Yes: Follows the licensing requirements.

3rd party assets/code

Yes: Follows the guidelines for 3rd party assets/code.

README.txt/README.md

Yes: Follows the guidelines for in-project documentation and/or the README Template.

Code long/complex enough for review

Yes: Follows the guidelines for project length and complexity.

Secure code

Yes: Meets the security requirements. / No: List of security issues identified.]

Coding style & Drupal API usage

[List of identified issues in no particular order. Use (*) and (+) to indicate an issue importance. Replace the text below by the issues themselves:

1. mini_blocks_admin_add_form_submit :
   

     if ($action == 'edit') {
       // The mb_date and uid is always updated to the new time and uid.
       $mbid = db_update('mini_blocks')
         ->fields(array(
           'mb_id' => $key,
           'mb_value' => $val,
           'uid' => $uid,
           'mb_date' => REQUEST_TIME,
         ))
         ->condition('mb_id', $key_original, '=')
         ->execute();
   
       drupal_set_message(t('Mini Block Edited'));
       $form_state['redirect'] = 'admin/structure/mini-blocks';
     }
     else {
       $mbid = db_insert('mini_blocks')
         ->fields(array('mb_id', 'mb_value', 'uid', 'mb_date'))
         ->values(array(
           'mb_id' => $key,
           'mb_value' => $val,
           'uid' => $uid,
           'mb_date' => REQUEST_TIME,
         ))
         ->execute();
   
       drupal_set_message(t('Mini Block Added'));
       $form_state['redirect'] = 'admin/structure/mini-blocks';
     }

   Use the drupal_write_record it will provide the free validation for you as well.

2. No configure link in info file
3. Found no deltion option of the miniblock.Plesae specify ?

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

You need another review bonus to that will put you on the high priority list, then git administrators will take a look at your project right away :)

@cfischer83,
One git admin(@klausi) has done a review and for getting another review bonus from another git admin you need another review bonus.See Project application workflow for more info. https://www.drupal.org/node/532400
corrected git clone command and added automated review link.
Assigned to myself for next review that may be in tonight.

@cfischer83: you can get multiple review bonuses, so don't worry ;-)

@cfischer83,
First thanks for Contribution! I have not found any release blocker.Congrats setting it to RTBC :)

Automated Review

Best practice issues identified by pareview.sh / drupalcs / coder.

Review of the 7.x-1.x branch (commit 5ac44d7):

Manual Review

Individual user account

Yes: Follows the guidelines for individual user accounts.

No duplication

Yes: Does not cause module duplication and/or fragmentation.

Master Branch

Yes: Follows the guidelines for master branch.

Licensing

Yes: Follows the licensing requirements.

3rd party assets/code

Yes: Follows the guidelines for 3rd party assets/code.

README.txt/README.md

Yes: Follows the guidelines for in-project documentation and/or the README Template.

Code long/complex enough for review

Yes: Follows the guidelines for project length and complexity.

Secure code

Yes: Meets the security requirements.

Coding style & Drupal API usage

[List of identified issues in no particular order. Use (*) and (+) to indicate an issue importance. Replace the text below by the issues themselves:

1. hook_help() is missing in this module.It would be nice if you add it at the top in .module file.
2. function mini_blocks_load($block) { : The parameter name should be $mb_id instead of $block because it is referring to machine menu block id.
3. It would be nice if you also display the Edit link in the mini blocks listing page admin/structure/mini-blocks instead of linking the mb_id field to edit page.
4. you should also provide the function to delete the menu block.It would be nice if you also display the Delete link in the mini blocks listing page admin/structure/mini-blocks
5. mini_blocks_sanitize : Usage of single quotes is prefferable than double quotes.Also please add a comment above the regression what it do.
6. mini_blocks_overview : Usage of single quotes is prefferable than double quotes.Also please add a comment above the regression what it do.
7. mini_blocks_overview : Use the "db_query is preferrable than db_select for static" queries.
8. (+)mini_blocks_overview : Implement the pager on this page because its not the right approach to display all the data on this page without pager.
9. mini_blocks_admin_add_form :
   

     $form['submit'] = array(
       '#type' => 'submit',
       '#value' => t('Save Changes'),
       '#id' => t('edit-submit'),
     );

   Please add a comment about the neeed of #id.

10. Readme.txt is nice :)
11. mini_blocks_admin_add_form_submit :
    

      $record = array(
        'id' => $id,
        'mb_id' => $key,
        'mb_value' => $val,
        'uid' => $uid,
        'mb_date' => REQUEST_TIME,
      );
    
      if ($action == 'edit') {
        $primary_key = 'id';
        $record['id'] = $id;
        $return = drupal_write_record('mini_blocks', $record, $primary_key);
      }
      else {
        $return = drupal_write_record('mini_blocks', $record);
      }

    you can also write it like this.This will remove the dependency of edit action.

      $record = array(
        'mb_id' => $key,
        'mb_value' => $val,
        'uid' => $uid,
        'mb_date' => REQUEST_TIME,
      );
      if (isset($id)) {
        $record['id'] = $id;
        $return = drupal_write_record('mini_blocks', $record, 'id');
      }
      else {
        $return = drupal_write_record('mini_blocks', $record);
      }

12. mini_blocks_overview : drupal_substr is preffered over substr
13. mini_blocks_admin_add_form_submit : Remove the return $return; after the $form_state['redirect'] because its not needed here.If it is please add a comment.

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

Please take another review bonus, that will put you on the high priority list, then git administrators will take a look at your project right away :)
Awesome Use of form Api :)

Review of the 7.x-1.x branch (commit 5ac44d7):

• Coder Sniffer has found some issues with your code (please check the Drupal coding standards).
  

  FILE: /home/klausi/pareview_temp/mini_blocks_forms.inc
  ----------------------------------------------------------------------
  FOUND 1 ERROR AFFECTING 1 LINE
  ----------------------------------------------------------------------
   110 | ERROR | [x] Expected 1 space after FOREACH keyword; 0 found
  ----------------------------------------------------------------------
  PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
  ----------------------------------------------------------------------
  

• No automated test cases were found, did you consider writing Simpletests or PHPUnit tests? This is not a requirement but encouraged for professional software development.

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.

manual review:

1. I think the README should also contain a warning about the XSS threat same as on the project page.
2. mini_blocks_load(): mini_blocks_sanitize() is not needed here, the DB API will sanitize the value automatically in the placeholder.

But that are not application blockers, so ...

Thanks for your contribution, cfischer83!

I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.

Here are some recommended readings to help with excellent maintainership:

• Dries' post on Responsible maintainers
• Best practices for creating and maintaining projects
• Maintaining a drupal.org project with Git
• Commit messages - providing history and credit
• Release naming conventions.
• Helping maintainers in the issue queues

You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!

Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

Thanks to the dedicated reviewer(s) as well.