Having upgraded to 2.99 and added a hotfix, I still get errors with the conditional variants not holding their values. Additionally, the store on the portal that doesn't use the conditional variants, but just regular variants generates the error:
A critical error has occurred.
There is no row at position 0.
Full error text:
AssemblyVersion: 5.2.3
PortalID: 0
PortalName: Space Management Products
UserID: 1
UserName: Spacehost
ActiveTabID: 65
ActiveTabName: Screenflex
RawURL: /Screenflex/tabid/65/ctl/ProductDetails/mid/399/ProductID/2/Qty/1/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.spacemanagementproducts.com/Screenflex.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6.5; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 1.0.3705; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; InfoPath.1; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 7346eefd-15ef-448b-9321-bab1396e2260
InnerException: There is no row at position 0.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.RBTree`1.GetNodeByIndex
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: There is no row at position 0. ---> System.IndexOutOfRangeException: There is no row at position 0. at System.Data.RBTree`1.GetNodeByIndex(Int32 userIndex) at System.Data.RBTree`1.get_Item(Int32 index) at System.Data.DataRowCollection.get_Item(Int32 index) at Smith.DNN.Modules.BuyNow.ProductDetails.GetPrice() at Smith.DNN.Modules.BuyNow.ProductDetails.Page_Load(Object sender, EventArgs e) at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: EDTWEB27
When I back out the hotfix, this bug goes away.