Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#49796 closed defect (bug) (invalid)

wpmu_new_blog is deprecated since version 5.1.0 warning

Reported by: oldrup's profile oldrup Owned by:
Milestone: Priority: normal
Severity: minor Version: 5.4
Component: Networks and Sites Keywords:
Focuses: Cc:

Description

Hey. Whenever I'm creating new sites on my multisite installation, I get the following warnings (since I activated debugging due to another issue).

It seems that WordPress uses a deprecated function when new sites are created. The site is created just fine, its just warnings.

Deprecated: wpmu_new_blog is deprecated since version 5.1.0! Use wp_insert_site instead. in /home/oldrupdk/labs.oldrup.net/wp-includes/functions.php on line 5088

Warning: Cannot modify header information - headers already sent by (output started at /home/oldrupdk/labs.oldrup.net/wp-includes/functions.php:5088) in /home/oldrupdk/labs.oldrup.net/wp-includes/pluggable.php on line 1281

Warning: Cannot modify header information - headers already sent by (output started at /home/oldrupdk/labs.oldrup.net/wp-includes/functions.php:5088) in /home/oldrupdk/labs.oldrup.net/wp-includes/pluggable.php on line 1284

Change History (2)

#1 @swissspidy
5 years ago

  • Component changed from General to Networks and Sites
  • Focuses multisite coding-standards removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Hi there

You appear to be using some plugin that hooks into the wpmu_new_blog action, which has been deprecated . That's why there is this message Deprecated: wpmu_new_blog is deprecated since version 5.1.0! Use wp_insert_site instead.. The file location might be misleading, as it's just the location where the warning has been triggered, and not the location of the actual caller.

#2 @oldrup
4 years ago

Hm. Thanks. Learned something new. Even though no of the plugins were activated, the error triggered. Weeded out in no-critical plugins, and error is gone. Thank you for your help :)

Note: See TracTickets for help on using tickets.