WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #31335, comment 3


Ignore:
Timestamp:
07/26/2015 01:01:34 AM (5 years ago)
Author:
SergeyBiryukov
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31335, comment 3

    initial v1  
    1616The original {{{wp_nonce_url(...)}}} could then call {{{wp_nonce_url_pure(...)}}} to be backward-compatible with the current logic that calls {{{wp_nonce_url(...)}}}, but in general there seems to be something wrong with the way {{{wp_nonce_url(...)}}} is coded and called.  So the long-term solution would be to refactor the logic that would need {{{wp_nonce_url(...)}}} to return an encoded result.
    1717
    18 Taking a look at {{{https://wordpress.org/support/topic/wp_logout_url-not-redirecting}}} indicates that this problem has been present for a while.  The solution presented in the last post to that thread may not work if the redirect URL also contains query strings.
     18Taking a look at https://wordpress.org/support/topic/wp_logout_url-not-redirecting indicates that this problem has been present for a while.  The solution presented in the last post to that thread may not work if the redirect URL also contains query strings.
    1919
    2020For anyone dealing with this problem while it still persists in the WordPress core, I would recommend duplicating the logic in {{{wp_logout_url(...)}}} in your own project, but instead of calling {{{wp_nonce_url(...)}}}, have it call your own function like the theoretical {{{wp_nonce_url_pure(...)}}} that I described above.