Revision history

1.4.3.0 BETA 2 -

• NEW: 2CheckOut payment gateway is now supported
• FIX: If the shipping fees, payment fees or vat group id was changes using the .NET API - the changes would save to DB but not be reloaded once the order was reloaded from DB
• FIX: SagePay now works with US states
• FIX: Tea Commerce would mix language files when uninstalling
• FIX: Authorize.Net and WorldPay provider where they would cut the order id if the Tea Commerce order prefix was a number

1.4.2.4 - 07 March 2012

• Fix the "shipping is free above" field to also take both comma's and dot's as decimal delimiter

1.4.2.3 - 05 March 2012

• FIX: Shipping fees, payment fees and VAT can now be entered with both dot and comma as decimal separator.
• FIX: If the master product where chosen on both product and variant, the wrong master product would be chosen in some cases.

1.4.2.2 - 27 February 2012

• NEW: Use cookie for storing the clients cart instead of the usual session approach.
  Can be set up in the "General settings" area of Tea Commerce.
• NEW: Order prefix is now optional and "-" isnt added automatically
• NEW: World Pay Payment provider
• NEW: Norwegian translations
• NEW: Added currency symbol and currency symbol placement for a currency
• NEW: Quickpay payment provider has been updated to v4
• NEW: Made the Tea Commerce SessionController class public. This makes it possible to tamper with the Tea Commerce session on the fly using the .NET API
• NEW: Most of the Order methods are now public
• NEW: The dataType setting now works with the invokeXslt JavaScript method
• FIX: Multi capture of payments at the order list only captured the first order
• FIX: WebshopEvents.PaymentStatusChanged wasn't invoked when an order was finalized
• FIX: WebshopEvents.OrderCreated would result in inifinite loop if you called order.Save()
• FIX: Optimized GeneratePaymentForm method of base/xslt library
• FIX: Quickpay provider needs an order id of min 4 characters - automatically inserts leading 0's
• FIX: Custom stock datatype could not be validated mandatory or by regex
• FIX: SagePay didn't accept the status of "REGISTERED" when doing 3DSecure payments
• FIX: PayPal provider and PayEx payment providers would fail when having multiple languages
• FIX: When changing the stock on a product in the content section, the cache would not be updated.
• FIX: GetProperty will now search up the tree to find the nearest chosen master product.

1.4.1.2 - 24 November 2011

• BREAKING: All dates in the xml are now formatted in the same sortable date/time format as Umbraco does. Furthermore the format is done with an Invariant culture. This means that you can now sort the orders by date. But you will also have to format the dates, if users can see them.
• BREAKING: countriesSupported removed from shipping and payment methods in XML
• BREAKING: PaymentCountries removed from payment methods in JSON
• BREAKING: ShippingCountries removed from shipping methods in JSON
• NEW: Wannafind payment provider added
• NEW: PayEx payment provider added
• NEW: Authorize.NET payment provider added
• NEW: order.MemberId is now available in the .NET API
• FIX: End-user was able to add a negative quantity for an order line
• FIX: Stock management wasn't working correctly when using master products
• FIX: The PayPal payment provider would send the order lines total prices to PayPal instead of the unit price.
• FIX: It wasn't possible to delete basic settings for the payment provider

1.4.1.1 - 21 September 2011

• NEW: Added GetPrices to the XSLT library
• NEW: Invoke xslt will now search in sub folders to the xslt folder and find the file. The file must have a unique name and must still be approved in the general settings.
• NEW: Overload method for the library methods GetProperty and GetPropertyXML. The new overload lets you apply an AND selector which will narrow down the options.
• FIX: The eventhandlers is now loaded when using the .NET API as well as when using the JavaScript API
• FIX: The country specific VAT is now working properly
• FIX: Price parser was buggy when dealing with number with large decimals.
• FIX: Shipping and payment methods did not load the isDeleted property from the database, thus making them impossible to delete.
• FIX: Payment providers had a problem loading default settings.
• RENAMED: .NET API - PriceHelper.FormatPrice renamed to PriceHelper.ParsePrice
• REMOVED: .NET API - PriceHelper.FormatPriceWithSpecificCulture has been removed
• REMOVED: .NET API - PriceHelper.FormatPriceNoSymbolWithSpecificCulture has been removed

