This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - David Johns
« on: June 12, 2015, 01:36:49 PM »
As discussed earlier, I think I led you astray in one regard. Please change the account type to "Yahoo" where I had told you to set it to "PayPal". The account can still be called simply "PayPal". As long as it has the word PayPal in it (not case sensitive) it should recognize it as a PayPal merchant account that it works with through Yahoo.
Let me know if that works for you.
« on: June 11, 2015, 01:56:40 PM »
Sorry about this issue. This is actually a known issue that has been addressed in the beta release. Please update to the beta release and see if it works better.
« on: June 11, 2015, 10:21:58 AM »
That would do it. Fortunately there's another way to do this:
- Go to "View", "Admin"
- Right click in the blank white area, where your accounts and/or batches may be listed and choose "Add Account"
- Set the name for this new account to "PayPal" and set the type to PayPal
After this, go to the site settings and select this account.
« on: June 09, 2015, 04:40:05 PM »
I did some benchmarking to see why it takes so long. I thought it might be that the majority of the time was in comparing the old products to the newly downloaded products. That is, in fact, the vast majority of the time. However, at least in debug mode on my development computer it looked like it would take ~1.5 minutes to download and load the file, then about 83 minutes to parse the 52,135 products. I didn't let it run the full time even to do that and didn't want to let it run out to complete the whole process. I just it would take the remaining ~4.5 hours to do the comparison.
Point of the matter is that the way SuperManager is accessing the file simply wasn't designed for efficient handling of this number of products. Don't misunderstand what I mean by that, however. I don't know that there is a better way to do it with what SuperManager has available to do it with. There's a chance that we could look at other XML reading libraries that may be more efficient, but it will likely still take a long time to parse the size of file it has to work with (126 MB file, by the way).
We do have some options. At the time this approach was adopted for importing product lists the Yahoo Catalog API was not available. It is possible that we could implement support for it so that you could right click on selected product(s) and choose "Update from Shopping Cart". We could also implement a function to right click on selected order(s) and choose "Find Products" to open a list of products in that order on the product list. In this way you could use the find products function to generate a list of products in a set of orders, select them all, then right click and choose "Update from Shopping Cart" to pull them in.
I'll contact you offline to scope out something like that.
« on: June 05, 2015, 03:18:56 PM »
Sorry about that. I've release another beta that I think will fix it for real. Please try updating to 22.214.171.124 and let me know.
« on: June 04, 2015, 07:04:45 PM »
This issue has been addressed in beta version 126.96.36.199. Please update to it, try it out and let us know how it works for you.
« on: June 04, 2015, 02:35:09 PM »
Thanks for bringing this to our attention. Yahoo made an update to the store manager last week. We had to release a quick update to make the "Update To Shopping Cart" still work. This function has also been affected and we'll get an update out for this right away.
« on: June 01, 2015, 06:47:16 PM »
We took another look at it and can't see a way that the charging function alone could corrupt the orders. If you haven't already switched over to using the API for charging orders, please check one order at a time for a few orders and make sure it doesn't cause any problems. I certainly don't expect that it could.
« on: June 01, 2015, 08:25:14 AM »
We'll take another look at that and see if there is a potential for problems with charging. Yes, we do recommend switching over to the Yahoo API for download, charging and updating shipment status. Unfortunately the API does not currently cover updating changes to the orders wholistically at this time. But switching over to it should certainly prevent any problems from occurring whiole charging.
Here is a link for how to switch over:http://blog.thesupermanager.com/supermanager-updated-to-take-advantage-of-yahoo-api-improvements/
« on: May 29, 2015, 02:23:49 PM »
Sorry about the hassle this caused you. We should be out of the woods on this issue. A couple of questions, however to follow-up on this.
Did you update these orders to Yahoo using SuperManager before charging them? If so, can you explain your process so I can understand why updating to Yahoo would be required within your process?
« on: April 28, 2015, 05:23:05 PM »
You got it!
« on: April 28, 2015, 03:53:20 PM »
Here are the instructions from Yahoo:http://ep.yimg.com/ty/cdn/vw/order-payment-api.pdf
Page 5 explains the process of generating a token. I'm guessing you are facing one of two issues:
- The email with the token went to your spam folder
- The email address on file with Yahoo for this type of communication is a different one than you usually use. Perhaps its an outdated email address that you no longer use? I'm guessing Yahoo support could help you figure this out and update it, if necessary.
Thanks for the correction to our instructions. I have updated the blog entry. Sorry about the confusion.
« on: April 28, 2015, 02:21:55 PM »
There are a couple of ways you can get around this. The one I would recommend is switching your store type to "Yahoo API". This will use Yahoo's API to download orders, do "typical" order charges and credits and upload tracking numbers back to Yahoo. This is much faster and a much more direct way of integrating with your store. The process for changing this is described in our blog here:http://blog.thesupermanager.com/supermanager-updated-to-take-advantage-of-yahoo-api-improvements/
Another way you could do this instead is to just switch to using SuperManager's native email functions instead of using Outlook for sending all emails through SuperManager. This is changed under "View", "Store Settings" on the "Email Settings" tab. Uncheck the option at the top "Use default mail client". You will then need to enter your outgoing email server settings so that SuperManager can directly connect to your outgoing mail server to send emails.
« on: April 28, 2015, 10:40:50 AM »
If you don't choose to have dazzle do the date advance, Amazon doesn't have a problem with the dates. SuperManager only shows this log when there is an error. It won't show it if there are only warnings, such as about the carrier name.