-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Undefined property: wpdb::$blog_versions in C:\inetpub\WP5_GC_2020_01\wp-includes\wp-db.php on line 748 #493
Comments
You might have something else going on this time. I can't find $blog_versions at line 748, and so far can't find it anywhere in the file. |
Hey Patrick: It did not occur with every page load as the other issue. This occurred only once. I believe it was on a update of plugins or themes. |
@PHuhn I'm facing the same issue in WordPress 6.0.3 & WordPress 6.2 but let me tell you I face this issue once I complete the setup of Easy WP SMTP plugin in both setups. Also, It occurs on every page. |
Hey look at this post I created about a similar problem: |
Hey Patrick: I got this again, this time in a different PHP file (class-wpdb.php). I believe I was logging in for the first time after deleting all of the tables.
I corrected it by adding a declaration at line 60:
|
I'm still trying to figure out how/why this is being a problem for you. I can't find any reference to blog_versions in class-wpdb.php in either WP Core or PN. Have you found where it is being referenced yet? |
It tells you the line #. I believe it is dynamic. It is not a part of the WordPress code base. You can google it and find the value. |
Just started a completely fresh on-prem install under Windows 2019 latest, PHP-8.2.6 and sqlsrv 5.11.0. I didn't git clone the repo but used the deployment from the zip file. Same error. Same fix. Let me know if there's anyway I can help provide more info also. |
I'm running ProjectNami on my Windows 10 laptop. I updated to 3.0.3 (WordPress 6.0.3) on a test site and I'm getting a notice as follows:
I am assuming it is similar to the other one I reported.
The text was updated successfully, but these errors were encountered: