Make WordPress Core

Opened 7 months ago

Last modified 7 months ago

#58983 new defect (bug)

Old error message from 5.1 reappeared in 6.2.2

Reported by: namithjawahar's profile namith.jawahar Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 6.2.2
Component: Networks and Sites Keywords:
Focuses: multisite Cc:

Description (last modified by sabernhardt)

The following error message appears in multisite installations after upgrade to 6.2.2
Performing the network upgrade doesnt seem to get rid of the message

Notice: Function wp_check_site_meta_support_prefilter was called incorrectly. The wp_blogmeta table is not installed. Please run the network database upgrade. Please see Debugging in WordPress for more information. (This message was added in version 5.1.0.) in .../wp-includes/functions.php on line 5865

The table itself doesnt seem to exist in the database nor is it being created. Its no affecting any multi site functionality though.

The hosting is Wp-Engine if that matters.

Change History (6)

#1 @sabernhardt
7 months ago

  • Component changed from General to Networks and Sites
  • Description modified (diff)
  • Focuses multisite added

#2 follow-up: @rajinsharwar
7 months ago

Here's a related ticket: #46167

#3 follow-up: @rajinsharwar
7 months ago

Can you try these two steps:

  1. Visit the wp-admin/upgrade.php, and check if the network DB is up to date.
  2. Try to create the wp_blogmate table using the below query, and check if it resolves the issue:
CREATE TABLE IF NOT EXISTS wp_blogmeta (
meta_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
blog_id bigint(20) NOT NULL DEFAULT ‘0’,
meta_key varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
meta_value longtext COLLATE utf8mb4_unicode_520_ci,
PRIMARY KEY (meta_id),
KEY meta_key (meta_key(191)),
KEY blog_id (blog_id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci AUTO_INCREMENT=1 ;

More details: https://wordpress.org/support/topic/not-creating-table-wp-blogmeta/page/2/#post-11265255

Version 0, edited 7 months ago by rajinsharwar (next)

#4 in reply to: ↑ 2 @namith.jawahar
7 months ago

Replying to rajinsharwar:

Here's a related ticket: #46167

The warning message was introduced as part of the fix for this ticket ASFAIK.
This ticket is about the same warning message being trigger by error.

#5 in reply to: ↑ 3 @namith.jawahar
7 months ago

Replying to rajinsharwar:

Can you try these two steps:

  1. Visit the wp-admin/network/upgrade.php, and check if the network DB is up to date.
  2. Try to create the wp_blogmate table using the below query, and check if it resolves the issue:
CREATE TABLE IF NOT EXISTS wp_blogmeta (
meta_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
blog_id bigint(20) NOT NULL DEFAULT ‘0’,
meta_key varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
meta_value longtext COLLATE utf8mb4_unicode_520_ci,
PRIMARY KEY (meta_id),
KEY meta_key (meta_key(191)),
KEY blog_id (blog_id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci AUTO_INCREMENT=1 ;

More details: https://wordpress.org/support/topic/not-creating-table-wp-blogmeta/page/2/#post-11265255

Already tried it, it doesn't help.

Again this might be related to the specific configuration that wp-engine uses. The problem is the error shouldn't be triggered as far as a mechanism is handling multisites without anyone altering the core.

#6 @NekoJonez
7 months ago

For those curious, that line in the error ... /wp-includes/functions.php on line 5865 is actually the line that's showing from which version it appeared in.

Note: See TracTickets for help on using tickets.