Fix #41562. - #5
Closed
pento wants to merge 2 commits into
Closed
Conversation
pento
pushed a commit
that referenced
this pull request
Jun 12, 2022
…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
azaozz
pushed a commit
to azaozz/wordpress-develop
that referenced
this pull request
Feb 2, 2024
Updates to Plugin Dependencies
BesrourMS
added a commit
to BesrourMS/wordpress-develop
that referenced
this pull request
Aug 6, 2024
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.
Closed
4 tasks
blitzy Bot
pushed a commit
to Blitzy-Sandbox/blitzy-wordpress
that referenced
this pull request
Jul 8, 2026
Resolves all 24 findings from the FINAL full-project review (docs/index.md boundary). Every fix preserves byte-identical functional output, public APIs, hook contracts, REST routes/schemas, and enqueue semantics (minimal-diff, evidence-first). Code fixes (implemented): - F-005 (CRITICAL, #3): cache-first/batch-primed prepare_item_for_response in class-wp-rest-posts-controller.php matching the passing sibling controllers; fixed a discovered attachment cache-key collision by scoping the media slice under object_type 'attachment-media' (281 posts + 129 attachment tests pass). - F-006 (WordPress#12): registered-handle memoization (get_registered_handles, count-snapshot self-healing) in class-wp-dependencies.php (340 tests pass). - F-003 (WordPress#9): WP_Metadata_Lazyloader $settings expanded to 'post'/'user' (additive; reachable via queue_objects()). - Observability (CRITICAL, #1): install_mu_plugins() wires server-timing.php + clear-cache.php into the benchmark runtime in run-baseline.sh/run-optimized.sh. - Reproducibility (CRITICAL, #2): committed representative raw inputs (before/after JSON) + fail-loud missing-baseline guard in generate-diff-report.js; report regenerates byte-identically. - Quality gate (CRITICAL, WordPress#5): refactored two no-nested-ternary JS-lint errors into a formatSignificantLabel() helper (the alleged PHPStan error was empirically non-reproducible; composer phpstan is green). - KPI 3 (WordPress#6): clarified the admin.test.js instrument as runtime browser-measured gzipped transfer (PerformanceResourceTiming.transferSize); honestly NOT met (17.97%), delivered via F-007 conditional loading. - Accessibility (WordPress#21): prefers-reduced-motion accommodation in the reveal.js deck (Rule-4 verbatim settings preserved). Documented Rule-2 deviations (files intentionally unchanged, with rationale): - WordPress#4 F-009 webpack splitting (DEV-03): admin JS is Grunt-uglified; webpack emits only 4 independent media bundles; splitChunks would break the enqueue graph for zero KPI benefit. development.js split-disable is correct. - WordPress#7 default-filters.php (DEV-04): AAP target mandates "465 registrations preserved"; deferral violates hook-contract preservation. - WordPress#8 class-wp-query.php (DEV-05): memoization/priming is pre-existing WP 6.1+ baseline; F-002 delivered in composed meta-query/wpdb/meta classes. - WordPress#10 general-template.php, WordPress#11 script-loader.php, WordPress#13 ajax-actions.php (DEV-06): no byte-identical-safe, evidence-backed seam at each file's own layer. Documentation honesty rebuild (WordPress#14-WordPress#17, WordPress#19, Rules 1-3): - Rebuilt decision-log-and-traceability.md from git-diff ground truth (correct 10-controller list, accurate per-feature counts, DEV-01..DEV-10, 100% traceability); corrected project-guide.md, technical-specifications.md, index.md, performance-dashboard.md, and the deck to reflect the actual implemented state and baseline-parity gate status. Scope accounting (WordPress#20): three added test files + signatures.php test-alignment (F-003, DEV-10) accounted in traceability §4.3. Build discipline (WordPress#18): grunt build --dev succeeds and dirties zero tracked files (compiled outputs are gitignored). Test evidence (WordPress#19): PHPStan green; PHPCS 0 errors / 0 new warnings (BASE-parity proven); JS lint green; full PHPUnit suite 28994 tests with only 8 pre-existing environmental tzdata failures (deprecated zones absent from container tzdata), all in unchanged files and baseline-identical.
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Aug 30, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Aug 31, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Aug 31, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Aug 31, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Aug 31, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 1, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 1, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 1, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 1, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 1, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 2, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 2, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 2, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 2, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 2, 2026
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} ```
jack9603301
added a commit
to jack9603301/wordpress-develop
that referenced
this pull request
Sep 3, 2026
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} ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.