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
Bypass scheduled actions for customer updates #37265
Merged
mattsherman
merged 10 commits into
trunk
from
update/bypass-actions-for-customer-updates
Mar 17, 2023
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
8bc8400
Bypass scheduler for customer update
mattsherman 18866b4
Handle case when wc_last_active user meta doesn't exist at all
mattsherman 4c09f07
Bypass scheduler for wc_last_active customer update
mattsherman 8a65779
Changelog
mattsherman d6fb8a6
Bypass scheduler for delete_user and remove_user_from_blog
mattsherman 1bc03bb
Bypass scheduler for woocommerce_privacy_remove_order_personal_data
mattsherman 4356684
Bypass scheduler for woocommerce_new_customer
mattsherman 33254b1
Fix linting issue
mattsherman c8e5fe7
Remove obsolete test for last_active_update sync
mattsherman 26aa5a3
Remove assertions for pending wc-admin_import_customers
mattsherman File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
4 changes: 4 additions & 0 deletions
4
plugins/woocommerce/changelog/update-bypass-actions-for-customer-updates
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,4 @@ | ||
Significance: patch | ||
Type: performance | ||
|
||
Bypass Action Scheduler for customer updates. |
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
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
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
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
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'm wondering why this had to be added. In which scenario would this be called with user_id < 1? Maybe it's worth adding a comment?
EDIT: I see you only moved this from the scheduler. Feel free to leave it like this if you think it's OK.
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.
A user ID of
0
would be an unauthenticated request, or some error up the chain that resulted in user ID0
. Whatever the case, proceeding with theDELETE
would be unnecessary, so the early return seems most robust.