Our site www.viart.com site is operated by latest Viart Shop 5 with default Clear design
Topic Information
Coffeeman (Guest)
Coffeeman (Guest)
Will you be posting ALL released fixes here
http://www.viart.com/announcements.html
for download? I know I've asked support this same question before, and the answer was "what problem are you encountering?"
I don't want to have to experience a problem for which there is already a fix. If you would just always post ALL fixes here and let us apply them pro-actively, it would save a lot of grief for everyone.
Last modified: 2 Mar 2007 1:59 PM
 
Eugene (Guest)
Eugene (Guest)
Hi,
 
We shall try to publish all important fixed under this section.
If you found any bug, please report us and we'll fix it ASAP and publish here too.
 
WBR,
Eugene
ViArt Support Team
 
Will you be posting ALL released fixes here
http://www.viart.com/announcements.html
for download? I know I've asked support this same question before, and the answer was "what problem are you encountering?"
I don't want to have to experience a problem for which there is already a fix. If you would just always post ALL fixes here and let us apply them pro-actively, it would save a lot of grief for everyone.
 
Coffeeman (Guest)
Coffeeman (Guest)
Hi Eugene.
"We shall try to publish all important fixed under this section"
That's just my point. What ViArt support may not deem as important enough to post may actually be critical for one of your customers. That's why I continue to ask that ALL fixes be listed, regardless of how important you deem them to be. Let your customers decide which ones are critical to them.
 
charleshays
charleshays
Going from 2.8 to 3.0 should be fairly signficant change. But your log of changes has nothing in it. It would be nice to know what all has changed otherwise we may not need to upgrade at all.
 
Coffeeman (Guest)
Coffeeman (Guest)
Eugene
 
Here is a perfect example of a problem that could have been avoided. The customer here http://www.viart.com/undefined_variable_email.html, Martin, had to stumble on this problem when it was already known about, the fix was already available, but ViArt did not post the fix until someone reported it here.
 
ViArt KNEW THERE WAS A PROBLEM, and posted the fix afterward here http://www.viart.com/user_profile_fix_for_release_3_dot_0.html, stating the problem was not in the 2/28 download of the product, but the fix should have been posted already!
 
Is this an example of how ViArt is classifying fixes as 'important' or not? Why is it so difficult to get this point across, that ALL FIXES NEED TO BE POSTED regardless of how imported you feel they are or how many people you think they will affect.
 
Eugene (Guest)
Eugene (Guest)
Hi,
 
Thanks for your comments and notices.
 
We do our best to lessen the time needed to react on bug fix requests. We have a number of developers that can cause some delays in publishing all updates in the Announcement forum.
 
In fact this practice is rather new for us as you have noticed, and we hope we could do all to prevent our customers from getting into a confusion because of bugs in ViArt software.
 
WBR,
ViArt Support Team
 
Eugene
 
Here is a perfect example of a problem that could have been avoided. The customer here http://www.viart.com/undefined_variable_email.html, Martin, had to stumble on this problem when it was already known about, the fix was already available, but ViArt did not post the fix until someone reported it here.
 
ViArt KNEW THERE WAS A PROBLEM, and posted the fix afterward here http://www.viart.com/user_profile_fix_for_release_3_dot_0.html, stating the problem was not in the 2/28 download of the product, but the fix should have been posted already!
 
Is this an example of how ViArt is classifying fixes as 'important' or not? Why is it so difficult to get this point across, that ALL FIXES NEED TO BE POSTED regardless of how imported you feel they are or how many people you think they will affect.