Miva Merchant 5 Proves Problematic
Product import problems, lack of modules, lack of documentation, price group bugs among other nasty critters, and lack of admin features without the OpenUI Look and Feel are just a few of the problems plaguing end-users of Miva Merchant 5.
The latest problem is huge. A core update has left many stores crippled. Unlike OpenUI, there is no rollback feature. For more details on the latest problems, see this thread on the users list archive.
November 20th, 2005 01:17
I create tutorials for Miva Merchant. I’ve been trying to create tutorials for MM5 as a way to overcome Miva’s lack of docs. However, even I can’t figure out most of the stuff. It’s catch-22.
As a developer in the MM community, I see a huge drop in MM users. Very few are starting with MM4, and those who start with MM5 are dumping it fast as you can see in the lack of activity on the MM5 user list. It’s a great day for MonsterCommerce, ProductCart, ShopSite and the rest. It’s a bad day for us.
November 20th, 2005 09:32
As a host, I am frustrated with Miva Corp. They insist that we push Merchant 5.
Let me see…if I went to a car dealership, and purchased a car, with no owners manual, no technical manual, no service manual, then got it home and found the radio only tunes to 2 stations, the air conditioning didnt work, it only allows you install one manufacturers type of tires, and hardly anyone in the industry has any after market parts for it.
Then you take it to the dealer to get it fixed, only to find out they fixed the air conditioning, but broke your heater.
I’d be just a bit upset.
Thats sort of what we have here. A broken product with no documentation or technical reference manuals.
I honestly cannot market and sell a product in which I cannot give my customers the know how to use.
Now Miva’s gone and hired another DocWriter. Fabulous! Then we find she has been tasked with producing docs for a new product that hasnt even hit beta yet.
HEY MIVA! Time to wake up. How about concentrating your development efforts on fixing your flagship product first - before writing new software. And hey, a novel concept - How about docs for products that already are in use?