When all available terms (tags) are already shown, there is no use for the "more tags" link in the bottom right corner

Comments

jurgenhaas’s picture

I have patched the tagadelic.module by replacing

$blocks['content'] .= theme('tagadelic_more', $voc->vid);//add more link

with

if (count($tags) == variable_get('tagadelic_block_tags_'. $delta, 12)) {
   $blocks['content'] .= theme('tagadelic_more', $voc->vid);//add more link
}

This works really nice.

pfaocle’s picture

Version: 5.x-1.x-dev » master
Status: Active » Needs review
StatusFileSize
new1.06 KB

Features into HEAD, I guess? Patch for suggestion attached, not tested on my side.

pfaocle’s picture

(Ignore me)

Bèr Kessels’s picture

First priority is a DPL6 release.
Then I will open up head for development on new features and bugfixes.

add1sun’s picture

Just reporting back that this patch applies with fuzz against 6x-1.0 and works as expected.

Bèr Kessels’s picture

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

I recall having duscussed this before, but fail to find that thread:
Why do you check if (count($tags) == variable_get('tagadelic_block_tags_'. $delta, 12)) { and not if (count($tags) => variable_get('tagadelic_block_tags_'. $delta, 12)) {

I would say that the *more* must show in case there are the same, or more tags in the cloud then shown in the block. Is that correct?

cpugeniusmv’s picture

I think he used == because $tags will never have more than 12 (or whatever the setting contains) elements (the query uses db_query_range to limit the number of results).

That works fine, but I think >= is more readable and unambiguous.

pfaocle’s picture

Version: master » 6.x-1.x-dev
Status: Postponed (maintainer needs more info) » Needs work

Bumping.

Bèr Kessels’s picture

Leafish, can you summarise what work needs to be done still?

pfaocle’s picture

Status: Needs work » Needs review
StatusFileSize
new1.07 KB

Well, both the patch above and the one attached here work - this one uses ">=" for the reasons in #7. I'm currently using this patch on a single Drupal 6 blog site and its doing the trick.

Bèr Kessels’s picture

Status: Needs review » Reviewed & tested by the community

looks good.

jstoller’s picture

+1

Bèr Kessels’s picture

Status: Reviewed & tested by the community » Fixed

Committed to DRUPAL-6-1.
Is not in the DRUPAL-6--1-1 release, though, that was released yesterday.
Will be in the next bugfix release and off course in the -dev version.

Also merged into HEAD.

Status: Fixed » Closed (fixed)

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