If you are a developper on AspDotNetStorefront ML Multi store, here is some news.
With the multiple bugs and missing features AspDotNetStorefront team came up with Service pack release mid november 2010
Google Checkout works accurately with real time shipping rates
The shipping estimator now works accurately with shoppers with no address
'Shipped On' Calendar on orderframe.aspx now works as documented
Order based weight adjustments can no longer be made to orders that have multiple shipping addresses.
The status of appconfig “SkipShippingOnCheckout” is now honored throughout the checkout.
ApplyShippingHandlingExtraFeeToFreeShipping now works as expected
There is new consistency around the display of the shipping line item throughout the estimator, shopping cart and checkout.
The number of "Is Ship Separately" items in a cart now correctly controls the cost of shipping
Shipping and Tax Estimator not only accurately represents values, but also calls valid country/state dropdown list
Multi-ship logic has been reviewed and made consistent. Shipments are now split on address rather than item. Shipping calculations are consistent and accurate.
In-store pickup method honors restrictions in ship-to state conditions.
Multi-store
All release notes apply to multi-store, but the following apply ONLY to multi-store implementations.
The menu item for "Store Maintenance" which was previously often hidden, is now at all times visible.
ETSMapper has been nullified for the correct saving of coupons, both active and deleted, across stores.
When a customer subscribes from createaccount.aspx (OkToEmail) page, the resulting email confirmation now honors the correct SubscribeURL across stores
Allowing shipping options and other shipping entities to be filtered across multiple stores now works correctly.
Page layouts which over-ran page borders have now been corrected, particularly on Store Maintenance.
Global configs are now fully honored.
Skins and topics (including hometopintro) are now accurately mapped to stores
The shipping by weight, shipping by weight & zone, and shipping by total & zone tables do not filter by store. If you have multiple stores these tables will show regardless of the store you are on or the store you select in the store dropdown. To have different prices returned to different stores you would need to setup different appropriately priced shipping method(s) mapped for each store.
Shipping-to-State mapping is now respected throughout the estimator, shopping cart and checkout
Different stores now map and maintain different email config settings
The use of "AllowCustomerFiltering GlobalConfig" now honors customers accurately across stores, and through the order, acknowledgement and receipt process
The feed to Google Product Search (googlebase feed), honors the storeid when generating the feed.
Menus are no longer bound to "cross-store". Different stores can maintain their own menu structure
To show different Entities on multiple store's sitemaps you simply set the global app config "AllowEntityFiltering" to true. To show different Products on multiple store's sitemaps you must set the global app config "AllowProductFiltering" to true. (N.B. Sitemaps are cached so be sure to reset your cache after making any store mapping changes.)
Feed functionality, including saving, updating, or creating feeds on a per-store basis has been updated to support the use of Multi-store.
Payment Gateways and Checkout
There are now multiple appconfigs for MailMe_ToAddress, such that multiple gateways need not share the same address.
Paypal Express Checkout now allows accelerated boarding which enables every merchant to collect funds through paypal without the need to first setup an account.
Payments now deliver a CardExtraCode in place of a CVV code through a gateway transactor in line with recent gateway requirements. The code is validated prior to submission.
The functionality of the out-of-box One Page Checkout is improved so that the page no longer clears when shipping options are selected. Shipping options are honored for both registered and anonymous shoppers.
The full address (including State) of an anonymous guest is persisted during a session, so that a 'checkout restart' no longer returns partial data
Databinding and postback issues, particularly in One Page Checkout, have now been handled to dramatically improve the stability of the checkout. This is true, also, for anonymous checkout
Sagepay (Protx) test URLs have been updated following the merge of these gateways.
SagePay (UK) Start Dates are now valid and accurate
VAT is now accurately rounded throughout the store and checkout
One Page Checkout now honors the freeshippingthreshold accurately
Product Management and Promotions
AvailableStopDate now functions as documented at the product level.
Referrers are now accurately tracked for a shopper who visits a store and logs in. The feature, rightly, does not track referrers from localhost or from the same domain.
The display page "product.variantsindropdown.xml.config" now respects variants when a shopper orders other than the default option.
Tax free items on a VAT enabled store now display consistent prices throughout the store.
The published/unpublished values of entities are now honored throughout the store.
Hiding categories will also hide products regardless of the "SiteMap.ShowProducts" setting. There is currently no filter for distributors
Functionality for the "Also Bought" content section takes into consideration products bought within the same purchase (and ONLY within the same purchase).
Coupons cannot, under any circumstances, produce a negative cart value
Taxes are consistently applied to the gross value of a shopping cart and do not entertain coupon based discounts. If setting an order level discount with a dollar amount discount, taxes will be calculated ahead of time and then the discount will be applied. This has the affect of creating a discount that covers all of the products in an order, but the customer will still have to pay taxes. Notice that you may no longer specify a percentage over 100%. Also, you can (rightly) no longer specify both a percentage and a flat amount. Percentage-based coupon discounts take precedence over flat rate discounts.
It is no longer possible for unpublished products to be rendered on FeaturedProducts.xml.config
There is no longer conflict between inventory tracking by variant and Inventory.LimitCartToQuantityOnHand on variant-based XML config packs
"Call to Order" now works for kit items - please note that a product can carry flags for both "call to order" (i.e. don't show the buy button) and also a flag for "ShowBuyButton". "CallToOrder" takes precedence.
Variants, when ordered in quantity, and regardless of the XML config pack, are consistent and accurate
And many other functionalities. However they still not came up with the Multi-payment or split payment method.
Retieved from http://manual.aspdotnetstorefront.com on November 22nd 2010