Forum Replies Created

Viewing 15 replies - 46 through 60 (of 581 total)
  • Hi there @4vke!

    If I’m understanding correctly, you want to be able to use the filter blocks (eg the “Filter Products by Attributes”, “Filter Products by Price”, or “Active Product Filters”) blocks to power the filtered views on the store catalog page (which by default lives at the mystore.com/shop url). If so, currently that is not possible because the filter blocks do not affect the queries executed on the store catalog page.

    However, you can use the “All Products” block along with the filter blocks to achieve similar functionality as the filter blocks are wired up to work in concert with the All Products block.

    It sounds like this may be an issue with the extension you are using (Cart Flows – Cart Abondoment?) not supporting this status for those using the Cart and Checkout blocks.

    In the post I linked with you there’s some rationale given behind some of the technical reasons we had to introduce this new status. You may want to point the developers of the extension you are using to the post I linked to and see if they are planning on supporting this status (they can also reach out to us via the WooCommerce Blocks GitHub repository).

    Hi there,

    The new blocks introduced a new checkout-draft status for orders. You can read more about that here.

    An “Add to Cart” block is on our roadmap. No ETA yet.

    Sorry for your experience @simatic007 which has led to this negative review.

    Are you willing to elaborate on some specifics? Have you tried posting this as a support issue?

    I’m guessing this is in reference to you trying out the preview of the Cart and Checkout blocks in this feature plugin. Currently it is expected that not all payment methods are supporting these blocks yet, but this is improving and there’s already a number of payment methods that do support the blocks. You can follow this document here which is updated whenever extensions within the Woo marketplace (including payment methods) support the Cart and Checkout blocks.

    If your payment method is developed by a third party other than WooCommerce, you may want to notify them about their lack of support and you can refer them to this developer advisory we posted.

    I concur with @thup90 that this is an issue caused by your child theme’s functions.php file as noted in path of the fatal error in your logs. The problem is that the $product global referenced in the filter callback is not necessarily always populated in all contexts where the woocommerce_product_add_to_cart_text filter is called.

    Instead of using the global, a better solution would be to use the product instance provided to the filter callback – something like this “should” stop the fatal error from happening (untested and use at your own risk):

    
    /*Change Select Options Text */
    add_filter( 'woocommerce_product_add_to_cart_text', function( $text, $product ) {
    	if ( ! $product instanceof WC_Product ) { 
                return $text;
            }
    	if ( $product->is_type( 'variable' ) ) {
    		$text = $product->is_purchasable() ? __( 'Options', 'woocommerce' ) : __( 'Read more', 'woocommerce' );
    	}
    	return $text;
    }, 10, 2 );
    

    Hi @umbrellacover, I’m assuming you’ve been trying to use the Cart and Checkout blocks included in this feature plugin. As @dcka pointed out, it sounds like Advanced Dynamic Pricing does not integrate with these blocks yet.

    As we become aware of extensions that are compatible with the blocks we update this documentation page. As Cara mentioned, you can contact the developers of the Advanced Dynamic Pricing extension and let them know you are interested in their product being compatible with the Cart and Checkout blocks.

    Thanks for sharing more details around what was causing the error @n00b82! I’m going to mark this thread as resolved.

    Hi there Pablo!

    You mentioned that you’re having problem trying to use the product categories block to customize a page and the product categories you’ve created don’t show up as options to select.

    Just to make sure we’re talking about the same block first. Are you talking about the Products By Category block (like this one)?

    Assuming this is the block, is the issue that when you insert the block you don’t see categories to select from (it should show what is in my linked screenshot above).

    Hey thanks for the praise @doublehead73! You could also let Skyverge know about this post we published inviting payment method extension developers to integrate with the Cart and Checkout blocks (with links to documentation): https://developer.woocommerce.com/2021/03/15/integrating-your-payment-method-with-cart-and-checkout-blocks/ (in case they aren’t already aware).

    Plugin Author Darren Ethier (nerrad)

    (@nerrad)

    Hi there,

    I’m assuming you are here because you are using the new checkout block included with the WooCommerce Blocks feature plugin.

    The Checkout Block does not support all the same functionality as the existing shortcode based checkout flow so that does mean that currently the filter you are using to change the default checkout country will not work.

    However, if you don’t mind the default country being the same as what is configured as the country for your store address, the block does respect the Default Customer Location option configured in the WooCommerce general settings page. Here’s a screenshot of the option: https://cln.sh/fssMGz

    If you configure the option to be “Shop base address” and your store address is what you want the default country to be, this should work well.

    I hope that helps!

    Plugin Author Darren Ethier (nerrad)

    (@nerrad)

    Hi there Dave,

    Currently the only way to do items 1-3 in your list is via some custom CSS. For instance you can hide the product images via something like this:

    
    .wc-block-cart-item__image {
    	display:none;
    }
    

    Regarding not being able to get PayPal to show as a payment option for the Cart and Checkout blocks – currently only PayPal Standard is supported. Extensions need to explicitly support the new flows as they differ significantly from the shortcode powered flows currently in WooCommerce core. There are extensions integrating with the blocks all the time and we have a document tracking the status of integrations.

    I hope that helps!

    Plugin Author Darren Ethier (nerrad)

    (@nerrad)

    Howdy @papermelon,

    I thought your request was pretty interesting so I gave a go at seeing if there’s a way to implement this using the current state of the Payment Method interfaces in the new WooCommerce Blocks checkout flow. Turns out it IS! However, the caveat is this uses an experimental interface so if you find this meets your needs you will need to be careful with using it (and monitor changes in Woo Blocks updates carefully). Hence all the disclaimers I put in the gist.

    Here’s the gist proof of concept: https://gist.github.com/nerrad/fa24d2bf01c1726f62bec7accac8be39

    I’ve tested it on my local development sites and it seems to work okay. Note, currently this mechanism will only work for payment methods that already support the new Cart and Checkout blocks.

    Plugin Author Darren Ethier (nerrad)

    (@nerrad)

    Hi there!

    First, it’s great that you are watching for these things. Thanks for surfacing it to us and letting us know!

    Due to the fact WooCommerce Blocks supports the previous two minor versions of WordPress, inevitably there will be times when a WordPress package feature is deprecated in a more recent version of WordPress and not in a prior version. To keep support for earlier versions we have to ship with the deprecated implementation which results in these warnings.

    Fortunately, even though WordPress is showing these warnings, there won’t be any breakage because the package still supports the older implementation. Whenever we are able to update the minimum required version WordPress that we support to a version that we can drop the deprecated usage of the function/feature, we will, and those warnings will go away.

    Hi there,

    To be clear for folks reading this review, it appears to be directed towards the Cart and Checkout blocks specifically. It should be noted that this feature plugin is not only for Cart and Checkout blocks.

    Regarding terms and conditions checkbox: we will be providing more options for how stores wish to indicate requirements around agreeing to terms and conditions. This isn’t off our radar.

    Regarding compatibility for third-party gateways (and other extensions): the cart and checkout blocks do not re-use the same patterns of extensibility as the shortcode based checkout flow in WooCommerce core because it is primarily client based rather than server (php) based for the rendered content. There are a number of reasons for this, among them are increased stability and reliability for the checkout flow (protecting against breakage by extensions), a better shopper experience for checking out, more straightforward extending of the checkout/cart flow by extensions, and better options around modifying the cart and checkout by merchants. While we haven’t fully realized all our goals yet with the cart and checkout blocks (which is why they are still in the feature plugin) – we’re steadily working towards them.

    Due to the changes, extensions and payment methods will have to explicitly build compatibility for the new checkout flow. We are currently working through a number of the WooCommerce owned payment methods and are actively encouraging other payment method extensions to integrate with the blocks.

    In the meantime, we do have a page which lists the current status of extension compatibility with the blocks.

Viewing 15 replies - 46 through 60 (of 581 total)