1.4.1.0 - 17 July 2011

• BREAKING: GetOrCreateOrderLine on the .NET API order object have been removed and replaced with CreateOrderLine and CreateUniqueOrderLine which creates new orderlines AND adds them to the order.
• NEW: Danish and Swedish translations of the Tea Commerce section
• NEW: Razor API now have a RemoveOrder which removes the current order from the users session.
• NEW: GetPropertyXML library method. Works just like GetProperty only it returns XML for use in the xslt. Usefull when your property value is XML and not a simple string.
• NEW: GetMasterProduct library method
• NEW: GetMasterProuctRelatedProducts library method
• NEW: .NET API method EmailTemplate now has a public constructor
• FIX: The GetProperty library method now works with richtext editor fields
• FIX: A few of the english translations where faulty
• FIX: TeaCommerce.getCurrentCountry in the JavaScript API failed when settings parameter was null
• FIX: The razor method GetOrder now returns a new order if none was present
• FIX: jSon Serializing for Countries, Currencies, OrderStatusses, ShippingMethods, PaymentMethods and Transaction data would make a stack overflow
• FIX: Some events would throw an "Collection was modified" error when they where fired again from inside themselves.
• FIX: The Quickpay API calls did not work due to a wrong checksum
• FIX: Payment methods "Allowed Payment provider API calls" where not updated corectly in the UI

1.4.0.0 - 29 June 2011

We have once and for all, following requests from you wonderful people in the Umbraco community, refactored the JavaScript API. What we've done now is to create a settings object that can be extended indefinitely. Please read this blog post by Rune Grønkjær on how to upgrade your JavaScripts to the new settings style.

• BREAKING CHANGE: Mayor refactoring done on the Tea Commerce JavaScript library. Most methods now takes a settings object  in place of the async, successfn etc.
• NEW: No-JavaScript fallback support. You can implement this on your site. No-JavaScript fallback have allready been implemented in the Tea Commerce Starter Kit, where you can see how it works.
• NEW: Order list now supports applying an action to multiple orders for the webshop owner. Delete, change order status and capture multiple orders at once.
• NEW: Changed the commentary setup in teaCommerce_unpacked.js to provide Visual Studio intellicense
• FIX: CreateEmailTemplate had incorrect file extension

1.3.1.0 - 15 June 2011

• NEW: Added support for the Deli licensing

1.3.0.0 - 10 June 2011

Do you need an Umbraco ecommerce solution that can sell goods around the world in different languages? This release of Tea Commerce gives you the necessary tools to create exactly this. To get easily started to develop an ecommerce solution with multiple languages in Tea Commerce, download the Tea Commerce Multilanguage Starter Kit.

We have also made several minor improvements to the order management in Tea Commerce, so the daily work for shop owners is as easy as possible.

Rune has written a blog post that explains how to upgrade your current Tea Commerce solution compared to the below breaking changes. You can also looking into the updated documentation for the JavaScript API.

• BREAKING CHANGE: Added umbracoLanguageId to multiple JavaScript methods
  • TeaCommerce.invokeXSLT
  • TeaCommerce.updateOrderLineProperty
  • TeaCommerce.updateUniqueOrderLineProperty
  • TeaCommerce.updateOrderLineProperties
  • TeaCommerce.updateUniqueOrderLineProperties
• BREAKING CHANGE: Removed nodeId parameter from the following JavaScript methods.
  
  • TeaCommerce.updateUniqueOrderLineProperty
  • TeaCommerce.updateUniqueOrderLineProperties
• BREAKING CHANGE: The PaymentProvider API has been changed
• NEW: Support for multiple languages
• NEW: Multiple email templates - Send different order related emails from the order view
• NEW: Print order from order view
• NEW: Changes to the order search for shop owners
• NEW: All Payment methods now have an unlimited number of payment provider settings
            Thereby supporting all kinds of parameters for payment providers
• NEW: Trial mode now supports 20 orders when testing Tea Commerce
            Should make it much easier to test your site
