Thorworx

Phi Phan,
The update works flawlessly.

Thanx for your help!

Ben,

If the group block setting is enabled, can a child theme’s theme.json file simply include additions/overrides? Or does it need to be a complete formatted theme.json including copied kadence theme.json, schema, etc?

It would seem that it should work the same way as a child theme style.css or functions.php – (using overrides only) but the formatting is going to be important. An example commented child theme.json would be appreciated.

{
	"version": 2,
	"settings": {},
	"styles": {},
	"customTemplates": {},
	"templateParts": {}
}

Phi Phan,

No problems on your server.
Comparing server info, the only differences I’m seeing is you’re using PHP8 and a newer mysqli.

Turned on WP debug on my server, and it shows nothing and nothing is written to my server logs about the block crashes.

Tested in Firefox and Chrome (Opera).

Interestingly, Opera shows a different error -but still related to react-dom.js:

react-dom.min.js?ver=18.2.0:10 TypeError: Cannot destructure property '__experimentalGetPreviewDeviceType' of '(e(...) || e(...))' as it is undefined.
    at index.js?ver=5c3b4b6dba8322443e2e79cd0c0d0859:22:5208
    at data.min.js?ver=dc5f255634f3da29c8d5:9:1957
    at __unstableMarkListeningStores (data.min.js?ver=dc5f255634f3da29c8d5:2:22508)
    at Object.__unstableMarkListeningStores (data.min.js?ver=dc5f255634f3da29c8d5:2:22765)
    at l (data.min.js?ver=dc5f255634f3da29c8d5:9:1922)
    at data.min.js?ver=dc5f255634f3da29c8d5:9:2426
    at Je (data.min.js?ver=dc5f255634f3da29c8d5:9:2636)
    at Qe (data.min.js?ver=dc5f255634f3da29c8d5:9:2953)
    at gt (index.js?ver=5c3b4b6dba8322443e2e79cd0c0d0859:22:5161)
    at index.js?ver=5c3b4b6dba8322443e2e79cd0c0d0859:305:9707
ar @ react-dom.min.js?ver=18.2.0:10
a.componentDidCatch.t.callback @ react-dom.min.js?ver=18.2.0:10
tt @ react-dom.min.js?ver=18.2.0:10
Jr @ react-dom.min.js?ver=18.2.0:10
Zr @ react-dom.min.js?ver=18.2.0:10
Gr @ react-dom.min.js?ver=18.2.0:10
(anonymous) @ react-dom.min.js?ver=18.2.0:10
xl @ react-dom.min.js?ver=18.2.0:10
fl @ react-dom.min.js?ver=18.2.0:10
Nn @ react-dom.min.js?ver=18.2.0:10
(anonymous) @ react-dom.min.js?ver=18.2.0:10

EDIT: It looks like this block developer had the same problem but was able to fix it:
https://www.ads-software.com/support/topic/widget-area-blocks-no-longer-loading-3-1-0/

• This reply was modified 6 months, 3 weeks ago by Thorworx.

Phi Phan, Thanks for trying to help… but
1) I did not receive the e-mail w/credentials
2) Testing on your server is not going to help me.

Further testing on my server:
I WAS able to successfully add Icon Separator using the Customizer > Widgets > Sidebar 1

HOWEVER:
When adding the block, the screen briefly fades to black(!?) and the block gets added without crashing and no console errors… but there is no way to set any options.

If I publish from the customizer, I can verify that your code did get inserted (default unstyled separator).. but if I go back to Dashboard > Appearance > Widgets the crashed block errors are displayed.

Very strange.

Log sent.

Phi Phan,

This is what I’m trying to create with your plugin (I want this in a widget):

If I try to add your block to a widget, this is what happens:

https://demo.thorworx.com

As for the SVG styling issue, you could add padding to the SVG to prevent it from being cropped.

Unfortunately, that doesn’t work. If you add padding to the svg, it shrinks the svg, and/or adds white padding which covers the svg.

Thank you for your feedback. Could you please provide more details about your test site, such as the WordPress version, what theme? If there is a live test page, it would be great.

Latest version of WordPress… I tested with Twenty Twenty-One and Kadence… with no other plugins installed.

There is no test page, because you just can’t add an Icon Separator block to Appearance > Widgets. It crashes the block as soon as you add it.

Regarding feature requests, I’m not clear on what you mean by the “reset to default” settings. Please tell me a bit more about it.

In standard WordPress blocks, there are usually controls to reset.
Here is the WordPress paragraph block showing the Reset controls:

According to the code, it appears that this plugin is supposed to REPLACE the default “Submit Booking” button with an “Add to Cart” button, and return WooCommerce formatted Messages/Errors: “Added to cart”, etc. using Ajax.

It does NOT do this at all.
I even switched my Woocommerce product settings to redirect to the cart upon adding a product, and this did NOT fix the problem.

We have 30 days until we’ll have to refund this plugin if it’s not updated/fixed.

I notice in the EM 6.4 release notes:
“rewritten booking form JS to remove dependence on jQuery entirely”

The EM – Woo plugin code says “jQuery will load as a dependency”.

So it seems like that would break it? =(

Same here.
What’s worse is even though the backup DOES complete, if you click “Cancel” to stop the spinning wheel, it DELETES the completed backup.

This plug-in used to work flawlessly for me on multiple sites, but a while back, scheduled backups simply stopped working.

@jtuinstra Yes, it is ridiculous that this is still an issue. All of my WordPress sites are in subdirectories (the right way to do it, imo).

The workaround I found:
When viewing the homepage, instead of clicking “Customize” (Recently changed to “Edit site”) click on “Edit Page”
When the page editor opens, on the right side there is a Template section.
Click “Edit”
This will allow you to edit the template.

For me, the Design Library button does absolutely nothing when clicked.
Is it supposed to do something?

Upgraded to latest WC.

Did NOT fix the problem. Same as OP:

USPS REQUEST FAILED

As far as I can tell, the plugin is simply NOT contacting the USPS server, or is just failing to get a response.

It looks like you’re using a fairly outdated version of WooCommerce (3.3.5)

Yes.. I will be upgrading and testing to see if this solves the problem.
Generally, on a production site, I don’t do major upgrades when everything is working properly.

Since the UPS/USPS plugins are made to work with the latest WooCoomerce version

You would think so, but:

Heads up! The versions of the following plugins you’re running haven’t been tested with WooCommerce 4.0. Please update them or confirm compatibility before updating WooCommerce, or you may experience issues:
Plugin Tested up to WooCommerce version
WooCommerce Authorize.Net AIM Gateway 3.5.3

Heads up! The versions of the following plugins you’re running haven’t been tested with the latest version of WooCommerce (4.3).
Plugin Tested up to WooCommerce version
WooCommerce UPS Shipping 4.2
WooCommerce USPS Shipping 4.2