I believe the Latest trunk is supposed to suppress database errors before the tables are created. But yes, The "official" RC1 did log those errors, The current trunk however, shouldnt.
On Wed, 26 Mar 2008 12:27:51 +1100, Stephen Rider <[EMAIL PROTECTED]> wrote: > Hi -- > > First off, I'm using a somewhat modified system, so if somebody else > could confirm this on a "standard" install I would appreciate. > > When running the "5 minute install" in 2.5 RC1, it appears to hit the > PHP logs with errors similar to the following: > > [25-Mar-2008 20:17:51] WordPress database error Table > 'stride_MySQL.wp_options' doesn't exist for query SELECT option_name, > option_value FROM wp_options WHERE autoload = 'yes' made by > wp_load_alloptions > > I get what the errors are -- it's not finding the tables because they > don't exist yet. But should we really be hitting the logs with errors > for essentially expected behavior? > > Stephen > _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
