Donation shop error [workaround found]  (Read 1320 times)

0 Members and 1 Guest are viewing this topic.

GrumpyV5

Donation shop error [workaround found]
« on: 2 May 2014, 01:35:10 »
After entering the username in the textbox the shop prompts an errormessage and still shows the textbox (see attachment). Problem occurs on IE and Firefox.

[edit] Simple workaround found by ummfredfelizco (thanks for that): Just open the one of the categories in the donationshop in a new tab. The address shown should then be http://donate.noobstown.com/ and it should work just fine.
« Last Edit: 2 May 2014, 08:40:10 by AlbatrosX5 »

Orpheus_only

Re: Donation shop error
« Reply #1 on: 2 May 2014, 02:38:32 »
I've had it glitch out like this before, and sometimes it won't accept my log-in at all. A solution I found was to right click on one of the options and open it in a new tab. Or use the url donate.noobstown.com. Something about opening the Donate page in its own tab removes the problem, as opposed to using it on the main noobstown website.


Nariaki

Re: Donation shop error
« Reply #2 on: 2 May 2014, 07:12:49 »
I think it's because your cache is too full, as Jack told me when I had that problem. Try cleaning your cache and see if it'll work.

GrumpyV5

Re: Donation shop error
« Reply #3 on: 2 May 2014, 08:34:34 »
Hm, my computer is actually set to always clean the cache when I "log off" the internet. So while that might help others with a similar problem (that might yield the same error) it doesn't seem to help in my case. :)

However, ummfred's solution was not only simple but it did actually work in my case. I'll add it to the op in case someone else has that problem someday and searches for a solution.

ItsLawrence

Re: Donation shop error [workaround found]
« Reply #4 on: 8 May 2014, 15:53:15 »
Sorry for the delayed response:

This is an error with Buycraft (the system we now use for donations) we have contacted them regarding this problem and they are looking into fixing it. We can't really do anything about this for now, so I'd use the workaround you seem to have found if it works for you at this time. If the situation changes then I'll be sure to inform you.