Download & Extend
Similar By Terms » Issues

Patch implementing multiple blocks per vocabulary and adding other than this content type option

Posted by miiimooo on July 31, 2009 at 3:58pm
Project:Similar By Terms
Version:6.x-1.18
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:closed (won't fix)

Issue Summary

The attached monolithic path adds two features

  • multiple blocks for each vocabulary (number is configurable): in site configuration | similar by terms there is a collapsed fieldset at the bottom of the form that allow setting how many blocks should be created for each vocabulary (and the ANY vocabulary). The blocks show up in the block configuration labeled #1, #2, #3 etc
  • added "other than current" content type option to the block configuration options. Does the opposite of same as current.

    Note: This patch will break existing similar blocks. You'll have to re-create and reconfigure them.

    • AttachmentSize
    similarterms-add-multiple-blocks-and-other-than-current-type.patch7.92 KB
    Login or register to post comments

    Comments

    #1

    Posted by rmiddle on August 1, 2009 at 4:18pm

    miiimooo,

    Patch looks good for the most part. I am going to try and get this into the next version.

    Note. I hate the.

      }
      elseif

    instead of

      }  elseif

    but that part of the Drupal standard. http://drupal.org/coding-standards#controlstruct

    #2

    Posted by TKS on August 3, 2009 at 7:32pm

    +1 for this -- I was just about to start rooting around for ways to provide multiple blocks per vocabulary. Thanks miiimooo!

    Testing now...

    #3

    Posted by TKS on August 5, 2009 at 4:01am
    Status:needs review» reviewed & tested by the community

    Both the patch and the new functionality work like a charm...

    #4

    Posted by James Andres on January 29, 2010 at 3:44pm

    Works wonderfully, commit please? :-)

    #5

    Posted by rmiddle on July 5, 2011 at 2:23am
    Status:reviewed & tested by the community» closed (won't fix)

    1.x branch is no longer supported. Sorry I ended up not getting this committed before the 2.x branch was created.

    Thanks
    Robert

    nobody click here