[wp-trac] [WordPress Trac] #63066: Warning when array passed to wp_check_invalid_utf8()

WordPress Trac noreply at wordpress.org
Wed Aug 13 21:11:39 UTC 2025


#63066: Warning when array passed to wp_check_invalid_utf8()
--------------------------+------------------------------
 Reporter:  leedxw        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.7.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by siliconforks):

 Replying to [comment:13 garrigan]:
 >
 > {{{
 >
 > Aug   12      12:42:40        staging 8/12/2025       12:42:40
 [error] 3046#3046:      *358    FastCGI sent    in      stderr: PHP
 message: should only be passing string; not array to
 wp_check_invalid_utf8(); PHP message: #0 /my-path/www/wp-includes/
 while   reading upstream,       client: 2001:,  server:
 ~^(.+)(\.)((james|jim)?garrigan.*)$,    request:        GET /wp-
 admin/customize.php HTTP/3.0,   upstream:       fastcgi://unix:/run/my-
 path/www.sock:,  referrer:       https://staging.my-domain.com/wp-admin/
 > Aug   12      12:42:40        staging 8/12/2025       12:42:40
 [error] 3046#3046:      *358    FastCGI sent    in      stderr:
 formatting.php(4702): wp_check_invalid_utf8(Array)
 >
 > }}}

 It looks like the stack trace is getting cut off for some reason...

 Maybe try this instead:

 Edit your `wp-config.php` file and find the `WP_DEBUG` line and change it
 to this:

 {{{
 define( 'WP_DEBUG', true );
 }}}

 Also add the following line:

 {{{
 define( 'WP_DEBUG_LOG', true );
 }}}

 Then visit the customizer again.  This should have the effect of creating
 a file named `wp-content/debug.log` containing the information needed to
 find the cause of the issue (it may show that a plugin is triggering
 this).

 Note: this configuration is not really recommended for production
 environments so I recommend changing it back as soon as you are done
 (i.e., set `WP_DEBUG` back to `false` and remove the `WP_DEBUG_LOG` line).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63066#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list