-
Notifications
You must be signed in to change notification settings - Fork 51
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
fix(tracking): handling user role in pixel #3137
Conversation
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.
Couldn't replicate the warning, but otherwise looks fine to me. 1 non-blocking suggestion below.
@@ -38,7 +41,7 @@ private static function get_event_params() { | |||
$current_user = wp_get_current_user(); | |||
$event_params = [ | |||
'page_title' => get_the_title(), | |||
'user_role' => empty( $current_user->roles ) ? 'guest' : $current_user->roles[0], | |||
'user_role' => empty( $current_user->roles ) ? 'guest' : array_shift( $current_user->roles ), |
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.
Nit: since there's no need to alter the original array, reset
might be a better choice instead of array_shift
.
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.
Ah, good call! Updated in 28f5df2
🎉 This PR is included in version 4.1.0-epic-ras-acc.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
# [4.2.0-alpha.1](v4.1.0...v4.2.0-alpha.1) (2024-05-31) ### Bug Fixes * **newsletters:** missing UTM params passing ([#3145](#3145)) ([0688fa0](0688fa0)) * **ras-setup:** redirect to init screen after setup ([#3142](#3142)) ([b86580b](b86580b)) * **ras:** handle RAS disabled in newsletters signup handling ([3d70a1d](3d70a1d)) * **ras:** prevent email address exposure via user login ([#3139](#3139)) ([9b534d3](9b534d3)) * **reader-revenue:** prevent sending duplicate receipt emails ([aa91890](aa91890)) * **tracking:** handling user role in pixel ([#3137](#3137)) ([a041764](a041764)) ### Features * **cli:** enable running the setup with a site import ([#3122](#3122)) ([c6cc10e](c6cc10e)) * expand memberships perf to archives ([#3148](#3148)) ([bdbdf1d](bdbdf1d)) * **memberships:** remove content restriction handling on the homepage ([b63a3fa](b63a3fa)) * update donation landing page ([#3109](#3109)) ([96218c1](96218c1))
🎉 This PR is included in version 4.2.0-alpha.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 4.2.0-epic-ras-acc.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 4.2.0-epic-ia.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
# [4.3.0](v4.2.0...v4.3.0) (2024-06-12) ### Bug Fixes * **newsletters:** missing UTM params passing ([#3145](#3145)) ([0688fa0](0688fa0)) * **ras-setup:** redirect to init screen after setup ([#3142](#3142)) ([b86580b](b86580b)) * **ras:** handle RAS disabled in newsletters signup handling ([3d70a1d](3d70a1d)) * **ras:** prevent email address exposure via user login ([#3139](#3139)) ([9b534d3](9b534d3)) * **reader-revenue:** prevent sending duplicate receipt emails ([aa91890](aa91890)) * **tracking:** handling user role in pixel ([#3137](#3137)) ([a041764](a041764)) ### Features * **cli:** enable running the setup with a site import ([#3122](#3122)) ([c6cc10e](c6cc10e)) * expand memberships perf to archives ([#3148](#3148)) ([bdbdf1d](bdbdf1d)) * **memberships:** remove content restriction handling on the homepage ([b63a3fa](b63a3fa)) * update donation landing page ([#3109](#3109)) ([96218c1](96218c1))
🎉 This PR is included in version 4.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
All Submissions:
Changes proposed in this Pull Request:
Fixes an issue with how the user role was retrieved in the pixel tracking code. Also refactors the code to avoid unnecessary code execution.
How to test the changes in this Pull Request:
trunk
0
while there's none** because
$current_user->roles
inMeta_Pixel->get_event_params
is[1] => 'subscriber'
Other information: