HomeHome Product Discus... Product Discus...SmithCartSmithCartUpgrading to next versionUpgrading to next version
Previous
 
Next
New Post
9/8/2009 8:25 AM
 
Has anyone had problem upgrading their cart software? The last upgrade I installed seemed to rewrite the sql tables and broke many links within the DNN Module itself so that no purchases could be completed. Luckily I made a backup of the SQL tables before I ran the update.

Is there a tutorial for the correct way to upgrade the shopping cart module?

Thx!
 
New Post
9/9/2009 2:53 PM
 

To upgrade the cart please follow these steps. Please note we are modifying the sqldataprovider file to not overlay the tables starting in the next version released 9/18/09.

1. Extract the file named 01.00.00.SqlDataProvider from the cart zip file.
2. Open up the 01.00.00.SqlDataProvider file in notepad
3. Delete the following product create table statements from the file:

  • Smith_Manufacturer
  • Smith_Category
  • Smith_Products
  • Smith_ProductVariant


4. If you have live orders then you need to remove the create table stmts for these tables also:

  • Smith_Customer
  • Smith_StoreOrders
  • Smith_StoreOrderDetails
  • Smith_PayHist


5. Save the file and add back to the zip file.
6. Install the new module in dnn from the host menu.
7. Reset IIS to release the cache


At your service,
Dave Smith
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
6/10/2011 2:14 PM
 

Has there been any changes or documentation for the process of upgrading Smith Cart? For example, do you have a link on how to upgrade from 4.28 to 4.34.

 
New Post
6/10/2011 3:21 PM
 
To upgrade you can just install the new cart v4.34 over the existing cart module you have installed now. As always, before installing any new modules a live site make sure you have a full backup.

-Scott

Scott Kelly
Project Manager
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
6/10/2011 4:02 PM
 

Hi Scott - Thank you for your reply. I installed v4.32 over v4.28. My Categories and Products were not viewable from within the associated Store Admin links. I added a couple of new Categories and Products and then viewed the associated tables in SSMS. If you check out the attached png, you'll see the TabModuleId field with the discrepancies. I had similar discrepancies in the Products table. I changed the field values to match the new additions and all the records were once again available from within the Store Admin links.

I installed v4.32 using the Install Module link from Host >> Module Definitions page. Again, I already had v4.28 installed.

 
 Login to download attachment
New Post
6/10/2011 5:58 PM
 
Do you have multiple instances of the buynow module on your site? If so categories and products added from one buynow module will have a different tabmoduleid than categories and products from the second buynow module. The reason that tabmoduleid is saved with the cat and product is so you can run multiple stores in your portal with unique categories and products. Also if you delete a buynow module and add it again to the page dnn will assign a different tabmoduleid which could also be the reason you see a different tabmoduleid.

-Scott

Scott Kelly
Project Manager
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
6/13/2011 11:39 AM
 

Scott - Thank you for the info. My site consists of one portal. I do have a couple of instances of the Smith.BuyNow module - on the main page for a featured product and on my main shopping page. I can't recall if I entered the data from multiple modules. I'll keep that in mind about the different moduleIds.

After the module upgrade to the version 4.32, the main page took a while longer to load. Once loaded, I received a Page Load Exception: Can't get ModuleId for given module name 'Smith.BuyNow'. I did delete the module and reinstalled it. Inspection of the Categories and Products from the store admin page failed to show the records that I had entered. From this, I inspected the SQL tables. Again, I added a few more Category and Product records and viewed the tables as per my previous post.

With the above scenario, is it not recommended to have more than one Smith.BuyNow module installed?

Mike

 
New Post
6/13/2011 1:52 PM
 

The cart will work fine with multiple buynow modules added to your portal. After you upgrade make sure that you go into the buynow settings and re save your settings as there are several new settings that need to be initialized.

Thanks,


Scott Kelly
Project Manager
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
Previous
 
Next
HomeHome Product Discus... Product Discus...SmithCartSmithCartUpgrading to next versionUpgrading to next version