-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playground is creating a fatal error in site health #121
Comments
The function call to Because WordPress 6.6 is not released yet, it is still shown in the documentation (just search for This function was removed with this commit: Ticket: https://core.trac.wordpress.org/ticket/60096 (Milestone 6.6) This explains why there is a fatal error. As Unsure how to proceed here. This function is already removed, so this fatal error will disappear with WordPress 6.6. I don't know if this is something you want to backport. If yes, this would need a safeguard, to check if there is a MySQL/MariaDB or a SQLite database. |
To prove my findings. Playground with WordPress 6.6 (beta 3 at the moment) is not having this error anymore: |
Now that WP 6.6 has been released, I believe we can close this one 👍 |
Steps to reproduce:
Here are the logs:
Not sure what is causing this ... but maybe it has to do with
$wpdb->get_var( 'SELECT VERSION()' );
not working on SQLite.https://github.com/WordPress/WordPress/blob/master/wp-admin/includes/class-wp-site-health.php#L212
We could polyfill this with a user defined function.
More ideas here: https://stackoverflow.com/questions/9646353/how-to-find-database-file-version
The text was updated successfully, but these errors were encountered: