An interesting, perhaps shocking error in viart shop 3.3.1:
 
error info:
 
--------------------------------------------------------
DB ERROR 1054
 
We are very sorry, but an error has occurred while processing your request. Please try the operation again by either pressing the Refresh button on your browser, or by going back one page using the Back button. If the error persists, please contact our web development team.
 
The details of the error are shown below. Please quote this in any correspondance regarding this problem.
 
Database error: Invalid SQL: SELECT layout_id, menu_order, menu_title, menu_url, menu_target, submenu_style_name, menu_image, menu_image_active, show_non_logged, show_logged, parent_menu_id FROM va_header_links WHERE menu_id=138
MySQL Error: Unknown column 'submenu_style_name' in 'field list'
--------------------------------------------------------
 
And when I look at the database I find the sub menu style column named as sudmenu_style_name !!!!
I am flabbergasted by this silly bug I found in viart 3.3.1, if it were a scripting bug or one caused by wrong logic, I wouldn't mind because I know that no software is 100% bug free but a TYPO IN A TABLE COLUMN NAME wtf!!! It concerns me quite seriously and shows the level of sanity you have worked with on this version. I feel that am losing confidence in this version of your product and now, I am pretty sure that original Viart System is not even developed by you guys because someone who can develop such a high quality and amazing system can never be this careless. For your information, I have just lost my client because of this utterly stupid bug!

I think that most of us, when finding such a problem, simply send a support ticket and it is resolved straight away

Well, I've had my developers resolved the problem long ago but that after losing the client and I dont care about that I've lost that one client. The point is that the level of testing and QA or sane development for that matter put into the new version has been exposed to me and this what is causing a great deal of concern and I've already seen atleast a dozen of other bugs in the system but didnt bother to report them coz I can have them fixed myself. But a typo in a table name just pushes the limit!
 
As a customer I demand an explanation about the issue. Do they have any testing process at all? if yes, how could they miss out such an obvious one? Who is to blame for my loss? Should I be using this system at all?

Ive just checked my 3.3.1 and the mis-spelling isn't there. I also can't find an upgrade fix for this problem.

Hello,
 
Thanks for the comments.
 
We'll make an attempt to explain this. Of course, all features that we implement to our new releases are passed through testing, but it usually depends on the time we have before a new release. Version 3.3.1 included a lot of functionalities and numerous clients were waiting for the features that they ordered. So, we decided to issue the release faster and so we had not enough time for testing.
 
Please, note that all you have to do is report us about the bug at once and we make all possible efforts to solve it immediately and put an appropriate announcement to our Announcement section. Unfortunately, it is rather difficult to test all the new functionalities to be compatible with the old ones as so far our shopping cart is rather huge and includes numerous features and settings that are to be tested throughout. That is why we appreciate it much when our clients report bugs and we are always ready to fix them as soon as possible.
 
Please, do not hesitate to send the request or report any problems to our support center (support@viart.com). We are open to your comments and questions.
 
With kind regards,
ViArt Support Team
 

Hmmm., ok so ur telling me that the increased number of bugs is because you did not get enough time for testing this version, fair enough and perhaps explains why this kind of issues were not there in earlier versions but nevertheless IT IS YOUR RESPONSIBILITY TO KEEP THE VERSION MARKED AS BETA until you thoroughly test it so that the end user will not be affected, in my case I have lost a contract and it has a huge negative impact on the *good* image viart had in my company. Further, it is frustrating to report and wait for a patch and then find another bug and then report again, its like we are doing testing for you with our client's live data. Thereby, I request you to release a version 3.3.3 which would be a *THOGOROUGHLY* tested and QAed version of the current viart version, I dont mind even if I have to wait for a couple of months for this release but when it finally comes out, It has to be up to the *viart standard*. Please STOP working on any features and FULLY FIX the ones you currently have. I like viart and I do not want to see my company going for another product unless you refuse to do the above.
 
Thank you.

Mark
 
Why are you such an unpleasant person?

This is a bogus accusation!!! See blow. submenu_style_name is spelled correctly! V3.31 does have some problems, but NOT this one.
 
