 | | Re: shop.lego.com bug report
|
|
This sounds like a cookie problem -- possibly on your end, which is easier to fix, so it's the best place to start. Have you tried: - clearing out your cache (aka temporary internet files, but I believe in Netscape it's usually called cache). Always (...) (24 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| |
| | Re: shop.lego.com bug report
|
|
(...) rm -rf ~/.netscape/cache/* (...) UNIX versions of Netscape keep their cookies in the file ~/.netscape/cookies better than deleting the file, just edit it in your favorite editor (please, no vi/emacs holy wars here!) and delete any lines (...) (24 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| |
| | Re: shop.lego.com bug report
|
|
(...) <snip> Just an FYI, Tomas; I've noticed this error both from home & work (one is Netscape, one is IE; both on Windows 98). The standard 'bad cookie' fixes didn't seem to help (although I didn't kill my cookies at work - too much of a pain to (...) (24 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| |
| | Re: shop.lego.com bug report
|
|
(...) On Solaris, it is in the file .netscape/cookies under your home directory. It is possible that the original poster had cookies disabled, however; if so, he may need to turn them on. --Bill. (24 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| |
| | Re: shop.lego.com bug report
|
|
(...) ... (...) and (...) and William Ward wrote: (...) That was actually the first thing I tried, a long time ago. Also, my netscape cache was in a nonstandard location, but I found it. After removing all my cache files and cookies file and (...) (24 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| |
| | Re: shop.lego.com bug report
|
|
Yet another update: I've been told that along with the changes to the shop that were published yesterday, there were some additional code changes that will hopefully keep this "bad cookie" problem from happening again in the future. Of course, (...) (24 years ago, 15-Feb-01, to lugnet.lego.direct)
|
