You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running get_current_screen()->id within any of the inner admin pages of WooPayments ( e.g. Payments -> Transactions , Payments -> Payouts , and Payments->Disputes) , does not give a unique screen ID, but rather returns - woocommerce_page_wc-admin . This is not unique and does not give us an accurate depiction of where the function was called.
Notes
The usage of unique screen ID instead of extrapolating it with query parameters came up in a review on another PR, where we were implementing a track event.
Related internal discussion - p1740360862997249-slack-C04MVBQC0MS
The text was updated successfully, but these errors were encountered:
A unique screen ID for each admin page is very important for various use cases notably:
WordPress core and WooCommerce have a unique screen ID for each admin page that can be sought using the get_current_screen() function. However, we have a discrepancy within almost all WooPayments admin pages.
Running
get_current_screen()->id
within any of the inner admin pages of WooPayments ( e.g.Payments -> Transactions
,Payments -> Payouts
, andPayments->Disputes
) , does not give a unique screen ID, but rather returns -woocommerce_page_wc-admin
. This is not unique and does not give us an accurate depiction of where the function was called.Notes
The text was updated successfully, but these errors were encountered: