-
Notifications
You must be signed in to change notification settings - Fork 0
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
Advanced-gutenberg-blocks requiring WooCommerce working randomly #6
Comments
When attempting to debug this problem I came across another.
Perhaps the AddToCart::render_block() in method should return early when the product no longer exists. Note: This problem was produced by oik-clone not applying mappings of block attributes. The ProductID value of 1417 was OK on blocks.wp-a2z.org but not on blocks.wp.a2z, where it's 2184. |
The problem with oik-loader-mu.php appears to occur when the requested permalink ($_REQUEST_URI) is not all lowercase. e.g. /block/Add-to-cart-button-advanced-gutenberg-blocks-addtocart/ This permalink is created by the blocklist block. See bobbingwide/oik-blocks#27 |
There's a similar problem to #6 (comment) in the Product block
While attempting to edit this post, having retyped the Product search ( my fa.. ) I got a message box
WorkaroundEdit the block using the code editor and manually replace the invalid ID with the correct one. |
I found another problem with WPDM - Gutenberg blocks which is dependent upon WPDM ( WordPress Download Manager ).
Solutions
|
I made a local change in render_block()
and then corrected the |
I was going to raise a couple of issues against the plugin but discovered that it's no longer in the WordPress repository. |
New version of oik-loader v1.2.0 now installed in wp-a2z.org |
Two blocks from the advanced-gutenberg-blocks plugin - add-to-cart and product - are dependent upon WooCommerce. When this is normally activated then they work in the editor but not the front end. When WooCommerce is activated by oik-loader-mu then the blocks appear to work randomly. Working in the editor but not on the front end.
Needs investigating. It looks like an issue with which plugin is being loaded first.
The text was updated successfully, but these errors were encountered: