Making WordPress.org

Opened 10 months ago

Closed 10 months ago

Last modified 10 months ago

#7080 closed defect (bug) (fixed)

Odd data for the MySQL/MariaDB versions on WordPress.org stats

Reported by: l1nuxjedi's profile l1nuxjedi Owned by:
Milestone: Priority: normal
Component: API Keywords:
Cc:

Description

On the WordPress.org stats page (https://en-gb.wordpress.org/about/stats/) the data seems incorrect for the following reasons:

  1. There are no 10.10 / 10.11 versions listed. MariaDB 10.11 is an LTS and the default in Debian Bookworm. So, I would expect at least 1 user.
  1. There is an 11.5 listed. There is no MySQL / MariaDB 11.5
  1. In the UI frontend it appears that 12.0 is filtered out, this will be a real version in the coming years (https://github.com/WordPress/wordpress.org/blob/caf9d36e647382c6ea83e7cc6444a0a23a98c5e7/wordpress.org/public_html/wp-content/themes/pub/wporg-main/js/page-stats.js#L41)

The regex filter in WordPress used to send this data to the API appears to be correct, so I think this is a bug in the API side. Either data collection or when rendering the JSON for the pie chart.

Ideally, in addition, it would be nice if there was a separation or indication between MySQL and MariaDB since 5.x could mean either. Or at least the title change to MySQL / MariaDB versions.

Ideally there should be a separation of MariaDB and MySQL here, or at least the title changed to MySQL / MariaDB.

Change History (15)

This ticket was mentioned in Slack in #hosting by javier. View the logs.


10 months ago

#2 follow-up: @l1nuxjedi
10 months ago

Also a 9.6 version, not sure what that is either.

#3 @adamwood
10 months ago

Please note that the main (non localized) page at https://wordpress.org/about/stats/ is running a newer version of the frontend script. The relevant line for the v12.0 omission is https://github.com/WordPress/wporg-main-2022/blob/trunk/source/wp-content/themes/wporg-main-2022/js/page-stats.js#L41

Last edited 10 months ago by adamwood (previous) (diff)

#4 @dd32
10 months ago

These stats are a bit ambiguous, WordPress reports the Database version but doesn't actually identify the Database Engine / Server. So installs of MySQL/MariaDB/MsSQL/Sqlite/Percona Server/etc all report as a "MySQL version".

This is what is sent to WordPress.org:
https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/update.php#L76-L82
which is generated from this:
https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/class-wpdb.php#L4101-L4111

There are no 10.10 / 10.11 versions listed.

Thanks, it looks like it was being treated as a decimal version, so 10.10/10.11 were being counted in 10.1. This will be fixed shortly (and retroactively where possible)

There is an 11.5 listed. There is no MySQL / MariaDB 11.5

The most common version identifier for 11.5 that is reported is 11.5.30, which google only seems to suggest a Plesk version. I'm guessing there's a MySQL-like server instance included on a popular host that is showing the OS/Plesk version identifier rather than the actual SQL server version.

In the UI frontend it appears that 12.0 is filtered out, this will be a real version in the coming years

It looks safe to remove this line now. Between 2016 -> 2019 version 12.0.200 was being reported as a DB version, which I believe was a truncated Microsoft SQL version identifier of 12.0.2000.8.

#6 @dd32
10 months ago

  • Resolution set to fixed
  • Status changed from new to closed
  • 10.10 + 10.11 are showing up correctly now, rather than grouping in 10.1
  • 11.5 should vanish in the next few days
  • 12.0 no longer being hidden in the JS

#7 @dd32
10 months ago

I've filed a core ticket for some followup changes that could be used to improve the w.org data: https://core.trac.wordpress.org/ticket/58584 Some input there would be appreciated.

#8 in reply to: ↑ 2 @dd32
10 months ago

Replying to l1nuxjedi:

Also a 9.6 version, not sure what that is either.

Missed this comment.

That's showing primarily as 9.6.0, I had previously assumed this was PostgreSQL but based on the age of that version and the above core ticket, I suspect it's just badly parsing a version identifier.

Based on the minimal data I have access to, I can't determine from the data what that would be referring to.

#9 @l1nuxjedi
10 months ago

Thank you for your work on this.

This ticket was mentioned in Slack in #hosting by crixu. View the logs.


10 months ago

This ticket was mentioned in Slack in #hosting by jadonn. View the logs.


10 months ago

This ticket was mentioned in Slack in #meta by danielblack. View the logs.


10 months ago

This ticket was mentioned in Slack in #hosting by dd32. View the logs.


10 months ago

This ticket was mentioned in Slack in #hosting by javier. View the logs.


10 months ago

This ticket was mentioned in Slack in #hosting by amykamala. View the logs.


10 months ago

Note: See TracTickets for help on using tickets.