WordPress.org

Make WordPress Core

Opened 9 years ago

Closed 4 years ago

#19628 closed feature request (worksforme)

FEATURE REQUEST: std deviation option for wp_tag_cloud

Reported by: bhoogterp Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.3
Component: Taxonomy Keywords: needs-patch
Focuses: Cc:

Description

Feature Request

Add a std deviation, logarithmic, or other non-linear algorithm for generating tag cloud sizes... I have a sample set containing approximately 500 tags, with two tags which fall in the 100 posts range, whereas most tags end up with less than 20. I would still like the two tags to show up, and to show up the largest, and a simple std deviation (66% show up in 1 std dev, 96% or so in the 2nd, etc) or logarithmic algorigm for calculating tag element sizes, based on the sample set.

Change History (5)

#1 @solarissmoke
9 years ago

  • Keywords dev-feedback added

This sounds like plugin material to me... there are so many possible ways that people might want to tweak their tag clouds.

#2 @nacin
7 years ago

  • Component changed from General to Taxonomy

#3 @boonebgorges
6 years ago

  • Keywords needs-patch added; dev-feedback removed
  • Milestone changed from Awaiting Review to Future Release

I think this is a pretty cool idea, and would arguably be a replacement for (rather than an addition to) the current tag cloud logic. It'd be helpful to get not only a patch, but some sample data that shows what the font-size distributions would look like with different data sets (so we can see, at a glance, how the proposed changes will differ from the linear distribution we currently use).

#4 @chriscct7
5 years ago

  • Severity changed from minor to normal

#5 @swissspidy
4 years ago

  • Milestone Future Release deleted
  • Resolution set to worksforme
  • Status changed from new to closed

In [11894], default_topic_count_scale() (uses log10()) was added as a default callback to wp_generate_tag_cloud(). A custom topic_count_scale_callback can be added by plugins. Considering that the default callback uses a logarithm already and this ticket never got any real traction, closing it seems appropriate.

Note: See TracTickets for help on using tickets.