So I am bringing some issues here on the recommendation of Dario on the blog post announcing the new Blocks 1.5 and associated WooCommerce Blocks update.
So I generally use WooCommerce Blocks on my sites so that I can access the [wpv-woo-product-price] shortcode to display in my hand build HTML/CSS views.
I have some concerns regarding the removal of the settings screen from the latest update of WooCommerce Blocks. I have had some issues with this in the past where if you temporarily disabled the plugin fro troubleshooting purposes and enabled it again you would find your page layout template replaced by something else. So, a quick visit to the WooCommerce Blocks settings to adjust. To be honest this only happened on a certain version we were using last year and I am not even certain that the issues I am seeing now relate to this or the fact that access to their settings page has now been removed with the latest version on WooCommerce Blocks? It maybe just something that is an entry in the database?
To demonstrate I have a link to the live site where I now have WooCommerce Blocks disabled and everything is fine:
hidden link
It just so happens that in the view where I am listing theses guided tours (Guided Tours in top nav) I don't need to show the woo price as the woo price is actually a deposit (€500) and what you see on the Guided Tours page is the full price dynamically pulled from another custom field I set up.
I am though being thorough here as I do foresee a number of use cases where I may want WooCommerce Blocks. I am using the Divi Theme and am utilising a number of configurations between Theme Builder templates, and various mix-ins of Toolset templates and views implemented with both blocks and traditional methods. These do work and there are advantages, to using either a block or traditional based implementation, depending on the uses case.
For example, if you navigate into one of the Classic Spins you will see an example of where I am composing the layout with a Divi Theme builder template topped with the page header, then a Divi Post Content module pulling in the block based content template for this cycling itinerary custom post type (including repeating field groups for cycling routes and then nested day by day grouped fields for daily itineraries). The end of the main Divi template is finished off with an enquiry form.
hidden link
All good so far, till we have WooCommerce Blocks enabled. To illustrate this I have set this scenario up on a staging site.
Going back to the Guided tour Wild Atlantic Étape West on this staging site you will see what is happening:
hidden link
To me it looks like WooCommerce Blocks is interfering with how my template (Divi/toolset composition) is being applied. Note, I have moved to the product post type for eCommerce purposes for these Guided Tours. All the other posts under the cycling itinerary post type are unaffected by WooCommerce Blocks being activated. In the guided tour product I have reused and refactored the custom field grouping to fit this uses case. For example for the Day by Day area in guided tours I have used a traditional view instead of the block version in the other cycling itineraries. When I built the cycling itineraries last year I wanted to test out the block version. When I did the guided tours more recently, it was easier for me to set it up with html and css. Inversely I stuck with the block version of the gallery of images to the right of Day by Day.
You are welcome for me to give you access to the staging version of the site, if you want to investigate.
I include the debug information from the staging site below
One last observation. As I said above I generally only use WooCommerce Blocks to access the [wpv-woo-product-price] shortcode. Find building WordPress sites a precarious balancing act of adding too many plugins, just to achieve the functionality that projects dictate. Where I can, I will go out and research on the net simple functions that will provide this functionality to avoid Swiss army knife solutions. Is there any way we could have a Toolset repository of functions where we could pick and chose parts of plugins as needed? I have seen this with Dan Mossop's plugin Divi Booster. It is a bit of a Frankenstein of settings but at least you could reference the site for this plugin and it would offer the features function by function, so you didn't need to install the full plugin.