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

Unable to filter transactions report #2507

Closed
stephhjacq opened this issue Jul 21, 2021 · 5 comments
Closed

Unable to filter transactions report #2507

stephhjacq opened this issue Jul 21, 2021 · 5 comments
Assignees
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug.

Comments

@stephhjacq
Copy link

When trying to apply a filter to view transactions for last month, the screen appears blank and a JS error is thrown.

Steps to reproduce

Go to Payments > Transactions
Show > Advanced Filters
Add filter > Date
Between > try to select a date - error is thrown: TypeError: t.onMonthPreviewed is not a function

All Payments menu items cannot be accessed until a hard refresh is done.

Screen Shot 2021-07-21 at 13 35 36

WooCommerce 5.5.1
WooCommerce Payments 2.7.0
WordPress 5.8

@kalessil kalessil added priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug. labels Jul 22, 2021
@kalessil
Copy link
Contributor

There was a similar report (related to the dates filtering) #1632

@aprea aprea added status: has pr The issue has a PR. and removed status: has pr The issue has a PR. labels Jul 27, 2021
@aprea aprea removed their assignment Jul 27, 2021
@tpaksu tpaksu added status: has pr The issue has a PR. and removed status: has pr The issue has a PR. labels Aug 2, 2021
@tpaksu
Copy link
Contributor

tpaksu commented Aug 2, 2021

Sorry, added the fix and labels to the wrong issue :) Removed them.

@aprea
Copy link
Contributor

aprea commented Aug 4, 2021

Looks like this was fixed upstream here - WordPress/gutenberg#31751

This fix was included in Gutenberg 10.9.

I installed & activated the latest Gutenberg plugin locally (version 11.1.0) and was unable to reproduce this issue.

We'll need to wait until this fix is included in WordPress core.

As a temporary workaround, affected users can install the Gutenberg plugin.

WP core is currently at 5.8. The next major release is 5.9 and is scheduled for Dec 2021.

I can introduce a temporary fix in woocommerce-admin until the proper fix is released in WP core but I'd rather not as we'd have to revert it at a later time.

@Automattic/gamma, any thoughts on above? I'm unsure of how WP core releases work. Is it possible to petition for a patch release to include the upstream Gutenberg fix?

@kalessil
Copy link
Contributor

kalessil commented Aug 4, 2021

Since the fix will be released in a few months and we provided all details for future people, I'd close the issue and that's it.

@aprea
Copy link
Contributor

aprea commented Aug 4, 2021

Thanks Vlad, sounds good! I'll close this one for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug.
Projects
None yet
Development

No branches or pull requests

4 participants