Make WordPress Core

Opened 3 months ago

Closed 3 months ago

#64343 closed defect (bug) (invalid)

fatal errors after updating to 6.9

Reported by: bdubb's profile bdubb Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: Cc:

Description

nothing works now. admin/front end. just broken

Fatal error: Uncaught Error: Call to undefined function wp_is_valid_utf8() in /var/www/html/wp-includes/formatting.php:2287

Attachments (1)

Screenshot from 2025-12-03 13-30-22.png (112.4 KB) - added by bdubb 3 months ago.
screenshot - results of grep search for missing function

Download all attachments as: .zip

Change History (5)

@bdubb
3 months ago

screenshot - results of grep search for missing function

#1 @threadi
3 months ago

  • Keywords reporter-feedback added; needs-patch removed

hi @bdubb, welcome to Trac and thank you for your concern. Unfortunately, it is not possible for me to reproduce the problem described, e.g. via the Playground. Please make sure that your problem occurs in a pure WordPress without any plugins and with standard themes. If so, describe in more detail how you can reproduce it.

If you need general support, please contact the support forum: ​https://wordpress.org/support/forums/

#2 @sabernhardt
3 months ago

Could you check for wp-includes/utf8.php in the html directory? That new file might have failed to install properly there.

#3 @bdubb
3 months ago

Here's what happened:

Update failed to update wp-settings.php in root. Which contained the require for utf8.php.

Manual update and I'm back in business. Sorry for the confusion. Thx for the thoughtful responses.

B

#4 @jorbin
3 months ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Severity changed from critical to normal
  • Status changed from new to closed
  • Version 6.9 deleted

Glad to hear it is now working and thanks for following up @bdubb! I'm closing this as invalid which is the unfriendly term used to say it was resolved in a way that didn't find an issue in the Core WordPress software.

Note: See TracTickets for help on using tickets.