-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Comments: Fix 'sprintf requires more than 1 params' error #49054
Conversation
Created an issue on WordPress's Core trac and added a patch: https://core.trac.wordpress.org/ticket/57919 |
@aristath, there's no need for a separate core ticket and PR. The PHP changes from the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fixes the issue for me.
Ah OK, I didn't know if we need to backport this one manually since we're now at RC in Core. Good to know, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @aristath! Since the unnecessary sprintf()
was removed, and there were no changes to the string, this LGTM! 👍
I just cherry-picked this PR to the wp/6.2 branch to get it included in the next release: 784081e |
This bug was introduced in 6.1, not in 6.2. Technically, this should not be backported during 6.2's RC cycle. Why? Only bugs and regressions introduced in the milestone and found during RC can be backported. cc @Mamaduka |
I just reverted PR from the |
Thank you @Mamaduka! This fix is slated for 6.2.1. It also needs automated tests added in Gutenberg and Core. See the details of the committer discussion here https://core.trac.wordpress.org/ticket/57883#comment:15. |
I just cherry-picked this PR to the wp/6.2 branch to get it included in the next release: 5384ee8 |
What?
Fixes #49000
Why?
To avoid PHP errors. Please take a look at the report on #49000 for more details.
NOTE: The same error happens in WP-Core, so this will need to be backported to Core as well. cc @Mamaduka