Opened 10 years ago
Closed 10 years ago
#38174 closed defect (bug) (fixed)
Cannot add a new category from the post edit screen
| Reported by: | littler.chicken | Owned by: | obenland |
|---|---|---|---|
| Priority: | high | Milestone: | 4.7 |
| Component: | Taxonomy | Version: | 4.7 |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: | administration |
Description
In trunk, when creating or editing a post (or CPT), adding a new category from within the post editor appears to be broken. Only hierarchical taxonomies are affected--it is possible to add new tags, but any taxonomy which behaves like a category has the same issue.
Creating a new category from the Categories screen works as expected, and any existing category can be selected from the post editor, it's just that creating a new one doesn't work.
I'm not seeing any JS errors, just nothing happens when the "Add New Category" button is clicked after entering the new category/term name. It does not matter if there is a parent term selected.
Attachments (1)
Change History (5)
#2
@
10 years ago
- Focuses administration added
- Keywords has-patch needs-testing added
- Milestone Awaiting Review → 4.7
- Owner set to
- Priority normal → high
- Status new → assigned
cc @obenland
#3
in reply to: ↑ 1
@
10 years ago
- Keywords needs-testing removed
Replying to dlh:
Restoring the previous version of
init()seems to fix the issue. But as I'm not certain whyinit()was changed, going back might cause side-effects that I've overlooked, if it's even the right course to begin with.
It should be, I'm pretty sure I just misread what init() does there.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I can replicate this behavior, and I think it might be traceable to r38599.
Previously, the call to
process()insideinit()didn't pass the currentelement, so, insideprocess(),$elementwould be set to$( document )while registering event handlers.Restoring the previous version of
init()seems to fix the issue. But as I'm not certain whyinit()was changed, going back might cause side-effects that I've overlooked, if it's even the right course to begin with.