Making WordPress.org

Opened 7 days ago

Closed 3 days ago

#8308 closed enhancement (invalid)

Counts mismatch on the wordpress.org photos directory

Reported by: hurairah922's profile hurairah922 Owned by:
Milestone: Priority: normal
Component: Photo Directory Keywords:
Cc:

Description

I recently uploaded another photo to WordPress.org Photos, and it has been published successfully.

However, I noticed a mismatch between the photo count shown on my WordPress.org profile and the count shown in the Photos Directory.

I’m attaching screenshots for reference. Could you please check why the counts are different?

https://abuhurarrah.com/wp-content/uploads/2026/06/Screenshot-from-2026-06-16-22-04-06.png
https://abuhurarrah.com/wp-content/uploads/2026/06/Screenshot-from-2026-06-16-22-04-15.png

Attachments (1)

Screenshot from 2026-06-16 22-12-59.png (734.7 KB) - added by hurairah922 7 days ago.

Download all attachments as: .zip

Change History (4)

#1 @benniledl
7 days ago

This page is probably heavily cached and it might take some time to update.

Please check back later and if the issue is resolved you can close the ticket.

#2 @hurairah922
7 days ago

  • Type changed from defect (bug) to enhancement

Thanks for the clarification.

I understand that the page may be heavily cached and that the count will likely update later. However, this seems like an event where the relevant cache could be refreshed or invalidated automatically when a new photo is published.

From a contributor's perspective, seeing accurate contribution counts immediately helps build confidence that the platform is responding correctly to their activity. Small inconsistencies can sometimes create confusion, especially for new contributors who may not realize the delay is caused by caching.

Not a critical issue, but it may be worth considering whether the cache refresh strategy for these profile statistics can be improved.

#3 @mkrndmane
3 days ago

  • Resolution set to invalid
  • Status changed from new to closed

Closing this ticket, as the reported issue was due to a caching issue and is no longer reproducible.

Note: See TracTickets for help on using tickets.