Upgrade to AbleCommerce Gold R9

1)  Download Upgrade to temporary location

This upgrade is available to active subscription holders.  To obtain the file, login to the ablecommerce.com website and go to the customer account area.  From the Downloads tab, in the top section, you can see all files that are available to you by subscription.  Be sure to download the files and keep an original for backup.

1. Determine the type of version you are using, WAP or WSP, and download the applicable file.

2. Extract the contents.  Only changed files are included in the upgrade set.

3. Compare the new upgrade files with your existing ones, and merge any custom changes.

2)  Confirm License

Do not install the upgrade unless your license subscription is valid through the "release date" of the build you are installing, or you have a license key for the latest version.

There are two ways to see if you have a valid subscription for this upgrade:

Login to your AbleCommerce Merchant Menu and go to the Configure > Security > Licensing page.
The "License Details" section will indicate whether a subscription is included with your license, and the subscription's expiration date will be shown.

- OR -

Open the "commercebuilder.lic" file located in the \app_data\ folder with a txt program such as notepad. 

e.g. <subscription>09-30-14</subscription>

If your license purchase included a subscription, a line similar to the one above will be shown in your key file.  
Make sure the date is on, or after, September 30th, 2014, which is the release date for AbleCommerce Gold R9. 

NOTE:  A store in DEMO MODE is not valid for the upgrade.  Make sure you have a license key installed before continuing.  The key type can be Development or Live, but not DEMO.  

3)  Backup your Existing Production Files

Always make a backup copy of the entire AbleCommerce folder and the database before beginning any upgrade..

4)  Installation of New Files to Production Server

In this upgrade release, there is one configuration files that will be adjusted.  See post-upgrade instructions for the exact changes.

\web.config

Before copying the files from the upgrade folder, check to make sure that you have not made changes that will be overwritten.  It is best to use a file comparison utility (e.g. WinMerge) to view any differences before replacing your customized configuration files.

For WSP versions:

1. Stop the IIS web service, or application pool, to release a lock on the DLL files in the \bin\ folder.
   
   FAQ: How do I stop a website to upgrade?

2. Copy all files, from step 1c) above, to the corresponding folders on the production server.

3. Restart the IIS web service application.

For WAP versions:

1. Recompile the application.  For Gold release R8 and higher, the SLN file is upgraded to support Visual Studio 2012/2013.

2. Republish to the target server.

5)  Automatic Database Upgrade

When you login to the merchant administration for the first time, the database will be upgraded automatically.  For a complete list of database changes, see below.

6)  Automatic Re-index

If you are using the Lucene search provider, we will re-index the database automatically after the upgrade. Re-indexing could get interrupted if the server is restarted.  If this happens, simply access the Website > Indexes page to manually re-index the database.

7) Post-Upgrade Instructions

Upgrade your Theme -

To accommodate the new shop by and stored payments feature within the customer account pages, style sheet changes for the theme will be needed for this release.  The files are located in the \App_Themes\ folder, and then in the sub folder you are using for your own theme.  You can use a tool like WinMerge to easily find the changes between versions R8 and R9 and get them merged.

1. Open the style.skin file.

2. At the very bottom, add the following two lines:
   
   <asp:ImageButton SkinId="ShopByAdd" runat="server" ImageUrl="Images/Icons/shopby_addImage.gif" />
   
   <asp:ImageButton SkinId="ShopByRemove" runat="server" ImageUrl="Images/Icons/shopby_remove.gif" />

3. Save when finished.

4. Next, open the style.css file from the R9 release.

5. Scroll down until you find the section /* Payment Types styling */

6. Copy this entire section (below the wishlist style) to your existing stylesheet (style.css).  It will be used for the new customer payment profile page.
   
   /* Payment Types styling */

#account_payment_types div.column_1 {width:630px;padding:0 0px 0 0px;}

#account_payment_types div.column_2 {width:283px;padding:0 0px 0 0px;}

#account_payment_types div.paymentList {padding:5px;}

#account_payment_types div.noPayments {padding:15px;background-color:#e4e4e4;font-size:14px;text-align:center;color:#444;}

#account_payment_types div.mainContainer {width:auto;}

