Sorry CS people but here are my experiences with 2.0.5 which I personally rate as very poor.
1)Nochex APC (cannot get to work, not a server config problem, correct permissions etc, cURL is correct and works perfectly with Paypal IPN, was fine with 1.3.5 also. (see my other post for the full lengthy details of this).
2)Want to benefit from Firefox browser security over IE, think not in the Admin side, half of the links don’t do anything when clicked, had to resort to chedder cheese secure IExplorer (same applies to the CS-Cart Demo Site.
3)Users Carts log is useless, also on the CS-Cart demo site, why not log on and try for yourself, look at the user carts then fire a browser off and add items to cart, if you are lucky enough you will find them in the same user cart as everyone else has used, therefore making this feature redundant.
4)Only tried this on the Electro Skin, when categories have more items than will fit on a seperate page, you will get page 1,2 etc which is fine, try clicking on page 2 then trying to click page 1 again, ain’t gonna happen in FF3.5 or IE8.
5)Allow items to be sold as Pre-Orders, seems like a total waste of effort, cannot get this to work at all on my server or the CS-Cart Demo Site (Snow’s preorder mod was the way to go)
Loads of other annoying little issues to top it off.
Why go backwards, 1.3.5 was absolutely rock solid and have used it without problems for the last 12 months with almost 6000 orders, would have surely been better to build on that rather than to start something else full of bugs to squash.
All I can say is thank god I kept the 1.3.5 in a seperate folder after upgrade along with its database intact, managed to stick with 2.0.5 for no more than 24hrs before blowing my lid with it and deciding to go back.
The skins on 2.0.5 are quite decent though BUT not something that an average user can’t create for themselves.
Hi,
This is good to know, I will keep my money in my pocket and stick with 1.3.5
Sounds like the CS-Cart team need to get their act together. Everything about this new version has been poorly done - look at the database upgrade script for example.
Regards,
Graham.
Hi there, don’t blame the upgrade script, I have to admit it’s not perfect, however, it did upgrade 1.3.5 SP4 to 2.0 branch smoothly.
Tip: Use FF for all the upgrade process.
Give the team time to fix all the bugs, thanks for the bug report.
2.0 branch actually is quite ‘stable’ it’s just nitpicking small issues.
Everyone I’ve assisted so far has had server setting set incorrectly or didn’t take the most logical action to fixing something.
[quote name=‘JesseLeeStringer’]2.0 branch actually is quite ‘stable’ it’s just nitpicking small issues.
Everyone I’ve assisted so far has had server setting set incorrectly or didn’t take the most logical action to fixing something.[/QUOTE]
I agree. Sure there are some problems (heck, I have a few bugs that have been outstanding for over a month) but I am kind of surprised how stable it is given that it is basically a complete rewrite.
If someone is happy with 1.3.5, then I am not sure why they feel the need to rush to the new version. If the answer is "because it has these new features, then they were not completely happy with the prior version. Life is full of compromises.
Bob
[quote name=‘GT40Graham’]Hi,
This is good to know, I will keep my money in my pocket and stick with 1.3.5
[/QUOTE]
Graham, you don’t have to pay anything to upgrade to 2.x if you already have 1.3.5…
i have to much on the line to risk down time… like mama always said " if it aint broke don’t fix it "
and 1.35 aint broke for me
I did 2 sites with 2.05 and no issues. Love the new version
Fresh install with importing data
[quote name=‘Herbaria’]Graham, you don’t have to pay anything to upgrade to 2.x if you already have 1.3.5…[/quote]
He may have to, CS-Cart changed the license agreement last year requiring upgrades be paid for after a certain date
You can log on to your help desk account and go to the Licences/Updates section and it will have in there “Upgrades available to …” and the date.
I’m not for sure about all the bugs listed, but from what I’ve seen and messed with so far, I’m going to stick with our current versions and look at this version next year after more bugs are worked out. I see no reason to throw out the old that is working pretty smoothly…finally!
My conversion rate plumetted after going to 2.0. Have moved back to 1.3.5.