See My Reusable Blocks

I just saw this on WP Tavern and noting it here for the future.

With Gutenberg you can make reusable blocks. The neat thing about them is that if you subsequently edit the block, you change it for every appearance on the site. That can be handy if you need to update some information contained in the block.

The tip on WP Tavern was that if you want to see the reusable blocks you have made, log in to the admin panel and then add the next bit and you will see them listed.

~/wp-admin/edit.php?post_type=wp_block

Change One Instance Of A Reusable Block

This is something I heard tonight at a WordPress Meetup. If you want to use a reusable block and keep most of its features but change it a bit for just one instance, you could just start from fresh. But another way to do it is to duplicate the reusable block; change the duplicate to a standard block and then edit it. Then delete the reusable block.

Running The WooCommerce Setup Wizard

If you skip the setup wizard when you activate WooCommerce, a number of pages will not be created. If you go to WooCommerce/Status you will see that the following pages are not set:

  • Shop base
  • Cart
  • Checkout
  • My account
  • Terms and conditions

They are all special pages designed with WooCommerce shortcodes, and if you skipped or missed the setup wizard when you first downloaded and activated the plugin, you can restart the wizard at any time by going to:

~/wp-admin/?page=wc-setup

-OR- next to Add To Basket

I narrowed down the conditions under which the problem happened to the following:
– When ApplePay is set in Stripe ( Enable Payment Request Buttons. (Apple Pay/Chrome Payment Request API)
– And the product is a variable product
– And I am looking in Safari browser (but not in Firefox or Chrome)
– And I am logged in

Then the Add To Basket button shows the -OR- which is part of the Pay with Apple Pay – OR –

In Safari/Privacy I disabled ‘Allow website to check for Apple Pay and Apple Card in’, and then logged out of my WooCommerce site and back in again and the problem went away.