Make WordPress Core

Opened 13 years ago

Last modified 7 years ago

#18553 new defect (bug)

Counting of categories doesn't work without refreshing?

Reported by: jonezjea's profile jonezjea Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 3.2.1
Component: Taxonomy Keywords: has-patch
Focuses: administration Cc:


If you add a new category or delete one the number of total categories stays on the original number. For exemple, when you have 7 categories then in the corner it says '7 items'. When you delete one, you have 6 items but '7 items' is still displayed.

(Chrome 15.0.816)

1) Go to your categories
2) Add one and look to the number of items, IT WILL NOT CHANGE!

So this count for adding normal categories and child ones...

Attachments (3)

add_category_incorrect_striping.png (70.9 KB) - added by kurtpayne 13 years ago.
Adding multiple categories results in incorrect striping
add_category_usability_question.png (74.2 KB) - added by kurtpayne 13 years ago.
Explanation of usability question in comment
18553.patch (1.4 KB) - added by gk.loveweb 7 years ago.

Download all attachments as: .zip

Change History (12)

13 years ago

Adding multiple categories results in incorrect striping

13 years ago

Explanation of usability question in comment

#1 @kurtpayne
13 years ago

  • Cc kpayne@… added
  • Component changed from Editor to Taxonomy
  • Keywords ux-feedback added

I looked into this and was able to duplicate the problem. I also found that the table striping doesn't update correctly when adding multiple categories. See add_category_incorrect_striping.png for an example.

It seems like this defect would cover updating the striping and total category count when deleting categories.

I'm happy to own this, but I would like usability feedback on one issue. If the user has entered a search query, should the number of search result matches, or the number categories displayed in the table? See add_category_usability_question.png for an explanation.

#2 @jonezjea
13 years ago

that second screenshot is what I tryed to explain in my bad English. Indeed the screenshots explains it way better then I did!

Last edited 13 years ago by jonezjea (previous) (diff)

#3 @wonderboymusic
10 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to Future Release

This makes a pretty good case for using JS views for list tables, which also sounds like it would be nightmarish - nevertheless, there are a couple of things here that could be patched

#4 @SergeyBiryukov
10 years ago

#24809 was marked as a duplicate.

#5 @SergeyBiryukov
10 years ago

  • Focuses administration added

#6 @chriscct7
9 years ago

  • Severity changed from minor to normal

This ticket was mentioned in Slack in #design by karmatosed. View the logs.

7 years ago

#8 @karmatosed
7 years ago

  • Keywords ux-feedback removed

We discussed this in the weekly triage session for design and removing the tag as this is way this works currently. Although it's worth saying JS tables would be amazingly good.

7 years ago

#9 @gk.loveweb
7 years ago

  • Keywords has-patch added; needs-patch removed

@all Please check and let me know

Note: See TracTickets for help on using tickets.