Skip to content
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

BUG: All WooCommerce Orders showing up under individual accounts after sync/update #2657

Closed
tomburtless opened this issue Mar 16, 2022 · 2 comments · Fixed by #2658
Closed

Comments

@tomburtless
Copy link

Describe the bug
Recently updated our ElasticPress to 4.0.0 and re-synced our data to find that when clicking on the Orders tab within the My Account section of WooCommerce all of the orders in the system (regardless of user) were showing up. If I attempted to view any account's order that was not owned by me I would get invalidated but the listing of data was obviously inaccurate and very worrying.

Steps to Reproduce

  1. Click on Features under Elastic Press
  2. Click Allow Protected Content
  3. Re-sync the data
  4. Go to My Account > Orders
  5. See all orders in the system

Expected behavior
I expected that only the orders for my account would show up.

Screenshots
I cannot give screenshots yet as the data that was being shown is real, live data.

Environment information
Wordpress Version: 5.9.2

Additional context
If I disable the syncing of Protected Content, this issue goes away. I'm hoping we can index and sync that data in our system though.

@tomburtless tomburtless added the bug Something isn't working label Mar 16, 2022
@brandwaffle
Copy link
Contributor

@tomburtless thanks for submitting this report--we're taking a look right away.

@brandwaffle
Copy link
Contributor

@tomburtless thanks again for submitting this issue. We've released EP 4.0.1 to address this bug and also are adding this scenario to our testing matrix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants