I'm having problems with registering with the Market.
1. go to Account Settings -> Web Services
2. Select "Centrepoint Marketplace" from the left-hand box.
3. Select "Character Status" from the right-hand box.
4. Optional: add Comment
5. Click "Add Authorization".
6. Optional: remove all rules for Centrepoint Marketplace except WSgetHandle and WScharStatus.
7. Click the link below.
8. Optional: After the registration is complete, you can delete the rules for WSgetHandle and WScharStatus.
Every time I do Step 7, clicking the link. I get the "You have been Banned" sign. I am sure that I am not logged in at two seperate browsers and I'm at a loss to what's going on.
Edited By: Razhar Kalmn on Year 8 Day 46 0:25 ____________
I redirected him to post here after I tried the registration process myself and it worked perfectly well ... but since he reports getting SWC's "You are Banned" screen, I figured that the problem might be on this end.
I'm not sure what you mean, but even if it was configured, this is just clicking a simple link which brings up the "You have been Banned". If this is related to the database, should I post in; "Questions for the Admins"?
Edited By: Razhar Kalmn on Year 8 Day 50 23:55 ____________
FWIW: When I first tried to sign up to Centrepoint Market (a few weeks ago), I had problems completing the process (I did not get the banned message --- it just did not complete after I seletred the web services). I was using Windows Explorer. When I tried signing up using Firefox, the whole process worked first time.
There is no god but Ara... All will walk his path...
Reading your message, I did a experiment. All previous efforts had been done on Firefox, so I decided to try it on Internet Explorer. Surprisingly...it worked. Amazing that Firefox has it's downside. I then logged in on Centrepoint Marketplace on Firefox and it worked perfectly.
I'll like to thank you guys for your time, in helping me, especially Togan Jano, who responded immediately. I guess it's my side, not SWCombine. So my apologies. This thread can close now, I guess.