#8221 closed enhancement (fixed)
Remove irrelevant “tags” field from support forum review forms
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Support Forums | Keywords: | has-patch |
| Cc: |
Description
The review form currently includes a “tags” field inherited from bbPress topic functionality, which is not relevant in the context of reviews and leads to confusing UX.
Attachments (4)
Change History (9)
#2
@
5 weeks ago
@bor0 observations:
bbp_*is a bbPress filter, but this is a custom filter. I suggest usingwporg_bbp_instead. existing bbp_ uses within the file are because the template is copied from bbPress.add_filter( 'bbp_topic_form_show_tags', array( $this, 'hide_topic_form_tags' ) );having these be negated reads weirdly, I'd rename the function to 'show_topic_form_tags' instead, returning false explicitly for reviews.'reviews' === bbp_get_view_id()exists within one of your branches where you're hiding it, so it's a little obtuse why it's there.
Finally; bbp_allow_topic_tags() has a filter (named bbp_allow_topic_tags).. so this is duplicating that needlessly :)
I would:
- Remove the
'reviews' === bbp_get_view_id()branch and just have Topic Tags string - Use the
bbp_allow_topic_tagsfilter - Wrap the unwrapped code in
bbp_allow_topic_tags()
I might've missed why you didn't go that route though, as I know there's some globals that can be weird in bbPress.
#3
@
5 weeks ago
If 8221.2.patch works (I haven't tested, but visually reviewed), ship it :)
#4
@
5 weeks ago
- Owner set to bor0
- Resolution set to fixed
- Status changed from new to closed
In 14797:
This ticket was mentioned in Slack in #meta by dd32. View the logs.
5 weeks ago
Note: See
TracTickets for help on using
tickets.
Regular forum post - tags still remain