Better Topic Tag Management

[GautamGupta]

Proposals:

1. Allow topic tag description to be edited from the front-end (and probably show it too).
2. Replace the edit link in the admin section to point to the front end or make the topic tag edit screen in the admin section imitate the front end counterpart.
3. Bulk actions for merging tags. Related: #1243 (for standalone)

[johnjamesjacoby]

No time in 2.1. Moving to future release. Should reconsider for 2.2.

[netweb]

Replying to GautamGupta:

Proposals:

1. Allow topic tag description to be edited from the front-end (and probably show it too).

It was already being shown if the topic tag had a description.

In 1613.diff the topic tag descriptions are now wrapped in a bbp-template-notice info template similar to the single topic description. It is also only displayed if the topic tag does actually have a description.

2. Replace the edit link in the admin section to point to the front end or make the topic tag edit screen in the admin section imitate the front end counterpart.

Our current philosophy surrounding back vs front has been if we are in the back end stay in the back end, if we are in the front end stay in the front end.

3. Bulk actions for merging tags. Related: #1243 (for standalone)

Bulk actions cannot be added until ​#WordPress18449

MZAWeb ​http://bbpress.trac.wordpress.org/ticket/2246#comment:8
Core hardcodes which WP_List_Table child is used in every instance (see function _get_list_table )

Until this is resolved ​http://core.trac.wordpress.org/ticket/18449 doesn't make much sense to do this ticket, because we'll need to do some ugly hacks to make it work.

Notes on the 1613.diff patch:

bbp_topic_tag_description is only called in content-archive-topic.php and content-topic-tag-edit.php templates so we could change the default classes in /includes/topics/template.php rather than in the templates, can decide before committing.

[johnjamesjacoby]

In 5310:

Allow topic-tag descriptions to be edited theme-side. Props netweb. Fixes #1613.

[johnjamesjacoby]

Let's move bulk actions into a separate ticket.