Rank: Member
Joined: 2/21/2007(UTC) Posts: 1,113
|
It appears we have lost the ability for the customer to custom sort on the Grid Layout in 3.1 -- I believe this was available under 3.0 -- it's available on other layouts, but not Grid |
|
|
|
|
Rank: Member
Joined: 4/30/2007(UTC) Posts: 383
|
How is 3.1 overall Joe? Did you upgrade yourself? We just don't want to keep dumping money into patches unless there's some assurance we're near the end of the major hotfix cycle. This not being available is a show stopper for us.
|
|
|
|
Rank: Member
Joined: 2/21/2007(UTC) Posts: 1,113
|
It fixed a couple of problems that 3.0 caused, and 3.0 fixed some major problems, but 3.1 also created a problem with large carts and site speed. Moving the Viewstate to the bottom of the page helps that, but still customers notice. |
|
|
|
|
Rank: Member
Joined: 4/30/2007(UTC) Posts: 383
|
That's probably why ours is not as bad, we left the viewstate at the bottom. It's fine for us up to 5 products and most of the time we won't have that many products in the cart anyway.
It's great the forums are becoming more active, it will yield a better product and greater success for all of us.
|
|
|
|
Rank: Member
Joined: 3/1/2006(UTC) Posts: 1,142
|
We have some fixes in the works for the large carts and site speed. Please be patient! We hope to have a fix out very soon. Also, we don't think that moving the viewstate to the bottom of the page is a huge part of the slowdown (at least from our tests) and if it works for you then by all means continue using it, but we certainly do not recommend it as it can have unexpected side effects. |
Justin Etheredge Senior Software Engineer BVSoftware |
|
|
|
Rank: Member
Joined: 2/21/2007(UTC) Posts: 1,113
|
Justin,
Are you saying to NOT check to have viewstate moved to the bottom of the page? I thought that was the preferred setting. |
|
|
|
|
Rank: Member
Joined: 3/1/2006(UTC) Posts: 1,142
|
Yes, that setting should only be checked if you are aware of the possible side effects. |
Justin Etheredge Senior Software Engineer BVSoftware |
|
|
|
Rank: Member
Joined: 4/30/2007(UTC) Posts: 383
|
Which are....please elaborate.
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC) Posts: 2,136
Was thanked: 1 time(s) in 1 post(s)
|
The #1 effect of moving ViewState to the bottom of the page is so the visible HTML is loaded first and the browser can start rendering it.
The #1 side effect is that if someone causes a postback before the entire page is loaded, the ViewState may not match what is posted and the server will throw an error. |
|
|
|
|
Rank: Member
Joined: 2/21/2007(UTC) Posts: 1,113
|
Yes, I was seeing that #1 side effect on the cart page -- however, large carts were timing out without it loaded at the bottom, so I had to go back to it for now. |
|
|
|
|
Rank: Member
Joined: 4/30/2007(UTC) Posts: 383
|
Thanks Andy!
I hate to mess with moving it back up top as we're happy with how everything is progressing but have seen the errors in the cart. I thought users may see unanticipated behavior vs the full crash though, did not realize we probably lost some sales because of it. Am I correct in thinking it would yield an error page to the end user?
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC) Posts: 2,136
Was thanked: 1 time(s) in 1 post(s)
|
@Joe: Customers would probably recommend ViewState at the bottom of the page since the page will appear to be rendered more quickly (the total rendering time stays the same, but the visible parts will appear sooner). Microsoft would recommend ViewState at the top--the way they designed it--to avoid the potential page validation errors.
@C: That's hard to say. If the page or website have an error handler, then probably not. |
|
|
|
|
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.