I upgrade to 1.70 and I still can't update ebay categories.

Now, as an additional annoyance, every time I look throught the items in my batch, a message pops up saying that if I save the item, I will lose my custom categories.

I'm also getting the errors on uploading batches.

It's been months since misterposter has worked properly and all we're getting is slow "fixes" that aren't fixing anything.

Are you EVER going to get misterposter working again?

Hello,

That message you see when looking through your batches will go away once you update your store categories.

What error do you receive when trying to update store categories?

-- Auctiva David

"Problem checking for store category updates.

AuctivaError Ebay.Service.Core.Sdk.ApiException: the authentication method you are using is invalid."

followed by a long list of tags which I can't cut and paste.

but calls were to

SendRequest
Execute
GetStore
Page_Load

I do appreciate your looking into this, but I'm also getting "the paramater is incorrect" xml error when I try to upload a batch which I've been getting regularly since before Christmas.

Any idea when/if you'll have that one fixed?

I've had the same problem all year too. I upgraded to 1.70 and couldn't even post ONE item!

Is anyone listening?

I am having the same problem. I have regenerated my authentication token, so that's not the cause. The problem occurrs within the API call. Could someone please do something about this?

OK, I've figured out what's wrong with Auctiva's programming. Previously the call to get Store Custom Categories could be made to the API using a generic token (ie. Auctiva's developer token which can be used to get public info from eBay). Now they've changed it and the GetStore call requires a user specific token (ie. the authentication token for the user who owns that particular store). It doesn't matter whether a user's authentication token is up to date or not, because Auctiva is sending the wrong token. This results in Error 16112 which flat out denies the request to authenticate at all because the API can tell the wrong type of token is being sent (as opposed to authentication proceeding but failing because a user specific token is incorrect or out dated, which is a different error all together).

Sooooooooo, you guys just need to change the XML for that GetStore call to send a user specific token and everything should work great. So pretty please with sugar on top, could you fix it so I can list?

Hello spam10,

Unfortunately Mr Poster already sends the user's personal token to eBay, not a generic one. So that error should only be generated by eBay when your token is invalid. If what you say were true, then NO user would be able to update categories. However, that isn't the case.
Have you filed a support case regarding your specific issue? We can look into it further then.

Thanks,
Auctiva David

Auctiva David,

If the problem was that my personal token was invalid, wouldn't regenerating the token fix the problem?

Because I regenerated the token and it didn't fix the problem.

Yes I filed a support request. In the request I specifically said that I had regenerated the token and it did not help. I filed the original request on 7/2. I got a reposnse on 7/2 but all that person was able to tell me was that no one could help me until 7/5 because of the holiday. Finally, today 7/7, I got a reply. I was told that they had deleted my token and to regenerate it because that would surely fix the problem.

Gee, thanx so much for that. Not only did that do absolutely nothing to fix the problem, but it left me with the feeling that customer support didn't even bother to read my suppot request.

It's still broken. Regenerating the token doesn't fix it.

The users peterpalma, vevee, and Dflyweb also report having the same problem with updating store categories as far back as june 6. I see their posts on the board reporting the problem and saying that the problem was ongiong, but no posts saying anything was done to fix it. Regenerating the authentication token didn't help them either. (This is the main thread http://community.auctiva.com/eve/forums/a/tpc/f/945609321/m/8501046071)

So, was anything ever done for any of those users? If so maybe you could find out what it was so I could use the same fix. If not, maybe you could cross-reference all the support requests so that everyone can have their problem solved.

Hi spam10,

Both Dflyweb and Vevee received different errors after regenerating their tokens (they did not continue to receive the invalid token error.) Vevee's issue was resolved several weeks ago, as you can see on the second page of that thread.

I believe the same workaround we figured out for Dflyweb could work for you as well, even though you have a slightly different problem. I have passed it on to the support staff so they should be contacting you again shortly.

I apologize for all the confusion,
Auctiva David

This message has been edited. Last edited by: Auctiva David,

David,

My problem was never resolved. I filed a support request, and never received a resolution to my problem. Regenerating the token made no difference. I was never able to update my store categories, and can no longer list using 1.70. I have moved on to another bulk listing program out of necessity. I have used Mr. Poster from almost its beginning, and appreciate all the work auctiva staff did to enable me to list thousands of auctions. At this point its no longer a viable option for me.

Here is the last message I had from my support case:
from John L.
Mr. Poster Support
Posted Friday, June 09, 2006, 2:47:22 PM
Hello,

We have forwarded your issue to our developers. It is currently under review. They will have a solution for you as soon as possible.

Auctiva Support

Hi Dflyweb,

I am going to personally follow up with this case to make sure you get that solution delivered on Monday (along with spam10 as well).

It's been 10 days since your response.

Any chance of a fix?