• NEW: EmailTemplate class added to the .NET API.
            Use it to easily send e-mails from the webshop to the customer.
• NEW: Added new events in the .NET API
  • BeforeMailSend
  • AfterMailSend
  • MailError
• NEW: umbracoLanguageId property added to order object
            Will be set when an orderline is added via the javascript API
• NEW: Added new functions to the javascript API
  • TeaCommerce.setOrderUmbracoLanguage
      Will set the new umbracoLanguageId property on the order object
• NEW: Now works on http://localhost/
• NEW: Default continue URL and default cancel URL has been moved from "General Settings" to the individual payment methods. For PayPal, Ogone, SagePay, DIBS, QuickPay and ePay these settings is automatically added when updating
• FIX: Payment and shipping methods are marked deleted instead of permanently deleted
• FIX: Changed Ogone payment provider to send form data as UTF-8
• FIX: goToPayment would fail if order contained no order lines

1.2.1.1 - 20 April 2011

• NEW: Opened up a large portion of the Tea Commerce .NET API. Including the XSLTHelper and several dataclasses.

1.2.1.0 - 07 April 2011

• NEW: Added sorting feature for contries, currencies, order statuses, payment methods, shipping methods and VAT groups
• NEW: Moved some menu items in the Tea Commerce section
• NEW: Developer node in the Tea Commerce section. Find usefull information and license check here
• NEW: Changed some contextual help texts to help even more
• FIX: Decimal separator would generate problems in some server/language setups
• FIX: CC and BCC emails would fail to let you write more than one email

1.2.0.0 - 14 March 2011

This update is all about the new Razor library added to Tea Commerce. With the Razor library you get all the same methods that is available in the XSLT library. The .NET API also been extended with the ability to manipulate product prices and VAT groups. This gives you the opportunity to make discounts, prices based on member groups, etc.

We have also added support for two new payment gateways - Sage pay and Ogone. With these two new payment providers, Tea Commerce now supports six different payment gateways.

• BREAKING CHANGE: The PaymentProvider API has been changed.
• BREAKING CHANGE: The .NET event model has been overhauled. Some events have been removed and some have been given new names
  
• NEW: Razor library
• NEW: Ability to manipulate prices, fees and VAT groups has been added to the .NET API
• NEW: Sage pay payment provider
• NEW: Ogone payment provider
• NEW: OrderLineChanged event added to the .NET event model
• NEW: The .NET events is now invoked by all changes to the order. Before, events where only invoked when Tea Commerce manipulated data.
• NEW: Check your licensed domains in the Tea Commerce section
• NEW: .local domains is now accepted as legal domains when testing
• NEW: Pay Pal payment provider now shows orderline, payment and shippingfee information within Pay Pal.
• NEW: Better descriptions for payment provider settings in Tea Commerce admin
• FIX: PayPal payment provider couldn't handle auto capture
• FIX: Minor bug in Tea Commerce default payment provider
• FIX: Bugs in transaction snapshot information
• FIX: When a customers current cart was deleted from the admin, an error occurred
• FIX: Installation overwrites the default xslt files and the orders.xml. Now it leaves the old ones.

1.1.1.0 - 23 February 2011

• BREAKING CHANGE: The PaymentProvider API has been changed.
• NEW: New JavaScript method added - removeOrder
• FIX: Bugs in the payment providers

1.1.0.5 - 16 February 2011

• Minor bugfixes

1.1.0.4 - 16 February 2011

• Minor bugfixes

1.1.0.3 - 24 January 2011

• BREAKING CHANGE: The PaymentProvider API has been changed. Method return types have have been changed
• BREAKING CHANGE: TransactionPaymentState removed from Order object
• NEW: Added ePay as an available payment provider
• NEW: Added DIBS as an available payment provider
• NEW: TransactionPaymentCardType property added to Order
• NEW: TransactionPaymentCardNumber property added to Order
• Payment Provider API extended with new funktionality

1.1.0.2 - 13 January 2011

With the release of Umbraco 4.6, we have updated Tea Commerce, so it supports the latest version of Umbraco. This gives you the possibility to use all the new cool features of Umbraco that makes it even easier to build a e-commerce solution using Tea Commerce

