I’ve been experiencing a lot of frustration with WooCommerce recently, especially with the new block-based checkout approach. When trying to customize the checkout form to include extra fields and adapt the experience to the needs of my business, I’ve run into a lot of obstacles. The idea of ??a modular system could be beneficial, but in practice, the lack of flexibility has been extremely limiting.
What’s most disappointing is that this rigidity seems to contradict WordPress’ own policies and proposals, a platform that has always preached freedom and flexibility for developers and entrepreneurs. WordPress is known for allowing its users to create and adapt their projects freely, without restrictions. However, the impression that WooCommerce gives with this approach is completely different.
It’s as if WooCommerce is holding thousands of developers and entrepreneurs hostage to a system that should make our lives easier, but instead forces us to find complex solutions for simple tasks, such as adding a custom field to the checkout, as is the case in my country, which requires additional fields to the plugin’s default to meet our needs.
This change, instead of helping the community, feels like a barrier, taking away the promise of freedom that has made WordPress the number one choice for so many businesses around the world.
]]>Well, to begin with, I am very newbie on wordpress.
But since it’s a modular based platform, seems easy to work with in some ways.
I’m currently creating my business website on it, turns out I’m stuck with a mobile lack of responsiveness.
If you see the page I’ve attached, and you scroll down, you’ll see 5 squares of key points, I have one block with the key point and other above it with full description, seems cool on desktop, but when I turn to mobile, the key points are all ligned up, and after that comes all the descriptions.
Any help to get them like desktop? Thanks ]]>
I have a client site where we’re using RCP Pro; the site uses a classic theme. I’m going to rebuild the site using a new block-based theme. Will RCP continue to work, or work better?
Thanks!
]]>I’m not in the block editor enough to know which version of WP introduced the third-party ‘Available Blocks’ feature, but I recently became aware of the fact that when searching from within the block inserter the keywords are being used to populate an ‘Available Blocks’ section within the results list. The blocks advertised in this section all seem to be from third-party’s of which I have no idea where they’re actually being hosted (I’m an in-house developer, so I’m not aware of a block marketplace). The feature was brought to my attention via one of our brand/design directors who was concerned about users with the right permissions installing and using them. I assured him that wouldn’t happen due to underlying installation permissions that would likely block such an event but I’m wondering if there’s any documentation out there yet with regard how to disable the third-party blocks feature itself and in doing so without the use of a plugin.
Outside of looking to disable the feature I’m curious if anybody else finds this feature as potentially troublesome in being ‘enabled’ by default?
The screenshot below shows how the third-party blocks are brought up during a block search and where they’re displayed in the inserter…
Link to screenshot – https://www.dropbox.com/scl/fi/3lfojes2mvsmd69dncang/Screen-Shot-2024-10-14-at-10.27.48-AM.png?rlkey=btnv21ywp4r80m0sni6gxyk0t&st=d9dvytal&dl=0
I have a CPT named “Diets” and a PHP based custom block that allows editors to add product previews in the Gutenberg editor for the diets (and other CPTs).
If the “Credit card with Oney” option is selected in the Netopia plugin, the admin pages containing the product preview block will no longer work, throwing the following error:
Fatal error: Uncaught Error: Call to a member function get_cart_total() on null in /home/stage/public_html/wp-content/plugins/netopia-payments-payment-gateway/oney/oney-add-on-netopia.php:195 Stack trace: #0 /home/stage/public_html/wp-includes/class-wp-hook.php(324): oneynetopia_single_product_page() #1 /home/stage/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /home/stage/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #3 /home/stage/public_html/wp-content/themes/kindora-v2_child/woocommerce/single-product/add-to-cart/simple.php(67): do_action() #4 /home/stage/public_html/wp-content/plugins/woocommerce/includes/wc-core-functions.php(345): include(‘…’) #5 /home/stage/public_html/wp-content/plugins/woocommerce/includes/wc-template-functions.php(1729): wc_get_template() #6 /home/stage/public_html/wp-includes/class-wp-hook.php(324): woocommerce_simple_add_to_cart() #7 /home/stage/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #8 /home/stage/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #9 /home/stage/public_html/wp-content/plugins/woocommerce/includes/wc-template-functions.php(1720): do_action() #10 /home/stage/public_html/wp-content/themes/kindora-v2_child/template-parts/woocommerce/quick-view-product-card.php(75): woocommerce_template_single_add_to_cart() #11 /home/stage/public_html/wp-includes/template.php(812): require(‘…’) #12 /home/stage/public_html/wp-includes/template.php(745): load_template() #13 /home/stage/public_html/wp-includes/general-template.php(206): locate_template() #14 /home/stage/public_html/wp-content/themes/kindora-v2_child/template-parts/blocks/product-card.php(45): get_template_part() #15 /home/stage/public_html/wp-includes/template.php(812): require(‘…’) #16 /home/stage/public_html/wp-includes/template.php(745): load_template() #17 /home/stage/public_html/wp-includes/general-template.php(206): locate_template() #18 /home/stage/public_html/wp-content/themes/kindora-v2_child/blocks/main-diet/block.php(67): get_template_part() #19 /home/stage/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php(738): include(‘…’) #20 /home/stage/public_html/wp-includes/class-wp-hook.php(324): acf_block_render_template() #21 /home/stage/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #22 /home/stage/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #23 /home/stage/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php(712): do_action() #24 /home/stage/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php(610): acf_render_block() #25 /home/stage/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php(533): acf_rendered_block() #26 /home/stage/public_html/wp-includes/class-wp-block.php(519): acf_render_block_callback() #27 /home/stage/public_html/wp-includes/blocks.php(2061): WP_Block->render() #28 /home/stage/public_html/wp-includes/blocks.php(2113): render_block() #29 /home/stage/public_html/wp-includes/class-wp-hook.php(324): do_blocks() #30 /home/stage/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #31 /home/stage/public_html/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(1871): apply_filters() #32 /home/stage/public_html/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(575): WP_REST_Posts_Controller->prepare_item_for_response() #33 /home/stage/public_html/wp-includes/rest-api/class-wp-rest-server.php(1230): WP_REST_Posts_Controller->get_item() #34 /home/stage/public_html/wp-includes/rest-api/class-wp-rest-server.php(1063): WP_REST_Server->respond_to_request() #35 /home/stage/public_html/wp-includes/rest-api.php(547): WP_REST_Server->dispatch() #36 /home/stage/public_html/wp-includes/rest-api.php(2925): rest_do_request() #37 [internal function]: rest_preload_api_request() #38 /home/stage/public_html/wp-includes/block-editor.php(753): array_reduce() #39 /home/stage/public_html/wp-admin/edit-form-blocks.php(80): block_editor_rest_api_preload() #40 /home/stage/public_html/wp-admin/post.php(187): require(‘…’) #41 {main} thrown in /home/stage/public_html/wp-content/plugins/netopia-payments-payment-gateway/oney/oney-add-on-netopia.php on line 195 ]]>
Any chance you can add a filter to override this and provide an example of triggering the tracking ID as the REST API does not rely on a cookie?
Look forward to your response.
]]>