Starter Kit 2 bug - Adding settings to Payment Provider
Using Tea Commerce 2 with two installations - blank and the starter kit, when a setting is added to any payment provider (i.e. credit card, Paypal) an error is shown:
[NullReferenceException: Object reference not set to an instance of an object.]
TeaCommerce.Umbraco.Application.Views.PaymentMethods.EditPaymentMethod.lvSettings_ItemDataBound(Object sender, ListViewItemEventArgs e) +620
System.Web.UI.WebControls.ListView.OnItemDataBound(ListViewItemEventArgs e) +137
System.Web.UI.WebControls.ListView.CreateItemsWithoutGroups(ListViewPagedDataSource dataSource, Boolean dataBinding, InsertItemPosition insertPosition, ArrayList keyArray) +1234
System.Web.UI.WebControls.ListView.CreateChildControls(IEnumerable dataSource, Boolean dataBinding) +1156
System.Web.UI.WebControls.ListView.PerformDataBinding(IEnumerable data) +64
System.Web.UI.WebControls.DataBoundControl.OnDataSourceViewSelectCallback(IEnumerable data) +221
System.Web.UI.WebControls.DataBoundControl.PerformSelect() +312
System.Web.UI.WebControls.ListView.PerformSelect() +123
TeaCommerce.Umbraco.Application.Views.PaymentMethods.EditPaymentMethod.btnAddSetting_Click(Object sender, EventArgs e) +485
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +154
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3803
Is this forum the best place to submit bugs or is there an email address I should use? We're using V2 for a new shop and are coming across a few bugs along the way.
Starter Kit 2 bug - Adding settings to Payment Provider
Using Tea Commerce 2 with two installations - blank and the starter kit, when a setting is added to any payment provider (i.e. credit card, Paypal) an error is shown:
Is this forum the best place to submit bugs or is there an email address I should use? We're using V2 for a new shop and are coming across a few bugs along the way.
Hi Matt
Send us an email with bug reports - info at teacommerce.net
I have fixed this bug in a 2.0.1 we are working on at the moment. I can send it to you.
Kind regards
Anders
is working on a reply...