WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 3 years ago

#25570 closed defect (bug) (wontfix)

Add New term to category or tag via ajax only resets text input fields

Reported by: valllabh Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Taxonomy Keywords: needs-patch
Focuses: javascript Cc:

Description

Add New term to category or tag via ajax only resets text input fields.
If any plugin is adding extra fields with checkbox or radio button or any other the input field other than text,
tags.js only resets text fields after term ajax post operation.

Attachments (1)

tags.js (332 bytes) - added by valllabh 8 years ago.

Download all attachments as: .zip

Change History (6)

#1 @valllabh
8 years ago

  • Keywords has-patch added; needs-patch removed

@valllabh
8 years ago

#2 @wonderboymusic
8 years ago

  • Focuses javascript added
  • Keywords needs-refresh added
  • Milestone changed from Awaiting Review to Future Release

Needs a proper .diff or .patch file, please

#3 @helen
7 years ago

  • Keywords needs-patch added; has-patch needs-refresh removed

#4 @tyxla
6 years ago

  • Keywords 2nd-opinion added

Not sure if this is a good idea.
What if any of the checkbox or radio needs to be enabled by default?
Then this line will wrongly reset the checkbox/radio field.

Perhaps a better alternative here is to trigger a custom event, allowing developers to customize the custom term fields reset actions as they wish.

Second opinion would be nice here.

#5 @chriscct7
3 years ago

  • Keywords 2nd-opinion removed
  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Closing ticket as wontfix.

This condition would be used by an extremely limited usecase, for which a cursory search of the WordPress plugins directory did not return any suggestions for. Such a plugin implementing it would likely have to implement a custom ajax handler anyways in order to make the user experience make any sense.

For the reason of having an extremely limited (if not for a handful of WordPress users) and lack of evidence of need, closing this ticket as wontfix.

Note: See TracTickets for help on using tickets.