Am i the only one that feels that 1.3.5 is a little premature to be released, considering that this forum is no being littered with suggestions of bugs and more bugs.
Although i am sure the Devs are working hard to bring out more updates, this forum from a personal point of view does not look pretty at this moment in time.
In light of this i did upgrade, then thought better of it and am sticking with 1.3.4 / 3.
The only advice i can give is that you may well be better off not upgrading just yet if you are happy with what you have especially iof you have a few mods - if it ain’t broke then don’t fix it.
If your a newbie then i cannot see what you have to lose.
Oh and by the way, dont expect to be able to simply update your database, as this has had a few modifacations too … don’t ask me exactly what they have done as i am not mysql database expert, You have been warned
if you don’t have to upgrade then don’t, why fix something that isn’t broke, also no one should ever expect to do an upgrade without a few headaches, if you have even a slightly modded store your upgrade will not go smoothly and I see this being the majority of problems folks are having. It’s a good idea to just keep a running tab of mods you have done with detailed instructions and then just upgrade and re-apply your modifications…
It is clear that the 1.3.5 release is premature.
However, as I have said elsewhere, I NEVER upgrade a live site (regardles of software) without first testing the upgrade with a copy of my live data. This allows you to not only test the new features before going live but also allows you to work out any bugs in the upgrade process. It is really a case of “hope for the best but be prepared for the worst.”
This really demonstrates the value of helping to test the beta releases. Perhaps if more people had tested the betas and reported bugs, we would have been much further along when the final was released.
I will say that the developers have been pretty quick to get reported bugs resolved and look forward to seeing SP1.
Bob
when the beta was out I built my store in it, i reported all the bugs in it so now im not having any problems,
any software that is released will have bugs, even Microsoft has a lot of bugs in vista, with the millions they have you think they could fix them 
but with cs cart 95% of the bugs are from upgrading
do a clean install, then find the bugs 
1.3.4 has had bugs fixed in it since it was released. It’s not unusual. The main thing is making sure that urgent bugs get fixed quickly, whoich CS Cart are very good at.
But I do agree. Don’t upgrade unless you really need the features offered.
[quote name=‘jobosales’]It is clear that the 1.3.5 release is premature.
However, as I have said elsewhere, I NEVER upgrade a live site (regardles of software) without first testing the upgrade with a copy of my live data. This allows you to not only test the new features before going live but also allows you to work out any bugs in the upgrade process. It is really a case of “hope for the best but be prepared for the worst.”
This really demonstrates the value of helping to test the beta releases. Perhaps if more people had tested the betas and reported bugs, we would have been much further along when the final was released.
I will say that the developers have been pretty quick to get reported bugs resolved and look forward to seeing SP1.
Bob[/QUOTE]
Though i fully agree with what you are saying, i cannot help but to remark on some of these so called ‘bugs’. They do not seem to be bugs as such, but rather a complete nightmare for existing users. I would have thought that to ensure that the bugs are fixed that users would be able to at least upgrade, but thats the nightmare in its self.
It would have been a more sensible approach by the Devs to suggest a new complete install and do away with the upgrade part for now at least as this new cart reaches pushed the boundries somewhat.
Even if it the upgrade did go well i would still be somewhat suspisious as to whether scripts were going to show errors.
For me, well im staying well clear for the time being and probally going to follow Zyles at some stage soon anyhow.
Many of the problems upgrading seem to result from the using Store Manager. Others have had success upgrading manually as long as they understand all the steps involved. While the concept for Store Manager is good for a easing the upgrade process, the results seem to be the opposite.
Again, no one should upgrade a live site without doing a dry run and documenting every step, preferably using a copy of their existing data.
Bob