Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Bas Elbers

    (@baaaaas)

    Please save options and try again or delete all plugin files and download again. Can’t seem to get the error my self.

    Plugin Author Bas Elbers

    (@baaaaas)

    Did you get it to work? Please let me know. ??

    It also has the same problem

    Had the same problem, the mPDF debugging option was enabled.
    Disabled and it worked ??

    Where can we see the mPDF debugging though ? In a specific log file ?

    Unfortunately disabling mPDF debugging did not help for me; here (latest Woo + Subscriptions) only deactivating the plugin(s – using premium) solves the issue. Any updates?

    Thanks!

    Plugin Author Bas Elbers

    (@baaaaas)

    Will find the problem as soon as possible. Thanks!

    Thread Starter deb

    (@debendra)

    I love this plugin, it worked as I have reinstalled …

    Any updates on this? The error is about receiving malformed JSON on a shop order, instead of a JSON response it gives an error that the PDF already exists and needs to be deleted (but it just got generated when the order was made, so this makes little sense). This error is in plain text, therefore it gives a syntax error.

    Managed to fix this by changing the Invoice number type to WooCommerce Ordernumber, the autonumbering by the plugin itself seems to be horribly bugged.

    Plugin Author Bas Elbers

    (@baaaaas)

    I did a quick look yesterday and come across this error. Please try to delete invoice and try again. If you can’t find invoice in orders admin page, just manually delete invoices in wp-content/uploads/bewpi-invoices. I have to change the code to just not create the invoice when order has been made and invoice with invoice number already exists.

    This happens when you reset the invoice number to a number which an invoice already is generated with. Also the problem could be that the order has been deleted while the invoice is not. I will look into it asap!

    Plugin Author Bas Elbers

    (@baaaaas)

    This has been resolved in version 2.3.4.
    Please confirm so I can close the topic. ??

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘SyntaxError: Unexpected token C’ is closed to new replies.