Hi @smr76
Thank you for your kind words.
I’m not sure I fully understand you request, right now there is no plan to support the new WooCommerce block editor. The plugin only add the markdown editor to the product description and categories, and you can still use the legacy shortcodes :
Woocommerce | Shortcodes included with WooCommerce: documentation – WooCommerce
Most of the new blocks provided by Woocommerce are not currently standalone features I could trigger on demand. I would have to rewrite from scratch most of them. 💦
If you are selling items, it’s for a business case after all so if you need those blocks, I would recommend the official way by using a professional theme with the Jetpack markdown feature. (Disclaimer : I haven’t tested it myself)
Otherwise if you want to stick with the Markup Markdown plugin, I would recommend “playing” with custom post types and disabled the markdown editor for a specific set. You can easily desactivate the markdown features on both the backend and the frontend with the following snippet for example :
add_action( 'init', function() {
remove_post_type_support( '{custom_post_type}', 'markup_markdown' );
});
But I don’t know if that could cover all of your cases. At least that should allow you the freedom to use any other editors (the native block editor, Elementor, Divi, otter, etc…) with any templates related to the selected custom post type.
Feel free to tell me if that could work for you and if that answers your question.
Thread Starter
smr
(@smr76)
Sorry for the late reply, and thank you for your explanation.
What I was trying to point out is this, the new WooCommerce Product Editor (beta).
Which also I hadn’t noticed the following note before:
Development on the new product editor (v2) has been paused as we evaluate the best path forward.
But what I’m suggesting is that we change only certain parts of the product editor rather than reverting entirely to the classic editor.
I realize, however, that this approach may not align with the plugin’s intended direction.
No problems at all @smr76,
As you already understand mixing different features from different handlers won’t work together 😅 Looks like the beta editor has stopped in favor of the new V3 as you wrote, so I don’t expect the result to be different as now for the future as well. If API is involved with the V3, tuning might be tricky to do and support with a free version so I’m gonna rely on the classic editor for the long run.
Appreciate your concerns, feel free to open a new discussion if need be.
I’m trying to reply to inquiries as much as I can.
Kind regards, and have a wonderful journey with markdown
