Fix #41562. - #5

…p_user_settings()`.

The `wp_user_settings()` function calls the PHP native `setcookie()` function, the fifth parameter of which is the ''optional'' `$domain` parameter which expects a `string`.

A parameter being optional, however, does not automatically make it nullable.

As of PHP 8.1, passing `null` to a non-nullable PHP native function will generate a deprecation notice.

In this case, this function call yielded a `setcookie(): Passing null to parameter #5 ($domain) of type string is deprecated` notice.

Changing the `null` to an empty string fixes this without a backward compatibility break.

References:
* [https://www.php.net/manual/en/function.setcookie.php PHP Manual: setcookie()]
* [https://wiki.php.net/rfc/deprecate_null_to_scalar_internal_arg PHP RFC: Deprecate passing null to non-nullable arguments of internal functions]

Follow-up to [29478].

Props ocean90, shenyanzhi, meysamnorouzi, jrf.
Fixes #54914.

git-svn-id: https://develop.svn.wordpress.org/trunk@53490 602fd350-edb4-49c9-b593-d223f7449a82

Updates to Plugin Dependencies

This commit addresses a fatal TypeError occurring in widgets.php when merging sidebar widgets. The error was caused by null values being passed to array_merge(), which expects only arrays.
Changes made:

Replace the problematic array_merge() call with a more robust loop
Add explicit checks for array type before merging
Implement array_unique() to remove potential duplicates

This fix prevents the "Uncaught TypeError: array_merge(): Argument WordPress#5 must be of type array, null given" error, improving stability when handling widget data, especially during theme switching or widget updates.

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```

trac: https://core.trac.wordpress.org/ticket/65914

When `$button` has a structure like `%a`, a PHP parser error can cause
Pods or other similar custom metadata blocks to fail to display,
resulting in a serious problem. This often disrupts the normal
management and use of WordPress. This patch corrects this issue in a way
that has been verified to be effective!

It's worth noting that, whether we like it or not, this solution is
generated by AI combined with internet data retrieval. This solution is
very simple and therefore involves no human creativity; I must admit, it
was generated by AI.

Hopefully, it can be merged quickly to resolve the issue as much as
possible. It aims to fix the following bugs:

```
  thrown in /var/www/wordpress/wp-includes/general-template.php on line
533" while reading response header from upstream, client: 10.20.245.1,
server: www.qhjack.top, request: "GET
/wp-admin/post.php?post=582&action=edit HTTP/1.0", upstream:
"fastcgi://unix:///run/php/php8.5-fpm.sock:", host: "www.qhjack.top",
referrer: "https://www.qhjack.top/wp-admin/edit.php?post_type=services"
2026/08/30 16:25:15 [error] 289643#289643: *106436 FastCGI sent in
stderr: "PHP message: PHP Fatal error:  Uncaught ValueError: Unknown
format specifier "a" in
/var/www/wordpress/wp-includes/general-template.php:533
Stack trace:
#0 /var/www/wordpress/wp-includes/general-template.php(533): sprintf()
WordPress#1 /var/www/wordpress/wp-includes/general-template.php(400):
wp_get_tooltip_helper()
WordPress#2 /var/www/wordpress/wp-admin/includes/template.php(1410):
wp_get_tooltip()
WordPress#3 /var/www/wordpress/wp-admin/includes/post.php(2392): do_meta_boxes()
WordPress#4 /var/www/wordpress/wp-admin/edit-form-blocks.php(401):
the_block_editor_meta_boxes()
WordPress#5 /var/www/wordpress/wp-admin/post.php(199): require('...')
WordPress#6 {main}
```