-
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
Try: Return error when session is missing for REST nonce refresh #67812
Open
Mamaduka
wants to merge
1
commit into
trunk
Choose a base branch
from
try/rest-nonce-send-eror
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+23
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
<?php | ||
/** | ||
* Temporary compatibility shims for Core Ajax handlers. | ||
* | ||
* @package gutenberg | ||
*/ | ||
|
||
/** | ||
* Handles renewing the REST API nonce via AJAX. | ||
* | ||
* @since 5.3.0 | ||
* @since 6.8.0 Returns error when session token is missing. | ||
*/ | ||
function gutenberg_ajax_rest_nonce() { | ||
$token = wp_get_session_token(); | ||
if ( empty( $token ) ) { | ||
wp_send_json_error( null, rest_authorization_required_code() ); | ||
} | ||
|
||
exit( wp_create_nonce( 'wp_rest' ) ); | ||
} | ||
add_action( 'wp_ajax_rest-nonce', 'gutenberg_ajax_rest_nonce', 0 ); |
This file contains 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
Oops, something went wrong.
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.
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.
I love to see a wp_die and wp_error combo here. wp_die is clever enough to use _ajax_wp_die_handler if it is admin ajax request.
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.
Any particular reason why this piece of code should be different/inconsistent with most other AJAX responses from admin-ajax? Don't think introducing inconsistencies is a good idea, sorry :)
Also, as mentioned above I think this code may introduce edge cases as it is only checking the default cookies and not using the proper functionality to determine if a user is logged in?
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.
The
wp_send_json_error
useswp_die
internally.See: https://developer.wordpress.org/reference/functions/wp_send_json/.
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.
Sure, let me reformulate the question: why not use wp_send_json_error() as most other WP code but use wp_die() directly with a new
WP_Error
instance? What advantages does that bring? Are the advantages worth it the change/inconsistency? (And other in the same line of thought) :)BTW if a new
WP_Error
instance is needed for some reason it seems it can be passed towp_send_json_error()
.