HomeHome Product Discus... Product Discus...SmithCartSmithCartConditionalGroupID  Exception thrown.ConditionalGroupID Exception thrown.
Previous
 
Next
New Post
9/23/2010 12:32 PM
 
I updated to 3.08 and copied the hotfixes for both the details and the paypal issues over. I will revert back to the old details DLL to see if this goes away.
I assumed that the hotfixes are just copied over the old DLLs in the bin directory.

Please let me know if there is a reason this exception is being thrown due to "user error".

AssemblyVersion: 5.5.0
PortalID: 0
PortalName: Anywear Clothing
UserID: 1
UserName: host
ActiveTabID: 40
ActiveTabName: Home
RawURL: /Home/tabid/40/ctl/ProductDetails/mid/380/ProductID/11/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://anywearclothing.com/Default.aspx?tabid=40&error=Object+reference+not+set+to+an+instance+of+an+object.
UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 0f0d7889-cc2d-4125-98e8-7c366c54c474
InnerException: Column 'ConditionalGroupID' does not belong to table Table.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.DataRow.GetDataColumn
StackTrace:
Message: System.ArgumentException: Column 'ConditionalGroupID' does not belong to table Table. at System.Data.DataRow.GetDataColumn(String columnName) at System.Data.DataRow.get_Item(String columnName) at Smith.DNN.Modules.BuyNow.ProductDetails.AddProductVariants(ProductsInfo pinfo) at Smith.DNN.Modules.BuyNow.ProductDetails.Page_Init(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.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Modules.ModuleHost.InjectModuleContent(Control content) at DotNetNuke.UI.Modules.ModuleHost.LoadUpdatePanel() at DotNetNuke.UI.Modules.ModuleHost.CreateChildControls() at System.Web.UI.Control.EnsureChildControls() at DotNetNuke.UI.Modules.ModuleHost.get_ModuleControl() at DotNetNuke.UI.Containers.Container.get_ModuleControl() at DotNetNuke.UI.Containers.Container.ProcessModule() at DotNetNuke.UI.Skins.Pane.InjectModule(ModuleInfo objModule)
 
New Post
9/23/2010 2:17 PM
 

Not sure what version of the cart you upgraded from but there have been new variant fields added recently in variant and variantGroup table in the cart database. If you go into the product variant setup screen in the cart and make sure you have groups defined for your variants and then re save your variants it should work for you.

-Scott


Scott Kelly
Project Manager
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
9/23/2010 3:57 PM
 
I upgraded from 3.7 once I saw you had hotfixes for 3.8.

I assumed the upgrade would add the fields to the database. Your reply implies it may not. Does the upgrade modify the database schema?

Specifically, I am adding the very first ProductVariant after running a query to add the ProductVariantGroup records automatically.

The first query is

INSERT INTO Smith_ProductVariantGroup
SELECT ProductID, 'Color' AS Expr1, NULL AS Expr2, 0 AS Expr3, 0 AS Expr4
FROM Smith_Products

Then another one for 'Size'.

Then I use the product variant setup screen to add the very first variant. After that, the error occurs when I click on options under the product. Also, in the product maintenance, if I try to edit that variant, the edit screen flashes up and then reverts back to the product maintenance screen.

Here are the fields defined in my database currently:
ProductVariantGroup:
VariantGroupID int
ProductID int
VariantGroup varchar
VariantHelpURL varchar
PortalId int
Hide bit

ProductVariant:
VariantID int
ProductID int
VariantGroup varchar
VariantName varchar
VariantImage nvarchar
PriceAdjustment money
WeightAdjustment float
SortOrder int
PortalId int
VariantRequired bit
VariantDisplayType varchar
VariantGroupID int
Sku varchar
QtyOnHand int
ConditionalGroupID int

Let me know whether this is the correct schema for version 3.8. Or point me to the script in the upgrade files.

Thank you.

Guy



 
New Post
9/23/2010 4:35 PM
 

When you install the module the new fields are created in the variant and variant group table its just the data from your exisitng variants that needs to be populated in the new fields. For your existing products that you have already created variants for if you go into the product variant setup screen in the cart and make sure you have groups defined for your variants and then re save your variants it should work for you. Or if you create a new product and variant and test it should work for you.

-Scott


Scott Kelly
Project Manager
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
9/23/2010 4:57 PM
 
I am creating these records from scratch! The exception occurs even after I create a new product, new product variant groups for that product and then a new product variant.

Perhaps you could verify if the database I have is correct for 3.8? I see the ConditionalGroupID in the database I have installed, so it is confusing why the exception occurs.

To reiterate, I am completely removing all product, variant group and variant records before adding new ones.
 
New Post
9/23/2010 5:20 PM
Accepted Answer 

I recommend doing a clean install of cart v3.08


Clean Install Instructions
--------------------------------
Delete the old module and start with a clean install of the module. Please do the following:

  1. From the dnn->host menu uninstall all 6 modules; Smith.BuyNow, Smith.AffliateTracking, Smit.CategoryMenu, Smith.MiniCart, smith.featuredproducts and Smith.MyAccount. Make sure you check the delete files box when you uninstall
  2. Confirm that all stored procs and tables with a prefix of smith in your database are deleted
  3. Confirm that all files in /desktopmodules/smith.buynow are deleted and the folder is removed
  4. Install the latest module v3.08
  5. Configure the cart settings
  6. Add one category, manufacturer and product and test

Scott Kelly
Project Manager
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
Previous
 
Next
HomeHome Product Discus... Product Discus...SmithCartSmithCartConditionalGroupID  Exception thrown.ConditionalGroupID Exception thrown.