BV Commerce Forum
»
BV Commerce Support
»
General Support
»
SP3 has been out for 4 days and there are already 4 hot fixes
Rank: Member
Joined: 3/4/2006(UTC)
Posts: 121
|
I can't think of anything else to say.
|
|
|
|
|
|
Rank: Member
Joined: 1/3/2004(UTC)
Posts: 1,497
|
Not trying to defend BV, but all the fixes so far have not been to any of the store code, just the SQL stored procedures. As Marcus stated in this thread ( http://forums.bvcommerce.com/default.aspx?f=88&m=52168): Originally Posted by: "Marcus" 
The issue has been traced to an incorrect SQL script included with the SP2 to SP3 patch. The data script included was actually the rollback script. It does no harm to your database but it also fails to correctly install the required new table rows for SP3.
I suspect this was the cause of many of these issues. Some of these problems didn't occur on the full/new SP3 stores, just the patched SP2 to SP3 stores. |
|
|
|
|
|
|
Rank: Member
Joined: 3/4/2006(UTC)
Posts: 121
|
Thanks Chris, that's helpful to know. I think it is still indicative of a lack of thorough testing.
Rick
|
|
|
|
|
|
Rank: Member
Joined: 1/3/2004(UTC)
Posts: 1,497
|
While this hasn't been official yet, this thread has a fix the affected the code: http://forums.bvcommerce.com/default.aspx?f=88&m=52166 |
|
|
|
|
|
|
Rank: Member
Joined: 4/10/2006(UTC)
Posts: 462
|
|
Netriplex Corporation<br /> |
|
|
|
|
|
Rank: Member
Joined: 4/30/2007(UTC)
Posts: 383
|
As long as the issues are fixed...what I worry about in an SP3.1 is support being lost/muddied for early adopters.
|
|
|
|
|
|
Rank: Member
Joined: 3/1/2006(UTC)
Posts: 1,142
|
Two of the hotfixes are for the search stored procedure, in order to improve the results coming out of it, one fix is for a fairly rare occurrence where someone created products as inactive, then added children, then turned them to active. Then in SP3 we added code to check for active children, and it ends up we were actually wrong for checking this, since you aren't able to set child products as active or inactive. The third was because of a missing permission in the install scripts. I would like to think that we are being responsive, the software is going to have bugs. We are trying to get them fixed as soon as possible. If you want to hold off until SP3.1 then that is fine. We are going to release it as soon as we feel that we have enough hotfixes together in order to release it. I'm not sure what you mean about support being lost for early adopters, the SP3.1 release will only be a rollup of all of the hotfixes. |
Justin Etheredge
Senior Software Engineer
BVSoftware |
|
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC)
Posts: 1,786
|
There are only a few issues reported with SP3 and most of them can be traced to two things:
1) The SP2 to SP3 patch included the wrong SQL data script. We have a correct SQL script available.
2) The search page/code was rewritten for SP3 to address merchant requests for more options, paging, and better results. Anytime you introduce brand new code there are bound to be a few bugs.
What are we doing to resolve the issues?
1) We are releasing hot fixes as quickly as possible for those customers that need them.
2) We will be releasing a 5.3.1 update that rolls up all the hot fixes for these issues.
3) We are analyzing what went wrong in our testing process that would allow these errors into the code.
We did test SP3 in both full builds and patches. Most of our testing involved creating and placing orders. Our testing did indicate a problem with manufacturer searches but it was my call to release the software with that issue since at the time I considered it to be minor and for some merchants SP3 would fix more urgent issues. In retrospect the manufacturer search bug we saw turned out to be a signal of a more significant search stored procedure problem.
|
|
|
|
|
|
Rank: Member
Joined: 4/30/2007(UTC)
Posts: 383
|
Justin as long as your team keeps track of the changes that were made - I'm just worried that in a month when new updates come out the early 3 people aren't having a hassle as code was changed etc - similar to the tab being lost in admin.
Don't mistake our comments as critical. Things happen, your team is fixing them and not only restoring functionality but actively exploring and adopting better methods. We're all really impressed here all around. People just want to be heard, your team listened to the feedback and came up with quick solutions. If you always execute this efficiently by the time we get to BV6 you'll have the best cart in the market.
|
|
|
|
|
|
Rank: Member
Joined: 2/21/2007(UTC)
Posts: 1,113
|
I do'nt think you can expect a "bug-free" release at any point -- unless you have everyone with every imaginable configuration doing beta testing, there are bound to be instances that just can't be seen until it's released. After all, everyone here said "don't install this in a production environment while it's still in beta" -- well, how many configurations out there are NOT in production?
Four -- now five -- minor fixes in the first week is nothing compared to what I was seeing on another platform after 2 years -- at least there ARE hotfixes! |
|
|
|
|
|
|
Rank: Member
Joined: 6/26/2006(UTC)
Posts: 351
|
I myself have complete confidence in the BVC5 team and think they're doing an excellent job coming out with the hotfixes fast. I've never been happier with another shopping cart! |
|
|
|
|
|
|
Rank: Member
Joined: 4/30/2007(UTC)
Posts: 383
|
I'll come right out and say it, I've never been happier with BV. I don't care if there are problems, they'll always be problems. This is the best response I've seen and I really hope Marcus and Co keep it up for all issues. That's all anybody can ask. The more features, the more possible errors.
|
|
|
|
|
|
Rank: Member
Joined: 12/23/2003(UTC)
Posts: 909
|
Originally Posted by: "Joe"
(at least there ARE hotfixes!)
AMEN! |
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.