This might not be new, I hadn’t dealt with WordPress/WooCommerce in a while.

Currently (v8.8.2) in a new WooCommerce installation the “Checkout” page is created using blocks, like so:

<!-- wp:woocommerce/checkout-payment-block -->
<div class="wp-block-woocommerce-checkout-payment-block"></div>
<!-- /wp:woocommerce/checkout-payment-block -->

(...)

The problem

This might introduce breaking changes to the plugins and themes you normally use. For example, I couldn’t add a new field - programatically or using a plugin.

The fix

Remove the blocks and revert to using the shortcode:

[woocommerce_checkout]

  • Olissipo@programming.devOP
    1·
    3 months ago

    If it’s one of those things to try to make it easier for the technically challenged but ends up making more advanced techniques difficult or impossible I’m not a fan.

    In my opinion, the issue in this post is an outlier (although a surprisingly bad one).

    My experience with blocks (or the “Gutenberg editor”) has only been in creating custom blocks, I can’t speak for using built-in blocks or blocks bundled in plugins.

    With this context in mind, I’ve really liked this new editor used in conjunction with the “Advanced Custom Fields” plugin.

    And you can still use those old page builders like Visual Composer/WP Bakery (which I hate) or create templates yourself for each page, this is just another tool.

    I haven’t dived into it enough yet to see what purpose it serves or problems it aims to solve.

    I know of a project which is a good example. Very large website, but most of their content is written by non-technical people (regarding the web). They have a small team which makes custom blocks and dictates how they are used by other people when posting new content.

    I think using blocks helped them to maintain and improve a cohesive design even with so many people editing the website and after considerable years.

    I wasn’t convinced that trying to take a more advanced product like WordPress and dumbing it down for non-technical use cases was the best idea

    In that regard I reckon this is a step in the right direction for the WordPress ecosystem (but again, my experience is limited).