Darren Ethier (nerrad)

Hi there,

We just released 4.5.1 which should fix this for you. An initial deploy of 4.5.0 didn’t go as planned and a non production build was released. There was a brief window where folks could have updated to that build so we pushed 4.5.1 which will fix things for folks seeing this message.

@skhalaf09 I think I may know where the confusion stems from. WooCommerce Blocks is a feature plugin that is published on WordPress.org for exposing both in progress work on new blocks plus improvements to existing blocks that already exist in WooCommerce core.

It appears to me that you are only only getting use of the blocks that are included in WooCommerce core releases (which is why you don’t see this plugin in your wp-contents/plugins folder).

It’s unclear to me though as I read through this issue how you are seeing the Cart block (if that’s what the requests pertain to) since the Cart and Checkout blocks aren’t supposed to be available without the feature plugin installed. Would you be able to share a screenshot of what exactly you are trying to modify? There may be some additional confusion that hopefully we can sort out here.

For example, the Gutenberg editing experience would have been impossible without a technology stack change. But can the same point can be made for the WooCommerce cart/checkout experience?

This is a very good question and I don’t want to downplay the importance of it. It is one that we have considered carefully as we considered the architectural and ux approach to the new blocks. We haven’t done a good job of communicating around the rationale for this and other decisions which is something I plan on contributing towards doing better in the coming few months. I just wanted to make sure to highlight I think you are asking the right (and very important) question here.

At this time, many developers probably feel as intimidated as I do by the amount of rebuilding that this change is going to require, so good documentation/resources will certainly help steer the ship faster.

I definitely empathize with this and acknowledge the reality that the impact on affected developers varies greatly depending on the complexity of their existing integrations and the available hours to do any refactoring/new code. As much as possible we are trying to limit significant changes to where it gives the most benefit for the merchant/store. Getting there with that approach takes longer but I’m hopeful we can mitigate much of the pain for extension developers by retaining what extension points we can on the server, and building clear API interfaces for integrating in the client.

…I’d love to see a resource that explains…

The docs Gary linked to are where we will be adding initial iterations of developer docs for new extensibility interfaces as we build them. We’re still early in this process which is why its currently limited to what you see now (and primarily oriented to payment method integrations which is more feature complete at the moment). As we are confident in the stability of the APIs we’ll also be announcing them more broadly on developer.woocommerce.com (and likely publishing there).

We know it’s important to extension developers to have a heads up and be well equipped to build integrations for Cart and Checkout blocks when we roll them out more broadly to the WooCommerce user base.

Thanks for providing your feedback here Manos, it is valued!

• This reply was modified 5 years, 4 months ago by Darren Ethier (nerrad).

No. The blocks are intended to replace shortcodes. What is your use-case for having a shortcode?

Hi there @benyoussef,

Would you be able to explain further what you mean by “I couldn’t find it later on”? What wasn’t working when you installed the blocks plugin?

Hi @diegpl

It’s best to start new threads rather than add to an existing thread, that way we can give your issue the proper attention.

The code you are referencing should only run once unless there is an issue with creating the table (in which you’ll see a notice). The query is checking for the presence of the table and if it is present then it doesn’t create the table. When the table is present then the table check should not run again.

Are you seeing this slow query being reported when you load any admin page again?

Thanks for getting back to me with the results!

One thing that I wish to know is that whether this new cart block and checkout block is using react framework and webpack bundler?

Yes. All development is happening at https://github.com/woocommerce/woocommerce-gutenberg-products-block so you can follow along there if desired.

…are any further plans to add a my-account block because the current version of it looks really outdated.

We are exploring extending the ability to control account and various checkout routes (eg order-received) via blocks as well, but no ETA on that.

• This reply was modified 5 years, 10 months ago by Darren Ethier (nerrad).