In order to safely complete this installation on a live website you need to be able to backup your site files and database, and have a plan and permission to restore them should you encounter a problem during the installation process.
Different hosting providers and environments will have different methods of backing up and restoring databases. Please work with your hosting company to discuss the backup and restore tools that are available to you.
This installation process requires a level of technical expertise. Specifically, you will need to edit SQL.
Please read through the entire installation guide and make sure you understand the installation process before you begin an installation on your live site. If there are any steps of this installation process that are unclear, please submit a ticket to http://support.aspdotnetstorefront.com to request assistance.
Before you begin please ensure that:
You have file access to the root of your website (FTP or RDC are the most common).
You have SuperAdmin Access to your AspDotNetStorefront site.
You are running AspDotNetStorefront version 10.0.2.
Backup your database.
Backup your site files.
Copy the Web/Skins/Skin_1 folder into the /Skins folder on your live site.
Open the /Schema/Skinning.sql file in a text editor, edit as needed, then copy the contents into your admin console under Configuration > Run SQL. Click Submit to execute the script.
Click Refresh Store.
In Step 4 of the Installation procedure, you may want to edit the Skinning script before executing. Below is a breakdown of each section of the script with further explanation. The actual contents of the skinning script included in your installation package may vary. The below example uses Dean (Skin 1).
--Set the Skin ID here
SET@SkinID = 1
This section defines the Skin ID variable, which can optionally be used further down in the script. By default, this isn't used in most scripts, so this can typically be left as-is.
If, for example, your current live site skin is in the folder Skin_7, and you install the new skin into the Skin_1 folder, you might want to set all of your stores and customers to use the new skin. You could use the SkinID variable to add the following script just below this section:
UPDATEStore SETSkinID = @SkinID
UPDATECustomer SETSkinID = @SkinID
Dev / Staging Environment
--Images will work in Dev Environment as long as references DO NOT include a leading '/' character. If you're running this script in a dev environment, set @Environment = ''.
--Images will work in Staging Environment as long as references DO include a leading '/' character. If you're running this script in a staging environment, set @Environment = '/'.
This section defines whether you're running the script in a development or staging environment. If you plan to run this in a local/development environment first, to test out and modify the skin before applying to your live site, you'll want to leave this as-is. If you're running this on your staging or live site, set the @Environment variable to SET@Environment = '/'
Adjusting this setting to '/' will allow the images included in topics to appear correctly in the admin console. Images, when referenced correctly in topics, will appear on the front-end of the site regardless of this setting.
This section defines the product & entity xmlpackages (page layouts) used for all products & entities on the store. Adjust these to include the filenames of the XmlPackages you'd like to set globally throughout the store. Or delete these lines to keep your XmlPackage settings as they are. You can find the available filenames in the files on your live site under XmlPackages, and Skins/Skin_1/XmlPackages. If the same filename exists in both locations, the Skins/Skin_1/XmlPackages file will be used.
This section adjusts your store Settings (referred to as "AppConfigs" in the database). More information on each of these settings can be found in your live site admin console under Configuration > Settings.
INSERTINTOAppConfig (SuperOnly,Name,ValueType,GroupName,[Description],ConfigValue) VALUES(0,'promo-window-enabled', 'boolean', 'DISPLAY','Set this to true to show the promo popup window, set this to false to turn it off completely', 'false')
INSERTINTOAppConfig (SuperOnly,Name,ValueType,GroupName,[Description],ConfigValue) VALUES(0,'promo-window-cookie-expiration', 'integer', 'DISPLAY','Number of days until the promo window will show again for a visitor who has previously dismissed it.', '7')
INSERTINTOAppConfig (SuperOnly,Name,ValueType,GroupName,[Description],ConfigValue) VALUES(0,'promo-window-time-delay', 'integer', 'DISPLAY','Amount of time delay (in milliseconds) until the promo displays. For example: to delay for 5 seconds after page load, set this to 5000.', '5000')
INSERTINTOAppConfig (SuperOnly,Name,ValueType,GroupName,[Description],ConfigValue) VALUES(0,'Show.Variant.Image', 'boolean', 'DISPLAY','Show variant images on ''Responsive Variants in a List'' (product.variants-in-list.xml.config)', 'true')
INSERTINTOAppConfig (SuperOnly,Name,ValueType,GroupName,[Description],ConfigValue) VALUES(0,'ShowSkuOnProductPage', 'boolean', 'DISPLAY','Show SKU on product pages.', 'true')
Your responsive template includes some new settings which are used by some of the features specific to each of the Responsive Templates. This section of code will create the Settings on your store. After the script has been run, you can edit these new settings under Configuration > Settings in your store.
This section creates Prompts (referred to as "StringResources" in the database) that are used by some of the new Responsive Template features. Specifically, the product.tabbed-responsive.xml.config product page layout uses the product.tablabels... prompts to determine the tab names on the page just below the main product information. After the script has been run, you can edit these new prompts under Content > Manage Prompts in your store.
Near the bottom of the skinning script, there are several sections of code that create and insert HTML descriptions into topics. These topics are embedded throughout your responsive template and are used to display things like your store's logo, phone number, social media icons, top navigation, footer, etc.
For more information, or to get help with installing your new skin, please submit a ticket to our Help Desk .