• Hi, I just bought the premium version.

    When I Replace WooCommerce Statuses with Status Tracking Statuses I get the error below.

    When WP Debugging,
    SyntaxError: Unexpected token < in JSON at position 0

    Console Error:
    ajax=checkout Failed to load resource: the server responded with a status of 500 (Internal Server Error)

    Hope I can solve the ASAP

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor etoilewebdesign

    (@etoilewebdesign)

    Hi bemypet,

    Could you please check which version of the plugin are you using? We fixed this issue in version 2.11.1 where new WooCommerce orders didn’t have statuses with “Replace WooCommerce Statuses” turned on. If you are on a version before 2.11.1, please switch to the current latest version 2.11.2 and it should be fixed.

    Thread Starter bemypet

    (@bemypet)

    I’m currently using Version 2.11.2 (the latest),

    and the problem persists.

    Plugin Contributor etoilewebdesign

    (@etoilewebdesign)

    Hi t00k,

    Since you mentioned that you also see any error in the browser console relating to admin-ajax.php we suggest you to contact your website host, since they do tend to have triggers in place if a file is unexpectedly requested more than any other file on the server(admin-ajax.php seems to be one such file).
    Also, do you have any characters such as apostrophes or quotes in the name of the status, since it could also incorrectly conflict with the SQL queries and create such errors?

    Thread Starter bemypet

    (@bemypet)

    Hi, I’ve looked at Woocommerce Integration.php codes and I think it’s related to the Woocommerce language I’m using.

    I’m using a Korean version of Woocommerce and I think this is the cause of the problem.

    Could you update this in the further versions?

    I think I can handle this by directly editing the plugin php files for now.

    Plugin Contributor etoilewebdesign

    (@etoilewebdesign)

    Hi bemypet,

    Thanks for updating us on the issue. We have noted this down and shared with our developer.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Error when replacing WC status with Status Tracking’ is closed to new replies.