woocommerce/woocommerce

[GlobalStep] "Review" count fails to update until user refresh the full page on "WooCommerce->Home" Page

Open

#32 264 ouverte le 17 mars 2021

Voir sur GitHub
 (3 commentaires) (0 réactions) (0 assignés)PHP (10 294 stars) (10 695 forks)batch import
BugGood First IssueKirigamiWayfindingplugin: woocommerce

Description

Bug Description:

"Review" count fails to update until user refresh the full page, after user moves multiple reviews into "Approve, Mark as Spam or Delete" from "WooCommerce->Home" Page

Environment:

Woocommerce Version : WooCommerce 5.1 and 5.0 WordPress version: (v5.7) WooCommerce Admin version: v2.0.2

PC: Windows 10, Mac 10.14.6 Chrome(Version 88.0.4324.104) Firefox(Version 86.0) Safari: v13.1.1

Steps To Reproduce:

  1. Create any test site using JN site.
  2. Install and activate all the required plugins
  3. Complete the onboarding setup wizard.
  4. Go to Products->Add New and Add multiple Products /Import Products csv file
  5. Go to frontend by clicking on "Visit Site" at top left corner under Home icon
  6. Add multiple reviews from frontend
  7. Backend: Go to Comments
  8. Unapproved all the comments
  9. Go to WooCommerce->Home page
  10. Under the reviews section, move the review into "Approve, Mark as Spam or Delete" by clicking on the respective options
  11. Observe that the count fails to update, as we move the reviews
  12. Refresh the page and note that now the count for Review starts updating

Note: For one review its updating properly, for multiple reviews this issue is observed

Actual Result:

"Review" count fails to update until user refresh the full page on "WooCommerce->Home" Page

Expected Result:

"Review" count should update simultaneously when moved from "WooCommerce->Home" Page

Video:

https://user-images.githubusercontent.com/41110392/111493113-45f30a80-8763-11eb-85c3-cec90539b49e.mov

Isolating the problem (mark completed items with an [x]):

  • I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
  • This bug happens with a default WordPress theme active, or Storefront.
  • I can reproduce this bug consistently using the steps above.

Guide contributeur