• NEW: Supports Umbraco 4.6.x
• FIX: Unique order lines couldn't save
• FIX: RemoveAllUniqueOrderLines in /Base didn't work
• FIX: RefreshOrdersXmlAction caused an error in Umbraco 4.6.1

1.1.0.1 - 03 January 2011

• NEW: Added order status of the order to the XML and Json output
• NEW: Removed available shipping- and payment methods from the order XML and Json output

1.1.0.0 - 22 December 2010

Tea Commerce 1.1 is all about the .NET developers and extending the order flow. The entire data layer has been remodeled, so it is now possible to access the customers current order during the order flow and manipulate it. This provides endless possibilities for a. NET developer, and in a relatively short time, it is now possible to implement a voucher system, discounts, etc..

Tea Commerce 1.1 now makes it possible to create membership-based solutions because tea Commerce now keeps track of logged in customers during the checkout process and thereby enables order history.

• BREAKING CHANGE: Changed the OrderProperty and OrderLineProperty "DataNtext" property to "Value". This affects both the .NET API as well as the javascript API.
• NEW: Rewritten the entire datalayer
• NEW: Ability to create unique orderlines - 1 x 5 meters of wood, and 2 x 3 meters of wood
• NEW: Added new events in the .NET API
  • BeforePaymentStatusChanged
  • AfterPaymentStatusChanged
  • BeforeOrderLineRemoved
  • AfterOrderLineRemoved
  • OrderDeleted
• NEW: Opened part of the core .NET API to external developers
• NEW: New xslt library methods
  • GetFinalizedOrdersXmlForMember(int memberId)
  • GetFinalizedOrdersXml()
• NEW: Right click functionality on "Orders" in the Tea Commerce backend. This refreshes the orders xml file cache.
• NEW: Event model
  • CurrentOrderChanged renamed to CurrentOrderCloned
  • BeforeAddOrderLine renamed to BeforeOrderLineAdded
  • OrderLineAdded renamed to AfterOrderLineAdded
  • BeforeOrderMailSend renamed to BeforeOrderConfirmationMailSend
  • AfterOrderMailSend renamed to AfterOrderConfirmationMailSend
  • OrderMailError renamed to OrderConfirmationMailError
• FIX: Fixed missing checks for dirty properties on data objects, causing data not to be saved in rare cases.
• FIX: XSLT extension FormatPriceNoSymbolWithSpecificCulture didn't format from the correct culture.

1.0.2.0 - 02 December 2010

• NEW: Each country can have a default payment method
• NEW: Dynamic order line properties
  • Can now be added with addOrderLine and overwriteQuantity JavaScript methods
  • Can now be added with the two new JavaScript methods updateOrderLineProperty and updateOrderLineProperties
  • You cannot overwrite the secure properties that has been autocreated from the product
• NEW: Added two new event hooks - BeforeOrderLinePropertiesUpdated, AfterOrderPropertiesUpdated
• NEW: Admins can change what API methods that should be possible for a payment method
• NEW: APaymentProvider now has properties to specify what API call is supported by the payment provider
• NEW: Payment providers now handle error codes
• FIX: Problems changing some information on finalized orders
• FIX: Users does not understand how to write VAT. Must be in percent
• FIX: Order payment status was reset when getting error code from QuickPay

1.0.1.0 - 26 November 2010

• NEW: Capturing payments directly from the backend
• NEW: Refund payments directly from the backend
• NEW: Cancel payments directly from the backend
• NEW: Finalize an order directly from the backend
• NEW: New payment status enum
• NEW: Added paymentstatus to order - Captured, Cancelled etc.
• NEW: Added a beta version of the .NET event model to hook into the order flow
• NEW: Changed the License check functionality
• NEW: Changed the removeAllOrderLines functionality. It now deletes the order completely and starts a new clone of the order, with a new order id. This way you will be able to reset the order completely and thereby also reset the cache
• FIX: You needed to specify a vatgroup on a product even when you didn't needed it
• FIX: Possible hack of the payment system