There was a note from Brittney from DAZ but it was removed. The same bug persists as from the old site…. I was hoping that this was going to be resolve with this new software, apparently not… I clicked the link to come out to the forum and was told that the thread does not exist. SIGH….. DAZ DAZ DAZ…. *spanks DAZ HARD*
I got the email with that message in it, too. I had to go to the forums menu and trace into this thread again. DAZ3D definitely had told us that this wouldn’t happen with the new software. Now if the folks at Magento told them that, then they have reason right there to take them to task about this fiasco. What else did they lie…err…make misleading statements about?
The only worse software rollout I have ever seen was one where I was brought in to fix someone else’s mess. It was for a collection agency. Custom software had been written, but the “contractor” had written very, very bad code. Didn’t follow even the simplest rules. For example:
It was not a complete application yet, but they told the people they could go ahead and use it for production data, for live business!
They had no enforcement of clean data…
duplicates of key values were allowed;
blank key values were allowed;
there were transaction dates in the future.
After a long walk through the application and the code, I told the person who hired me that it would be best to rewrite it from scratch, using the database structure that was already in place, with some modifications, and after I cleaned the data as completely as possible. It took me about a year to complete the project, but they had a solid application without errors, and it even printed checks. Can you imagine a collection agency taken to court and not having proper data to back up their claims?
Your honor, this payment was made on December 18, 2005.
But today is only October 23, 2002!
Yes, your honor, but I assure you this payment was made.