WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 3 years ago

#5154 closed enhancement (worksforme)

Allow the little more flexible tag-list in templates.

Reported by: hangy Owned by: westi
Milestone: Priority: low
Severity: normal Version: 2.3
Component: Template Keywords: needs-patch reporter-feedback needs-docs close
Focuses: Cc:

Description

I think the user should have a little more flexibility in giving out the tags of a specific post.

The patch attached basically provides the same functionality as a simple plugin I made (still pending at wordpress.org, for more information see Data Division), which is enabling the user to completely disable linking the tags or allowing a custom tag-URI to be used.

Attachments (1)

category-template.php.diff (1.7 KB) - added by hangy 7 years ago.

Download all attachments as: .zip

Change History (8)

hangy7 years ago

comment:1 westi7 years ago

  • Keywords reporter-feedback added; has-patch 2nd-opinion removed
  • Milestone changed from 2.3.1 to 2.5
  • Owner changed from anonymous to westi
  • Status changed from new to assigned
  • Version set to 2.3

What are you trying to achieve here exactly?

We already provide a way for the user to configure the base part of tag permalinks on the Permalinks option page at the bottom.

Could you provide a better description of the individual problems you are trying to solve.

comment:2 hangy7 years ago

The idea about making the_tags() a little more flexible:

a) Allow non-linked tags to be used somewhere (someone asked for this on #wordpress, because he wanted to use the tags in his meta-keywords, but this was not possible because they are linked).

b) Using a custom $taglink is not about different permalinks (diff. tag-base), but about having tags listed by the_tags() e. g. linked to a different site (http://technorati.com/tag/%tag% as an example).

comment:3 westi7 years ago

  • Keywords needs-docs added

comment:5 Denis-de-Bernardy5 years ago

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

comment:6 solarissmoke3 years ago

  • Keywords close added

This has been idle for 2 years - I think it's fair to say there's no traction/leave for plugins?

comment:7 scribu3 years ago

  • Milestone Future Release deleted
  • Resolution set to worksforme
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.