Make WordPress Core

Opened 16 years ago

Closed 15 years ago

#8502 closed defect (bug) (fixed)

Dashboard comments approval doesn't update right now correctly

Reported by: westi's profile westi Owned by: nbachiyski's profile nbachiyski
Milestone: 2.9 Priority: normal
Severity: normal Version: 2.7
Component: I18N Keywords: needs-patch
Focuses: Cc:

Description

Dashboard comments approval doesn't update right now correctly

Unapproved count changes, comment bubble changes approved count doesn't

See attached image

Attachments (1)

Picture 1.png (29.6 KB) - added by westi 16 years ago.
Dashboard comments approval doesn't update right now correctly

Download all attachments as: .zip

Change History (9)

@westi
16 years ago

Dashboard comments approval doesn't update right now correctly

#1 follow-up: @azaozz
16 years ago

  • Component changed from UI to i18n
  • Owner set to nbachiyski

That could easily be added, but there's a localization issue when updating the numbers from Javascript.

For most languages the difference is only in the thousands separator 10,000 10.000 or 10 000, so the lower numbers of Spam and Pending are not affected. For the rest the problem is bigger.

Perhaps we could turn the update from js off and do it only on page reload when the numbers can be localized properly.

#2 @markjaquith
16 years ago

  • Milestone changed from 2.7 to 2.8

We need a better global solution for this, but no time for 2.7.

#3 @Denis-de-Bernardy
16 years ago

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

punting...

#4 in reply to: ↑ 1 @Viper007Bond
16 years ago

Replying to azaozz:

That could easily be added, but there's a localization issue when updating the numbers from Javascript.

Why not just use AJAX? On comment change via dashboard, refresh the counts (or even the whole "Right Now" widget via AJAX. That way PHP can handle generating the counts and everything.

#6 @Denis-de-Bernardy
16 years ago

  • Milestone changed from Future Release to 2.9

#7 @caesarsgrunt
16 years ago

Why not just leave the thousands separator out altogether? I believe this is acceptable in most locales, at least for numbers below 10,000, And it's certainly better to have an incorrectly formatted number than to have the wrong number.

Also, the localisation issue could conceivably affect the span and pending counts too, though it's true that they are unlikely to reach 1000...

#8 @azaozz
15 years ago

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.