Not sure yet if this is a bug, or some thing I'm missing...

Logged in as admin, I've enabled the module, and added the 2 blocks (for Tags & ANY vocab) to the left bar. The blocks do not appear when I visit any tagged content. Could othe taxonomy related modules be interfering?

CommentFileSizeAuthor
#1 similarterms.disappearing.patch977 bytesRichard Blackborder

Comments

Richard Blackborder’s picture

Richard Blackborder commented
Status: Active » Needs review
StatusFileSize
new similarterms.disappearing.patch977 bytes

Did you configure the blocks on the block page and save the configured blocks? I did that and my blocks disappeared. I debugged it in the code and have attached a patch that fixes it.

Line 153 of similarterms.module:

      $types = variable_get('simterms_sametype_'. $vocid, false);
      if (($types !== false) && is_array($types) && ($types['0'] == NULL) ) {

After you've configured the block, $types will return an empty array, not false. This causes the query for filter by content type to trigger, with zero content types.

If anyone is not comfortable applying patches and needs a temporary fix, simply configure the block to filter by one or more content types.

rmiddle’s picture

rmiddle commented
Status: Needs review » Reviewed & tested by the community

Likeless,

I will get that applied shortly.

Thanks
Robert

rmiddle’s picture

rmiddle commented
Category: support » bug
akwala’s picture

akwala commented

Strangely enough, the block started appearing shortly after I posted here. Then, it stopped appearing, probably following block config changes. I just changed the content type filtering, as you suggested, and I now see the block.

izarco’s picture

izarco commented

I'm the same issue.
I apply the patch and not fix nothing.

izarco’s picture

izarco commented

I fix my problem disabling the cache block in Site Mantenement->Performance.
Thank's for all

rmiddle’s picture

rmiddle commented
Status: Reviewed & tested by the community » Fixed

Committed to CVS D6.

Status: Fixed » Closed (fixed)

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