mysql> desc va_header_links;
+--------------------+--------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+--------------------+--------------+------+-----+---------+----------------+
| menu_id | int(11) | NO | PRI | NULL | auto_increment |
| layout_id | int(11) | NO | | 0 | |
| parent_menu_id | int(11) | YES | MUL | 0 | |
| menu_path | varchar(255) | YES | | NULL | |
| menu_title | varchar(255) | YES | | NULL | |
| menu_url | varchar(255) | YES | | NULL | |
| menu_target | varchar(32) | YES | | NULL | |
| menu_image | varchar(255) | YES | | NULL | |
| menu_image_active | varchar(255) | YES | | NULL | |
| menu_order | int(11) | YES | | NULL | |
| show_non_logged | tinyint(4) | YES | | 1 | |
| show_logged | tinyint(4) | YES | | 1 | |
| submenu_style_name | varchar(64) | YES | | NULL | |
+--------------------+--------------+------+-----+---------+----------------+
13 rows in set (0.11 sec)

First, tell me how pleasant you would be if your company relies on your choice of a system and loses a big contract because of it? I am not saying that ViartShop is bad, it is without doubt the best e-commerce system ever. But the company behind it seems to have started to ignore the quality process and this is making ViartShop lose its USP i.e., consistency and bug free code.
 
Second, its not a bogus accusation, the software was downloaded at Monday, October 29, 2007, 3:57:56 PM and below is the chunk from .sql that creates the table with the misspelled column name:
 
DROP TABLE IF EXISTS va_header_links;
CREATE TABLE va_header_links (
`menu_id` INT(11) NOT NULL AUTO_INCREMENT,
`layout_id` INT(11) NOT NULL default '0',
`parent_menu_id` INT(11) default '0',
`menu_path` VARCHAR(255),
`menu_title` VARCHAR(255),
`menu_url` VARCHAR(255),
`menu_target` VARCHAR(32),
`menu_image` VARCHAR(255),
`menu_image_active` VARCHAR(255),
`menu_order` INT(11),
`sudmenu_style_name` VARCHAR(64),
`show_non_logged` TINYINT default '1',
`show_logged` TINYINT default '1'
,KEY parent_menu_id (parent_menu_id)
,PRIMARY KEY (menu_id)
);

Mark, I have to go along with "Tiresome".
If you have a problem with Viart you should talk to them.
I think that most visitors here feel like us that there is no cause to be abusive in a public forum.
 
I, like many others, have found Viart people extremely helpful — from your comments it appears that you have not bothered to put in a support ticket. My apology if this is not so, but it is the fair starting point for a problem that is so serious for you.
 
We are all relying on Viart software; but we get action quickly by talking to them and not abusing them

Well, I had not intention to be abusive, if anyone has been offended by my comments then apologize for it. But nevertheless I request viart to release a version 3.3.3 which would be a *THOGOROUGHLY* tested and QAed version of the current viart version, I dont mind even if I have to wait for a couple of months for this release but when it finally comes out, It has to be up to the *viart standard*.

Hello to Everybody,
 
Please, find below some of our comments.
 
Actually, the typo in the table name existed in a few latest versions and those who made an upgrade from some previous versions, haven't experienced problems with the mentioned field and thus the error did not occur. In other cases, the clients could face this error.
 
Good news for Mark: We can assure you that our next release will be issued without any haste and we will do our best to conduct a proper and throughout testing before issuing the release. Or at least, there will be some beta version for those who will be in interested in getting the version faster.
 
And we would once again advise to contact our support Center (support@viart.com) for any urgent matters or bugs. We are open to solve them as soon as possible.
 
Please, accept our sincerest thanks to everyone who's been helping to test our system and find the bugs. We appreciate it very much as well as your opinions about our software.
 
With kind regards,
ViArt Support Team
 
 

Mark, people like you with that kind of negative response should not be using Viart at all. Go use another product and let the Viart guys do their work.
 
Just bitching and taking cheap shots (and not going the normal support route) shows how incompetent you and your company is.
 
DickS

I think this thread should be closed since Anjula Sheichenko has replied and stated Viart's position in this situation.
 
There is no need to get furious.
 
Bugs are a part of ecommerce systems :)
 
Just report them to viart and they will solve it :) simple

Sadly bugs are part of any software and the only thing that will stop it is thorough beta testing by as many people as possible. It is my understanding that these forums are for Community Support rather than Official support. As such anything urgent relating to your store should be taken to Viart directly as we users are unable to respond correctly or fix the system.
 
There is never an excuse for abusive comments unless (and even this is childish), a Viart representative has been abusive to you.

ViArt is one of the best E-Commerce softwares I have seen so far. I have experienced prompt replies and good customer support from their side. I am satisfied with this product, and fully I understand that each version may have bugs, and if they get patched soon it should not be a problem at all.