Import Failure
-
After having this issue multiple times, I deleted all items from WP-Lister then ran a new Inventory Report. I attempted to import just 1 item and the form returned this:
Couldn’t fetch URL http://www.amazon.com/dp/B00CBAN6XA/ – server returned error code 503
Couldn’t fetch URL http://www.amazon.com/dp/B00CDH43I8/ – server returned error code 503
The item was indeed imported but, WP-Lister gave it the SKU B00CDH43I8, rather than the SKU already assigned to the item on Amazon and the SKU shown on the Import screen.
What am I doing wrong?
-
The 503 error is an error caused by your host. A 503 error is defined as:
The Web server (running the Web site) is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay
Doesn’t that refer to the server throwing the error, meaning that Amazon is returning the 503, not my server. If it is my server, does that mean code within WP-Lister is causing the error? I can’t imagine how that is possible unless the requests made to Amazon are GET and the URI is too long. But even that shouldn’t be caught by my server.
Matt, when you imported the item, did you already have an item listed on Amazon with a custom SKU or did you just import the listing and allow WP-Lister to create a SKU?
John, as for the preview of the report, everything is correct there, on every single line. I noticed that if the item has to be IMPORTED then, WP-Lister uses an ASIN as the SKU, but if the item is to be UPDATED everything works fine. So, I am pre-creating all items in Woocommerce to match what I have listed on Amazon, then I will attempt the complete import again. I’ll post my results when finished.
My server logs every server error and ever PHP error. I just reviewed the log from the day I installed WP-Lister and there are no 503 errors or PHP errors related to this. The only errors listed are
PHP Deprecated: Automatically populating $HTTP_RAW_POST_DATA is deprecated and will be removed in a future version. To avoid this warning set 'always_populate_raw_post_data' to '-1' in php.ini and use the php://input stream instead. in Unknown on line 0I’m looking into whether or not that error is related to this issue. That error has occurred once per day since I installed wordpress. There are no other sites or frameworks running on this server. I am about to attempt the import again with a fresh report. I’ll post what happens.
Ok, I just attempted an import with a fresh report, on a single item.
After pulling the report from Amazon, I chose to “select rows to process” then selected a single item. That item was set to “import” and showed the SKU as 13011718, and the ASIN as B015TUOGPA, all of which was correct. I then clicked “process selected rows, which reloaded the page with a message that said “1 item added to import queue”. I then clicked the Process button, the import screen popped up and the import completed without any errors or messages. But, after the import, I went to check the item and the SKU had been set to B01DFXJM0C.
Worse yet, WP-Lister created and associated a new listing with the SKU it made. So now I have an extra listing that is not connected to any of my inventory management systems because the SKU doesn’t match the convention.
Matt, if you would like to me move this discussion to the support ticket system I will, but these kinds of things should be public incase another user runs into this problem before it is fixed and WP-Lister is updated. I am a developer too and I get not wanting this out there but, regardless of our feelings about our work, “open source” sort of requires transparency in development.
- The topic ‘Import Failure’ is closed to new replies.
