-
Notifications
You must be signed in to change notification settings - Fork 69
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
Error "this block has encountered an error and cannot be previewed" on media-based blocks #3886
Comments
Reported here too: 32170495-hc |
Another report: 34466522-hc |
I'm not being able to reproduce this issue on my test site. Not sure if it is related to a new feature available only for new Atomic sites, but it works as expected on my test site. Could you share the System Status Report for one of the test sites where you can reproduce this issue? In regular WP installations, you can get it by navigating to WP Admin > WooCommerce > Status. Once there, you can click on the "Get system report" button and then copy it by clicking on the "Copy for support" button. (I tested with the WooCommerce Payments test mode, but it would be odd to be an issue only with live mode.) |
Not sure if the same issue, but a user was unable to open pages at all in their browser (I was unable to replicate), this error was showing;
Said it just started happening today. Safari worked for them but not Chrome. 34464585-hc |
Here's a system report from a test site (via TasteWP). Safari browser. ` WordPress EnvironmentWordPress address (URL): https://smoketemper.tastewp.com Server EnvironmentServer Info: TasteWP Official/2.2.0 SUHOSIN Installed: – DatabaseWC Database Version: 6.2.1 Post Type Countsattachment: 1 SecuritySecure connection (HTTPS): ✔ Active Plugins (6)Backup Migration: by Migrate – 1.1.9 Inactive Plugins (0)Dropin Plugins (1)maintenance.php: maintenance.php SettingsAPI Enabled: – Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) Connected to WooCommerce.com: – WC PagesShop base: Automattic/wp-calypso#7 - /shop/ ThemeName: Twenty Twenty TemplatesOverrides: – SubscriptionsWCS_DEBUG: ✔ No Store SetupCountry / State: United States (US) — California Payment Gateway SupportWooCommerce PaymentsVersion: 3.8.0 Action SchedulerComplete: 3 Status report informationGenerated at: 2022-03-03 03:01:49 +00:00 |
(For reference, deleted the comment above as there were some links for the site of the user with the full SSR.) |
I was able to reproduce as well now, and not sure why I wasn't reproducing before. It seems to be happening also with sites that aren't Atomic. I wonder if we need to move it to the WooCommerce Payments repo. |
Also encountered on: And a slightly different one here: |
User report: 4827310-zen |
34467077-hc Customizer disappears when WC Pay is enabled. |
34439877-hc Only the Widgets option is visible on the Customizer section |
4827505-zen |
Another user with the same issue here: 34467330-hc Customizer appears after disabling the WooCommerce Payments plugin and disappears after enabling it again. |
Another user with the same issue here: 4827226-zen Unable to access customizer when WooCommerce Payments is enabled |
34468945-hc |
FYI. #3888 is going to fix this issue. |
34334410-hc |
Hi all, WCPay 3.8.1 has been released to fix this issue. Would you please ask to customers about that? |
I am closing this issue now. Feel free to create a new issue, and reach out to devs on #wcpay if there is still any other issue. |
4827132-zd-woothemes - enabled WooCommerce Payments plugin again and issue is fixed now. I updated the user |
4827417-zd Enabled WooCommerce Payments after updating it and could access the Customizer. I let the user know about it. |
Describe the bug
The WooCommerce Payments plugin is causing media-based blocks (i.e. image, media & text, cover, video, etc.) to throw
this block has encountered an error and cannot be previewed
errors.To Reproduce
Actual behavior
The error
this block has encountered an error and cannot be previewed
is shown.Screenshots
Expected behavior
The block should be rendered without any errors.
Additional context
Encountered in 4827037-zen and 344659200-hc. I also tested on a fresh local install of WP with only WooCommerce Payments (and WooCommerce) plugins installed and was able to replicate the error.
This issue description was edited by @felipelousantos for adding more clarity.
The text was updated successfully, but these errors were encountered: