Ticket #10315 (closed feature request: fixed)

Opened 3 years ago

Last modified 2 years ago

Add parameter "separator" to "wp_tag_cloud()"

Reported by: ramiy Owned by:
Priority: normal Milestone: 2.9
Component: Themes Version: 2.9
Severity: normal Keywords: has-patch
Cc: r_a_m_i@…

Description

When using wp_tag_cloud('format=flat') the result is a list of tags separated by whitespace.

The problem: We can't change the whitespace between the tags.

The solution: Adding the "separator" parameter will give us some control over the separator string.

Attachments

10315.patch Download (1.4 KB) - added by ramiy 3 years ago.
10315.2.patch Download (1.4 KB) - added by hakre 3 years ago.
Updated patch so that seperator is the only seperator and defaults to the default seperator ("\n").
wp_tag_cloud.separator.10315.diff Download (1.5 KB) - added by filosofo 2 years ago.

Change History

using "between" would be more inline with other functions.

  • Status changed from new to closed
  • Resolution set to wontfix

there is the 'format=array' options. use that to implode with the seperator char of your choice.

somewhat related: #5172

IMHO no need to re-invent the wheel here for a behavior in for some time, so I close this as wontfix. A wordaround is provided anyway.

  • Keywords needs-patch added
  • Status changed from closed to reopened
  • Resolution wontfix deleted

The problem is that not every one know how to use 'format=array', this is not user friendly!

The "separator" parameter is the most elegant solution to this problem.

Can you please name some other WordPress API functions having such a functionality already? Or is this just a personal preference of yours?

First of all, this is not a personal preference.

Adding this feature will make WordPress not only developer-friendly but also user-friendly and desingner-friendly. This is not a big technological improvement, this is a tag-cloud output design.

Instead of the current obsolete whitespace between tags blogers can change it to a minus sign or a nice image. Adding a widget control will allow users to edit the separator in the widget sub-panel and will make it even simpler and easier.

ramiy3 years ago

  • Keywords has-patch added; needs-patch removed

hakre3 years ago

Updated patch so that seperator is the only seperator and defaults to the default seperator ("\n").

  • Milestone changed from 2.9 to 2.8.2

Default seperator should be "\n" then. Updated the patch, credits to ramiy.

Additional note: wp_tag_cloud and wp_generate_tag_cloud share a decent amount of code (for example the default values) which does a bit fishy to me. Someone willing to clean that up?

comment:8   dd323 years ago

  • Milestone changed from 2.8.2 to 2.9

Milestone: Future release pending patch for enhancements, Current-trunk upon patch being added for consideration, point release back-porting at commiters discretion. (Generic reply for when I change the milestone)

  • Keywords needs-patch added; has-patch removed
  • Milestone changed from 2.9 to Future Release

Patch is stale needs updating.

  • Keywords has-patch added; needs-patch removed
  • Version changed from 2.8 to 2.9
  • Milestone changed from Future Release to 2.9

Refreshed patch. :)

comment:11 follow-up: ↓ 12   westi2 years ago

Patch fail - removes code :-(

comment:12 in reply to: ↑ 11   filosofo2 years ago

Replying to westi:

Patch fail - removes code :-(

Whoops. Updated patch with fix.

  • Status changed from reopened to closed
  • Resolution set to fixed

(In [12014]) Allow the separator in wp_tag_cloud and wp_generate_tag_cloud to be specified. Fixes #10315 props ramiy and filosofo.

Note: See TracTickets for help on using tickets.