Skip to content

fix: undefined array key 'context' warning in Gutenberg.php (PHP 8+) #943

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nicholasio merged 2 commits into from
Feb 13, 2026
Merged

fix: undefined array key 'context' warning in Gutenberg.php (PHP 8+) #943

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9338be8
fix: add null coalescing check for context param in Gutenberg.php
Feb 2, 2026
c33e94b
Merge branch 'develop' into fix/undefined-context-key-warning
nicholasio Feb 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/fix-undefined-context-key.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@headstartwp/headstartwp": patch
---

Fix: Add null coalescing check for context parameter in extend_post_content to prevent PHP 8+ "Undefined array key" warning. Fixes #940
2 changes: 1 addition & 1 deletion wp/headless-wp/includes/classes/Integrations/Gutenberg.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ public function extend_post_content( \WP_REST_Response $data, \WP_Post $post, \W

$params = $request->get_params();

if ( 'view' !== $params['context'] ) {
if ( 'view' !== ( $params['context'] ?? '' ) ) {
Copy link

@cursor cursor bot Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Default fallback value mismatches WordPress context default

Medium Severity

When the context key is absent from $params, the fallback defaults to '' instead of 'view'. WordPress's standard default for context in REST API endpoints is 'view', so a missing key semantically means context=view. With ?? '', the check 'view' !== '' evaluates to true and the method returns early, skipping block styles — the opposite of what happens when context is explicitly 'view'. Using ?? 'view' as the fallback would correctly match WordPress's intended default and ensure block styles are added for requests that omit the context parameter.

Fix in Cursor Fix in Web

return $data;
}

Expand Down
Loading