404 null on every page

  • Resolved mcdeth

    (@mcdeth)


    3 weeks, 4 days ago

    Hi, I noticed today many 404 errors, all coming from woocommerce-payments. Updated to newest version

    frontend-tracks.js:1 
            
    POST /checkout/null 404 (Not Found)
    n @ frontend-tracks.js:1
    (anonymous) @ frontend-tracks.js:1
    (anonymous) @ frontend-tracks.js:1
    (anonymous) @ frontend-tracks.js:1
    VM974:1 Uncaught (in promise) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter mcdeth

    (@mcdeth)

    Problem solved, I was logged out somehow and it didn’t show notifications anywhere but console

    Plugin Support Beauty of Code (woo-hc)

    (@beautyofcode)

    Hey @mcdeth ,

    Glad to hear that this has been sorted! I’ll go ahead and mark this as resolved then, however feel free to create a new topic if you need any further help. ??

    Cheers!

    Actually, i’m facing exact same issue just after an update, but in my case – i’m logged in, hovewer, it doesn’t matter. I’ve noticed that this issue (console error) happens on:

    • cart page (not checkout)
    • single product page

    It adds /null in the console at the end of a link and then, right below, VM974:1 Uncaught (in promise) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @johnwandler,

    Sorry to hear that you are experiencing the same issue.

    However, to align with?forum best practices, please create a new topic so that we can address your issue(s) separately.
    You can create a new thread here:?https://www.ads-software.com/support/plugin/woocommerce/#new-topic-0
    Thanks for understanding!

    Thread Starter mcdeth

    (@mcdeth)

    check woopayment settings if you’re logged in (wp admin > payments > settings? or access from plugin page)

    • This reply was modified 3 weeks, 3 days ago by mcdeth.
Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.