CVS edit link for JeremyFrench

I am a full time Drupal developer. My employer encourages me to contribute back to the community. I have fixed a few small bugs in core but would like to be able to contribute modules

The first of these which I am able to contribute as it works well as a stand alone module is the ‘inform’ module. This uses the a web service by inform technologies (http://www.inform.com/index.html?tab=3) to assign taxonomy terms to articles using Drupal’s taxonomy system.

As it stands all that this module does it tag items on insert save and allow batch processing to tag existing content. It also exposes a block to show the inform tags on a node page.

In future the number of different blocks that will be exposed will be increased to show related articles, and related media from other web sites.

The reviewer may have issue with the altering of a core table. This was done for performance reasons as the number of tags can run into the millions and having to query two tables with redundant data in them to get the tags would be slow.

The functionality may end up being similar to that in the opencalais module but the services that they use are different so a separate module is justified.

CommentFileSizeAuthor
#8 inform.zip23.93 KBJeremyFrench
#5 inform.zip23.91 KBJeremyFrench
#2 inform.zip23.94 KBJeremyFrench

Comments

JeremyFrench’s picture

Status: Postponed (maintainer needs more info) » Needs review

The module is now attached

JeremyFrench’s picture

StatusFileSize
new23.94 KB
greggles’s picture

It's hard to test this given the reliance on an external service, but I did a visual inspection of the code. I found a handful of things to tweak before this module is released. Specifically there are several calls to drupal_set_message which are not translatable and/or may contain security issues (lines 87, 170 and 315).

So, leaving "needs review" though I'm +1 on the application I'm hesitant about these important changes that need to happen (they could happen after the application is approved).

avpaderno’s picture

Status: Needs review » Needs work

Security issues need to be resolved before the CVS account gets approved; also the use of translatable strings is an important point, in a Drupal module.

I am changing the status basing on the previous comment.

JeremyFrench’s picture

Status: Needs work » Needs review
StatusFileSize
new23.91 KB

Have updated file to get rid of the problems with the t() functions

JeremyFrench’s picture

I should mention that you can sign up for an API key to test this here.

http://www.inform.com/index.html?tab=3

avpaderno’s picture

Status: Needs review » Needs work

What reported by greggles about code security is still true (at least for one of the three cases).

JeremyFrench’s picture

Status: Needs work » Needs review
StatusFileSize
new23.93 KB

Drat, I don't know how I missed that. Changed that, also the context in batch mode.

avpaderno’s picture

Status: Needs review » Needs work
  1.   $batch = array(
          'title' => t('Batch Tagging articles.'),
          'init_message' => t('Getting Articles to tag'),
          'error_message' => t('Tagging Failed'),
          'progress_message' => '',
          'operations' => array(
            array('_inform_batch_process', array($max_days, $max_batch)), 
          ),
          'finished' => '_inform_batch_finish',
        );
        batch_set($batch);
    }
    

    Strings used in Drupal user interface have the first word written in capital case, while the others are written in lower case characters.

  2. See the Drupal coding standards to understand how a module code should be written.
greggles’s picture

That seems like a nitpick below what a cvs application review should include. There are thousands of instances of improper capitalization in contrib and more created every day - I think the application should be approved at this point and further issues moved to the issue queue of the module.

avpaderno’s picture

Status: Needs work » Fixed

Basing on the greggles's comment, I am approving JeremyFrench's application (I should have done it already).

A note about my reference to the coding standards: the coding standards report also that a module should use the Drupal Unicode functions instead on PHP string functions; when I make a reference to Drupal coding standards, it could be the code is not using such functions.

JeremyFrench’s picture

Status: Fixed » Closed (fixed)
avpaderno’s picture

Status: Closed (fixed) » Fixed

We don't change the status to closed; that is automatically done after 14 days.

JeremyFrench’s picture

Status: Fixed » Closed (fixed)
avpaderno’s picture

Status: Closed (fixed) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

avpaderno’s picture

Component: Miscellaneous » new project application
Assigned: Unassigned » avpaderno
Issue summary: View changes
Status: Closed (fixed) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.