Closed haszari closed 3 years ago
Marking this as high
and adding to 1.0. If disconnect doesn't work in WordPress 5.6, then we need to fix it (or change the requirements).
In general, all functionality and UI should work consistently in all supported versions of WordPress & WooCommerce.
I'm not sure how much has been tested so far, I've done most of my testing with latest WP and Woo. So may need to dedicate some testing time to older versions.
After research, this seems to be a problem in the Modal
component of WP 5.6. I'm going to go ahead and test if any of the minor updates of WP 5.6 branch actually fixes the problem, therefore we can bump the version number there.
I'm certain the issue is with the Modal component, because if we unwrap the Modal content of the disconnect code, it renders.
If we try to even render an empty modal, it fails.
Will keep updating this.
Thanks @msaggiorato! Perhaps we can bundle the Modal
component rather than rely on whatever's in the current WP version.
Dependency Extraction Webpack Plugin
allows us to control which packages are pulled in from WordPress/Woo on the site at run time, vs compiled in (bundled) at plugin build time.
Describe the bug:
Just saw this issue, may not be easy to reproduce or high impact but wanted to log an issue for visibility. Note this was on my dev environment, with
trunk
build of WooCommerce, so may be unique to my setup.Steps to reproduce:
Marketing > Pinterest > Connection
, clickDisconnect
.Expected behavior
Disconnect modal, then disconnect.
Actual behavior
Additional details
Status report
JavaScript errors