-
Notifications
You must be signed in to change notification settings - Fork 384
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
AMP setting breaks with WooCommerce and TwentyTwentytwo theme. #7380
Comments
@milindmore22 If you could use a development build of the plugin to obtain the error stack trace, you'd be able to see the error without the minified identifiers. |
Error stack trace from dev build
|
We are getting some null sources in validation errors which are requested on-site scans. and while checking the source type in the below lines it gives the error. amp-wp/assets/src/components/site-scan-context-provider/get-sources-from-scannable-urls.js Lines 39 to 40 in 5479354
The below condition checks if sources are not empty, but there should be a guard as well to check if a source is not null. amp-wp/assets/src/components/site-scan-context-provider/get-sources-from-scannable-urls.js Lines 35 to 37 in 5479354
|
Tested prod build for PR #7406 it seems to have fixed the issue. |
Bug Description
We have received two support topics Topic 1 and Topic 2 Both users are using WoCommerce 7.2.0+ and TwentyTwentyTwo 1.3 themes both users are not able to access the AMP settings
Console error
Updated WooCommerce plugin to 7.2.2 after receiving updates still seeing same issue.
The issue can be reproducible on https://amp-support.rt.gw/
Expected Behaviour
Users should be able to access AMP settings
Screenshots
PHP Version
8.1.10
Plugin Version
2.3
AMP plugin template mode
Reader
WordPress Version
6.1.1
Site Health
Gutenberg Version
No response
OS(s) Affected
All
Browser(s) Affected
All
Device(s) Affected
All
Acceptance Criteria
No response
Implementation Brief
No response
QA Testing Instructions
No response
Demo
No response
Changelog Entry
No response
The text was updated successfully, but these errors were encountered: