![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 17 years ago
Closed 17 years ago
#10315 closed feature request (fixed)
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: | Focuses: |
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 (3)
Change History (16)
#2
@
17 years ago
- Resolution → wontfix
- Status new → closed
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.
#3
@
17 years ago
- Keywords needs-patch added
- Resolution wontfix
- Status closed → reopened
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.
#4
@
17 years ago
Can you please name some other WordPress API functions having such a functionality already? Or is this just a personal preference of yours?
#5
@
17 years ago
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.
@
17 years ago
Updated patch so that seperator is the only seperator and defaults to the default seperator ("\n").
#7
@
17 years ago
- Milestone 2.9 → 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?
#8
@
17 years ago
- Milestone 2.8.2 → 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)
#9
@
17 years ago
- Keywords needs-patch added; has-patch removed
- Milestone 2.9 → Future Release
Patch is stale needs updating.
#10
@
17 years ago
- Keywords has-patch added; needs-patch removed
- Milestone Future Release → 2.9
- Version 2.8 → 2.9
Refreshed patch. :)
using "between" would be more inline with other functions.