Skip to content
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.

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

Adds additional check to make sure the show_in_rest parameter is present before it is manipulated #60861

Closed

Conversation

thijsoo
Copy link

@thijsoo thijsoo commented Apr 18, 2024

What?

This pr makes sure that it is checked that show_in_rest is present before it is manipulated and shows a notice for plugins using register_setting without specifying show_in_rest.

Why?

This solves #60859

How?

I have added an additional isset check.

Testing Instructions

  1. Install Gutenberg latest version and & Yoast SEO
  2. Go to Yoast SEO->Settings
  3. Confirm that you don't get a Warning: Undefined array key "show_in_rest" warning

Testing Instructions for Keyboard

Screenshots or screencast

Copy link

github-actions bot commented Apr 18, 2024

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: thijsoo <[email protected]>
Co-authored-by: Mamaduka <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

  • Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
  • Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

Copy link

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @thijsoo! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

@github-actions github-actions bot added the First-time Contributor Pull request opened by a first-time contributor to Gutenberg repository label Apr 18, 2024
@thijsoo
Copy link
Author

thijsoo commented Apr 18, 2024

@aristath I heard that you would be willing to take a look

@Mamaduka
Copy link
Member

Sorry, @thijsoo. I didn't know you were already working on this and created fix for the same issue - #60862.

@thijsoo
Copy link
Author

thijsoo commented Apr 18, 2024

Sorry, @thijsoo. I didn't know you were already working on this and created fix for the same issue - #60862.

No problem! Just happy to see the notice fixed :).

@Mamaduka
Copy link
Member

I'll make sure to include you in the list of props. Sorry again for the confusion.

@Mamaduka Mamaduka closed this Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
First-time Contributor Pull request opened by a first-time contributor to Gutenberg repository
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants