It would appear the store still cannot tell that you have already bought an item — even if it’s a freebie. I just put the Genesis Bracers in my cart (because it came up in the New Items) then wondered if I hadn’t already downloaded it. Lo and behold, I had, just yesterday. But not a peep out of the store software about having already purchased this product.
This was something that it was known would not be working on launch, it isn’t a bug. As a result I wouldn’t expect it to change until the main bug-swatting is done.
Huh? This is the first time I see someone from DAZ mention that they knew the new site was not working properly before it was released. So they were just surprised that the problems are far bigger than they thought they would be. I feel like a guinea-pig right now.
We are guinea pigs right now. But in a good way (or at least necessary way).
I’ll explain what I mean in agonizing detail.
Sounds like a low-priority bug, or it needs a change to be made (options, new/modified code).
You do the bug hunt before you make make lots of changes. Every change complicates troubleshooting. Biggest bugs first.
When they first call tech-support (if available) they want to be able to say “This is my store, on your software. WTF?.” Same way for consulting the manuals. (The company tested the default software, and maybe a few option changes, they can’t test it all).
I’m not a pro - but this is the order to do it in: (List may be incomplete, or contain amateurish inaccuracies)
This list doesn’t account for anything like changing drivers, or the changing stuff with various bits of equipment (which may have it’s own software) that interfaces with the new software.
1) Set it up for your use, changing as few defaults as possible. (Load the store & forum, do the minimal necessities).
2) Test. 2b)*** Get it to an apparently-stable state. (***I don’t want to renumber).
3) Stress test (put it online).
4) Bug hunt.
5) Kill all possible bugs.
6) Test after each bug-kill.
7) Kill any bugs caused by each bug-kill. 7b)*** Test each… ad infinitum. (***I don’t want to renumber).
8) Change defaults the way you want.
10) Customize (add/modify code) (one at a time)
11) Test each change.
12) Keep going until you just accept that nothing’s perfect.
That being said, this sure isn’t a very good advertizement for the software. }:->