Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter mrmac78

    (@mrmac78)

    Free!… I use both free and commercial services of Automattic, so when a product/service falls short and costs my business a 4 figure drop in daily sales because a dev has implemented a feature that’s a conversion barrier… that dev a clown. Already making move to migrate back to Magento.

    Thread Starter mrmac78

    (@mrmac78)

    to note… the plugin works no problem with their sandbox test accounts. Just SLOOOOOOOOW when connected to a live account

    Thread Starter mrmac78

    (@mrmac78)

    Hi Darren, 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.

    In all honesty, I never read the notes… so that’s my bad. But I did watch this video https://www.youtube.com/watch?v=q6HjxaHBPm8&t and at no point did WPcrafter indicate that this is an explorative plugin to test the feedback for the direction that Woo is no doubt headed. In fact, at minute 11 of said video, WPC challenges ppl to install and use this on a live to ‘see if conversions increase’.

    I think this could be why so many ppl have thought this was an end-product? nad yes I know WPC is not connected to Automattic, but he is a heavy influencer & speaker.

    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.

    Personally, I think it’s essential that payment plugins that work on the current setup, will work on the new blocks checkout. If they don’t work and this is the direction of WOO with this becoming a core checkout, I might as well jump back to Magento. As none of my stores use Stripe et al, as they are all just too expensive!. Example, Stripe = 1.4% + 20p, but I pay 0.1% + 6p via takepayments….

    mrmac78

    (@mrmac78)

    If it helps, the only thing that worked for us was to make the 2nd address field optional. It was hidden on our site and we had the same error, but as advised by Woocommerce tech support team, make this an optional field and it should work.

    well it did for us

    The dev team have acknowledged it’s a bug but there is no ETA on a fix

    Hope this helps
    M

    mrmac78

    (@mrmac78)

    Im horrified to see that the OP reported this 2+ weeks ago.
    I am having the same issue, also reported to WOO direct support (heard nothing), on this forums, and direct to SquareUp….

    Does anyone, anywhere know of a work around? As ATM im having to use Braintree to process payments, who’s terms aren;t as good as Square.

Viewing 5 replies - 1 through 5 (of 5 total)