• Resolved jtonioli

    (@jtonioli)


    We have used this plugin for several years with no issues. It recently stopped sending data to shipstation from WooCommerce. We tried to reconnect the API and RestAPI and it appears to work, but when we send a test over we get a similar error. It appears to have started in July and even though we’ve tried multiple times to reconnect and even create and connect with a new store in Shipstation, it is having errors. The error code appear to show that there is a particular line of code that is having the issue. I’ve attached the error logs below that we are getting in the notifications when we try sending a test through. They are all similar, but when the error started on July 3rd, it was showing a Line 9 issue and now in August it is saying it is a Line 45 issue.

    Would love to know who I can connect with to help resolve this issue. This plugin has been fantastic for us and we’d really like to keep using it so we don’t have to do a Zapier or Make integration. – The email address was removed for security purposes but changes were made by the same user.

    08/02/2024?03:04?:[email protected]

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 11, position 43.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="n'

    08/02/2024?02:41?:[email protected]

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 11, position 43.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="n'

    08/02/2024?02:38?:[email protected]

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 11, position 43.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="n'

    08/01/2024?04:08?:[email protected]

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 11, position 43.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="n'

    07/11/2024?05:53?:[email protected]

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 9, position 36.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="i'

    07/08/2024?10:58?:[email protected]

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 9, position 36.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="i'

    07/08/2024?10:58?:[email protected]

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 9, position 36.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="i'

    07/08/2024?10:58?:[email protected]

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 9, position 36.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="i'

    07/03/2024?22:39?:?Shipstation

    An error occurred attempting to update orders: Invalid XML. Error: ''Songs' is an unexpected token. Expecting white space. Line 9, position 36.' We received: '<!DOCTYPE html> <html lang="en-US" prefix="og: https://ogp.me/ns#"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta charset="UTF-8"> <meta name="robots" content="i'
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @jtonioli,

    Thanks for reaching out.

    I understand you’ve been using the plugins for quite sometime with no apparent issues, but now it seems not to be able to send data to ShipStation from WooCommerce.

    Before we can proceed with further troubleshooting, do you remember making any changes in your store before the issue started, such as updating or installing plugin(s)?

    Thread Starter jtonioli

    (@jtonioli)

    We did have a malware issue that happened in July that we think has been cleaned up but there is a chance that could have moved something around that isn’t being picked up by a Malware scan. The hackers were able to delete some of the media files and cause a handful of other issues on our site before we were able to lock down the site and work with the Malcare team to resolve the issue. We’ve been clear for almost 2 weeks. There is a possibility something could still be lingering? I’m happy to work with someone at the plugin team to try and have them take a look at the site as well.

    • This reply was modified 3 months, 2 weeks ago by jtonioli.
    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @jtonioli,

    Thank you for sharing further details on this issue.

    As a first step, I recommend taking the basic troubleshooting steps like running a conflict test and switching to a default theme (Storefront) while only having WooCommerce and WooCommerce ShipStation Integration as the only active plugins to see if the issue could be related to any possible conflicts.

    I recommend making a full site backup, then running the tests on a staging site.

    Let us know how this goes.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.