#account_payment_types div.innerLeft {width:10px;display:inline-block;float:left;padding:23px 15px 23px 15px;}

#account_payment_types div.innerRight{width:270px;display:inline-block;float:left;}

#account_payment_types div.innerRight div.paymentItem { width:auto;-webkit-border-radius: 15px;-moz-border-radius: 15px;border-radius: 15px;border:solid 1px #3e9db3;padding:5px 12px 5px 12px;height:50px;margin-bottom:20px;}

#account_payment_types div.innerRight .deleteLink input{color: #3e9db3 !important;text-transform: lowercase; text-decoration:underline;font-weight: bold; background:none; border:none;}

#account_payment_types div.innerRight .deleteLink input:hover {background:none; color: #2a6b7a !important; border:none;}

#account_payment_types div.innerRight div.paymentItem div {float:left;padding:0px;}

#account_payment_types div.innerRight div.paymentItem div.reference {font-weight:bold;}

#account_payment_types div.innerRight div.paymentItem .deafultPayment {font-style:italic;color:#f00;font-weight:bold;margin: 0 0 0 3px;}

#account_payment_types div.innerRight div.paymentItem .expiration {padding-top:7px; clear:left;}

#account_payment_types div.inputForm {width:auto; /*margin:0 0 0 110px; padding:10px;*/}

#account_payment_types div.inputForm .rowHeader {display:inline-block;padding:8px 5px 8px 5px;float:left;font-weight:bold; color: #444444; width:120px; text-align:right;}

#account_payment_types div.inputForm .inputFied {display:inline-block;float:left; padding:7px 0 7px 0;}

#account_payment_types div.inputForm .securityCodeInput {width:152px;}

#account_payment_types div.inputForm .btn {margin-left:125px;}

#account_payment_types div.inputForm div.error {width:400px;}

#account_payment_types div.inputForm .errorCondition {color: #ff0000;font-weight: bold;padding: 0; }

#account_payment_types .instructionText {display:inline-block;}

Upgrade your web.config

Performance improvements will require an adjustment to your web.config file.  If you have not made custom changes to this file, then you can safely copy and paste over-riding your original version.  If you have made customizations, then use these instructions to make the code changes.  You can also use a tool like WinMerge to easily find the changes between versions R8 and R9 and get them merged.

1. Find and open the web.config file in the root folder of the website.

2. Find this block of code:
   
   <configSections>

    <section name="nhs-configuration" type="NHibernate.Search.Cfg.ConfigurationSectionHandler, NHibernate.Search" requirePermission="false"/>

    <section name="paypal" type="com.paypal.sdk.core.ConfigSectionHandler, paypal_base"/>

  </configSections>

3. Change it as follows:
   
    <configSections>

    <section name="nhs-configuration" type="NHibernate.Search.Cfg.ConfigurationSectionHandler, NHibernate.Search" requirePermission="false"/>

    <section name="paypal" type="com.paypal.sdk.core.ConfigSectionHandler, paypal_base"/>

    <section name="syscache" type="NHibernate.Caches.SysCache.SysCacheSectionHandler, NHibernate.Caches.SysCache" requirePermission="false" />

  </configSections>

4. Find this line:
   
   </nhs-configuration>

5. Immediately after, add this code:
   
    <syscache>

    <cache region="LongTerm" expiration="3600" priority="5" />

    <cache region="ShortTerm" expiration="900" priority="3" />

  </syscache>

6. Save when finished.

Informational Only - Database Changes

The database changes will be automatic after upgrading.  It is NOT necessary to make changes manually.  This is provided for informational purposes only.

ac_InputFields Table

column added: UseShopBy BIT DEFAULT 0 NOT NULL

ac_OrderStatusTriggers Table

column added: UseShopBy BIT DEFAULT 0 NOT NULL

ac_OrderStatusTriggers Table

primary key column added: OrderStatusTriggerId INT IDENTITY NOT NULL

ac_Payments Table

column added: GatewayPaymentProfileId INT NULL

If you need to merge any customizations, we recommend that you use a file compare and merge utility such as WinMerge.  WinMerge is Open Source file compare and merge utility which runs on all modern Windows versions.  Latest WinMerge version and other WinMerge information is available at http://winmerge.org