Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi @kubiq

    Thanks for reaching out!

    If I understand you correctly, you are receiving these error messages when using the WooCommerce Blocks, right?

    This is quite strange as I was unable to reproduce the issue on my end.

    Can you please share with us a clear screenshot of your screen referring to these error messages so that we could address you more effectively?

    If you don’t already have a screenshot service installed, you can try https://snipboard.io or https://skitch.com/. You can share the direct link to the image as a response to this topic.

    Additionally, I’d like to understand your site properly, please share your System Status Report that you can find via WooCommerce > Status. Select Get system report and then Copy for support. Once you’ve done that, you can paste it into your reply here.

    If you could also provide the fatal error logs (if any) under WooCommerce > Status > Logs.

    Thanks!

    Thread Starter kubiq

    (@kubiq)

    Hello,

    I’m testing this on clean WP install where only WooCommerce and Block manager plugin are installed – everything in newest versions – WP 6.1.1 + WOO 7.2.2

    So no, I don’t have separate plugin for WooCommerce Blocks.

    This is happening only in Block manager plugins, so blocks from cart or checkout can not be deactivated there because of these errors.

    I can tell you exactly what the problem is:

    When you register block in JS file with registerBlockType function you need to provide also title attribute there – you have this everywhere except checkout and cart blocks, eg. in file /wp-content/plugins/woocommerce/packages/woocommerce-blocks/build/checkout.js or /wp-content/plugins/woocommerce/packages/woocommerce-blocks/build/cart.js

    When you open these files (it’s minified unfortunately) you can see that everywhere where registerBlockType is called, the attributes list starts with icon and there is no title attribute.

    Just add title attribute there and everything will be solved ??

    Saif

    (@babylon1999)

    Hello @kubiq,

    Thank you for sharing your findings, this will help anyone land on the thread in the future. ??

    I will go ahead and mark the thread as solved, feel free to open a new one if you have any other questions.

    Cheers!

    Plugin Contributor Saad T.

    (@saadtarhi)

    Hello @kubiq! ??

    Thank you for reporting this bug! Our Blocks are registered on the server-side in addition to the client-side registration as recommended by Gutenberg and to apply some dynamic changes to our metadata. WordPress (or Gutenberg) prepare and send server-registered blocks to a specific set of WP core pages (i.e.,?post.php,?site-editor.php,?widgets-form-blocks.php) using the function?get_block_editor_server_block_settings?(For example, see?this line). In this instance, the?Gutenberg Block Manager plugin?is displayed on the?wp-admin/options-general.php, which isn’t included in the previously mentioned WP core pages. Hence, this plugin isn’t getting any back-end data about the blocks.

    So, it isn’t only an issue of missing titles; any other modification to the metadata done on the back end is also lost for this?Plugin!

    A potential solution for the author is to add?a similar line of code used in WP?somewhere in his plugin to get the back-end metadata.

    Thread Starter kubiq

    (@kubiq)

    That is very interesting, thank you very much for the detailed explanation!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Missing block titles’ is closed to new replies.