Tagged: , , ,

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • August 18, 2015 at 9:22 am #489305
    jewelandlotus

    Hello,

    I’m really dissapointed it’s been 7 days and no fix has been issued for the MASSIVE problem.

    I am running an online shop but the CHECKOUT IS BROKEN due to the most recent upgrade of WooCommerce.

    I understand it was a pretty massive upgrade, but no fixes or solutions have been issued!

    Please can you look into this issue.

    “SyntaxError: Unexpected token <

    It is appearing consistently at the checkout after clicking “Place Order”

    August 19, 2015 at 5:40 am #489827
    Rikard

    Hi jewelandlotus,

    Could you try to go back to an earlier version of WooCommerce to see if that helps? Please send us an admin login so that we can have a closer look, you can post the details in the Private Content section of your reply.

    Best regards,
    Rikard

    August 19, 2015 at 6:51 am #489836
    jewelandlotus

    Sure thing.
    We can’t go back to using an old version because we just updated our code to conform to the new woocommerce upgrade.

    Thanks for the quick response!

    August 19, 2015 at 10:33 pm #490432
    jewelandlotus

    Hi –

    Please do let me know what you find…

    My business can’t function with a broken checkout…

    Thank you!

    August 21, 2015 at 6:51 am #491173
    Rikard

    Hi,

    I got a https error when trying to login, could you check please? Are you running 2.4.5? I know there were some problems with 2.4.4 so updating again might help. I would try posting your problem an a WooCommerce forum as well since I think you will be able to get better help there.

    Thanks,
    Rikard

    August 30, 2015 at 10:13 am #495434
    Alessandro Marengo

    Hi guys!
    I’m experiencing tha same error with checkout, showing “SyntaxError: Unexpected number” after click on “Place Order”.
    I only tried using BACS payment. With Paypal, I tried to cancel and come back to website, but a list of db errors came out… :(
    How do you think I can fix this?

    August 30, 2015 at 8:12 pm #495515
    jewelandlotus

    Hey,

    I never received anything conclusive from this thread or contacting through WooCommerce. I worked with my web-developer and he was able to fix the problem without much difficulty, but am not sure how he was able to do it.

    That would be my suggestion however, is work with someone directly who has expertise in wordpress and experience with woocommerce.

    August 31, 2015 at 9:26 pm #496113
    Alessandro Marengo

    Hi! Thanks for your reply.
    My expertise in wp+woo is counting years and years, but never happened such thing.
    Could you please ask your web developer what did exactly?
    It would be very appreciated. :)

    September 1, 2015 at 8:56 am #496309
    Rikard

    Hey Alessandro,

    Could you please provide us with a temporary admin login so that we can take a closer look? You can post the details in the Private Content section of your reply.

    Regards,
    Rikard

    September 2, 2015 at 11:55 am #496997
    hamzahmauzam

    I am also facing the same issue.

    September 3, 2015 at 6:54 am #497496
    Rikard

    Hi @hamzahmauzam,

    Could you please provide us with a temporary admin login so that we can take a closer look? You can post the details in the Private Content section of your reply.

    Thanks,
    Rikard

    October 3, 2015 at 5:44 pm #513170
    hansmeiser

    Hey guys, having the same problem – but only with direct debit / SEPA Lastschrift payment option.

    Pay by invoice (auf Rechnung) works.

    I sent you data in the private box below.

    October 5, 2015 at 11:39 am #513619
    Andy

    Hi!

    IBAN/BIC combination I use does not work. It says: “Der Ländercode des IBANs stimmt nicht mit dem Rechnungsland überein.
    Ihr BIC/SWIFT scheint nicht gültig zu sein.”
    Can you provide us an example IBAN/BIC combination for us?

    Cheers!
    Andy

  • Author
    Posts
Viewing 13 posts - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.