Forum Replies Created

Viewing 15 replies - 91 through 105 (of 581 total)
  • Thanks for your feedback!

    We can’t give a firm timeline on when more payment method support will be added to the Checkout block, but I can tell you that we are prioritizing adding support for WooCommerce core payment methods (which includes COD).

    If you try changing your theme temporarily to something else (maybe try Storefront) does the issue persist? The symptom points to an encoding issue. The CSS used on this line is:

    
    content: "\00a0" counter(checkout-step) ".";
    

    The \00a0 is hex code for a space which should be interpreted just fine across browsers unless there is something affecting how the browser decodes the values or a plugin installed that is modifying the encoding of served assets. I would have also suggested a browser extension as the possible cause but the fact that you are reporting this across multiple browsers rules that out.

    For instance, I’m able to reproduce this issue if I use this extension for Chrome to change the character encoding to something different from UTF-8.

    Hi there,

    Thanks for taking the time to write a report on your issues here.

    This bug certainly is odd and is the first time I’ve come across this report. I appreciate you sharing the console.log from the page but it doesn’t look like any of the warnings or errors reported are related to the checkout block logic.

    The Block redirects to the native WooCommerce order received route so that would also explain the thank you page issues you are seeing as well. In this case, there is nothing the checkout block does on these routes because they are being loaded from WooCommerce core.

    As for some next steps for troubleshooting, if you have any customizations or extensions that modify the Order Received or Thank You pages, you could try deactivating them to see if that fixes it for you. It’s also possible something in your theme for those pages is causing the issue.

    Also, if you have access to the PHP errors log for your website, you can check it to see what errors are appearing in the log around the same time as your attempt to view the order received page.

    I hope the above helps you find what is causing this!

    All the best!

    Hi there!

    Thanks for taking the time to write about the issues you are experiencing using the WooCommerce Blocks feature plugin.

    I see you’re reporting difficulty with configuring a block to display the products you want. Would you mind letting me know what specific block you are having issues with? The name of the block will correspond to what you select when you insert it into the page.

    Also, could you share a bit more details about the exact steps you take to reproduce this problem? Ideally, any screenshots you could share would also help us with understanding how to attempt reproducing the issue on our end so we can discover what’s happening here.

    Also, do you have your browser set to display websites in different encoding than the default?

    Also, could you share some details about what language your site is in if it’s not configured for English? Thanks!

    Hi there!

    Thanks for your report!

    This is definitely odd behaviour. Would you be able to share details about what theme you are using on your store as well as what browser you are observing this behaviour in? Thanks!

    Hi there!

    Thanks for taking the time to offer some feedback on the Checkout block preview. The current behaviour is expected as that is how the Block is designed. While the shopper is redirected to the native WordPress login form, it is configured so that the shopper is redirected back to the checkout after they’ve logged in.

    However, I have made note of your observation in this issue.

    Hi there!

    You’re posting in the support forums for the WooCommerce Blocks feature plugin. Your request is better suited for the WooCommerce Core repository.

    If you end up having any questions about WooCommerce blocks please feel free to open up a new topic in these forums.

    All the best!

    Hi there,

    I definitely sympathize with the feeling of downloading something hoping it will meet expectations and finding out it doesn’t. In case you’re not aware, the Cart and Checkout blocks in this plugin is a preview release. You can read more about the release here.

    The current state definitely is not the final iteration of the blocks. We released them early so that folks are able to get an early look at them and for those who are able to use them, get some feedback about what to prioritize as we continue to build them out.

    Thanks for taking the time to share what you hope to see and be able to do with the blocks!

    There are also extensibility docs we’ve created for payment methods here: https://github.com/woocommerce/woocommerce-gutenberg-products-block/tree/master/docs/extensibility

    However, keep in mind that the Cart and Checkout blocks are still a preview. As we learn more about customer needs and integrate more gateways we might need to change the API’s related to extensibility. We definitely welcome third parties experimenting with the API’s now (any feedback will be invaluable!) but we do caution that it will require vigilance in keeping on top of the changelog and posts on https://developer.woocommerce.com to catch any potential changes we might have to make during the preview.

    Hi there @alexxus 👋.

    Thanks for reporting the issue. This error message will appear when the table creation for that table fails. This could be due to the db user for your WordPress install not having privileges to create tables (unlikely in this case because it being WPMU) but can also be something else.

    Is this only happening for a specific site in your network (whatever xxid is), or is it happening for multiple sites?

    You must be pig sick of telling people that this isn’t a fully-fledged plugin yet and it’s out there for test & feedback.

    It can be tiring ☺️, but honestly I realize that not everyone will be aware of the post or reads changelog notes before installing a plugin (or updating it). The best we can do is communicate where we can and have a place to point people to for more info. If anything, this feedback is super helpful because it helps us with where we prioritize development (considering all the feedback and opted-in, aggregated, data we get).

    I think the new layout is the right direction for WOO.. but it needs to include all the current features the current checkout has, otherwise you’re just limiting Woo to small-time mom & pop stores who only use Stripe and PP.

    I definitely agree with you there. That’s why the current blocks are a preview and not the final version. From our perspective, one of the main reasons we released the blocks this early as a preview is to help us learn what we need to prioritize our development time on. So we’re listening to all feedback!

    I also hear you on the payment methods ☺️

    Hey there folks!

    Thanks for checking out the preview for the new Cart and Checkout blocks! As noted in the release post, currently the blocks support a limited number of payment methods. We definitely do plan a on supporting a larger number as we iterate on the blocks (and hope third party payment method providers will build integrates as well over time), but this will take time (which is why the Blocks are not being considered for WooCommerce core yet).

    We know in their current state they won’t be usable by folks using unsupported payment methods so we are monitoring the feedback to help prioritize what we work on next.

    I hope that helps!

    Hi there @hugo_za !

    The issue you described does sound troubling. Would you mind creating an issue in our repository outlining the specific steps to reproduce that so we can look into it?

    Alternatively, if you’re uncomfortable using GitHub to report the issue, you can leave the steps here. It’s really important however, that you give as much information as possible on how to reproduce (including what payment methods you have setup, any WooCommerce extensions or customizations you may be using etc) so we can replicate in our testing as well. Thanks!

Viewing 15 replies - 91 through 105 (of 581 total)