All of our WHMCS Themes Have Been Updated for WHMCS 8.10
All of our WHMCS Themes have been updated for full compatibility with the latest versions of WHMCS, 8.10.0-8.10.1.

Contents


  1. Theme requirements
  2. Installation instructions
  3. Upgrade instructions
  4. Configurable theme options
  5. Configurable orderform template options
  6. Customising Flare theme
  7. Trouble-shooting and support
  8. Changelog and release history

Theme requirements


Before purchasing or installing Flare theme for WHMCS, please ensure that you have purchased and installed the latest version of the WHMCS software.

The current version of Flare theme is designed to work with WHMCS version 8.10.1.

Installation instructions


Please follow the instructions below to download and install the latest version of Flare theme.

Step 1: download Flare theme

To download the latest version of Flare Theme, please follow the steps below:

  1. Log in to My Account
  2. Select Account Overview from the My Account menu
  3. Scroll down the Account Overview page to the My Products section and select Flare WHMCS Theme from the list of available products
  4. Scroll down the Flare WHMCS Theme page to the Product Downloads section
  5. Choose the version of the theme you would like to download (we would always recommend using the latest available version of Flare Theme) and click the download button
  6. Extract the contents of the downloaded zip file on your computer

Step 2: install Flare theme

In order to install Flare Theme on your server, you will need to use an FTP client (such as FileZilla) to connect to your server.

After downloading and extracting the Flare Theme product zip file, you will find the following directories:

  • flare – contains the main Flare WHMCS theme files
  • orderforms – contains the three matching Flare order form / shopping cart templates:
    • flare_compare – contains the matching Flare order form template – comparison product selection version
    • flare_slider – contains the matching Flare order form template – slider product selection version
    • flare_standard – contains the matching Flare order form template – standard product selection version
  • third party addons – contains compatible themes / templates for various third party addons, including:
Step 2.1: install the main theme files

Using your FTP client, upload the flare directory to the following location on your server:

/your-whmcs-install-location/templates/

&nsbp;

Step 2.2: install the order form theme/template files

Using your FTP client, upload the flare_compare, flare_standard and flare_slider directories from the orderforms directory to the following location on your server:

/your-whmcs-install-location/templates/orderforms/

Please note: flare_compare and flare_slider are child templates of flare_standard. flare_standard must be uploaded to your server if you intend to use either flare_compare or flare_slider.
Step 2.3: install any relevant third party theme/template files

This step is only necessary if you are using any of the following third party addons/modules:

Official WHMCS Project Management Addon

To install the matching theme/template for the Official WHMCS Project Management Addon using your FTP client, upload the flare directory from the third party addons / project management addon directory to the following location on your server:

/your-whmcs-install-location/modules/addons/project_management/templates/

Modules Garden DNS Manager

To add the DNS Manager link the primary navigation, you need to upload the included hook file (hook_primary_nav_add_manage_dns.php) which can be found in the Flare theme download zip file (in the third party addons folder) to the following location:

/your-whmcs-install-location/includes/hooks/

Modules Garden Domain Orders Extended

Flare theme folder. Find the template files in the Domain Orders Extended download zip in the following folder:

…your php version…/templates/six/

Upload them to:

/your-whmcs-install-location/templates/flare/

Note regarding addons from Modules Garden: Our themes support the majority of modules from Modules Garden out of the box, with no requirement for additional theme/template files. Supported addons include cPanel Extended, Direct Admin Extended, Plesk Extended and many more. Styles for these modules are specified within the main Flare theme stylesheets to ensure that they match with the style/layout of Flare theme.

Step 3: activate Flare theme

Please follow the instructions below to activate and begin using Flare theme.

Step 3.1: activate the main client area theme

Log in to the WHMCS admin area and follow the instructions below to activate Flare theme:

  1. Navigate to Setup > General Settings
  2. On the General tab, scroll down to the Template option
  3. Select Flare from the list of available themes
  4. Click the Save Changes button at the bottom of the page
Step 3.2: activate the matching order form template(s)

Follow the steps below to activate the matching Flare order form template:

  1. Navigate to Setup > General Settings
  2. Navigate to the Ordering tab, scroll down to the Default Order Form Template option
  3. Select Flare Standard from the list of available order form templates
  4. Click the Save Changes button at the bottom of the page
It is recommended to use Flare Standard as the default order form / shopping cart template rather than Flare Compare or Flare Slider. Flare Compare or Flare Slider can be applied to particular product groups following the instructions below.

Follow the additional optional steps below if you want to apply a specific order form template, such as Flare Compare or Flare Slider, to a particular product group:

  1. Navigate to Setup > Products/Services > Products/Services
  2. Click the edit button edit button next to the product group you wish to apply a custom template to
  3. Scroll down to the Order Form Template option and select Use Specific Template
  4. Select the order form template you wish to use from the list of available order form templates
  5. Click the Save Changes button at the bottom of the page

Upgrade instructions


The upgrade process varies depending on whether or not you have made any changes or customisations to any of the theme files (including theme-options.tpl, custom.css or any other theme files).

Note: we always recommend backing up your existing website files (including theme files) before upgrading.

If you have not changed or customized any of the theme files, you can simply download the latest version of the theme files from our website and upload them to your web server, overwriting the previous version of the theme files.

For details of how to download and install the theme files, please follow steps 1 and 2 of the installation instructions section above.

Remember: you must select the overwrite option when prompted by your ftp client, to overwrite the existing theme files with the newer version.

If you have made changes or customizations to any of the theme files, the following upgrade process is recommended.

Step 1: download Flare theme

To download the latest version of Flare Theme, please follow the steps below:

  1. Log in to My Account
  2. Select Account Overview from the My Account menu
  3. Scroll down the Account Overview page to the My Products section and select Flare WHMCS Theme from the list of available products
  4. Scroll down the Flare WHMCS Theme page to the Product Downloads section
  5. Choose the version of the theme you would like to download (we would always recommend using the latest available version of Flare Theme) and click the download button
  6. Extract the contents of the downloaded zip file on your computer

Step 2: check which files need updating

Please refer to the Flare theme release notes and changelog to identify which theme files have been changed/updated since your installed version. If more than one new version has been released since you last installed or updated your current version, you will need to check the release notes and changelog for each subsequent version to identify all the files that need updating.

Step 3: update required files

After you have identified which files need updating, you will then need to update each file individually.

For each file that needs updating, check whether or not you have edited or customized the installed version of that particular file. If you’re not sure, you can use an online tool such as diffchecker.com to compare the original version and the version on your server to check for any differences.

Tip: it’s always a good idea to keep a record of any files that you edit/customize for future reference.

If you haven’t edited/customized the file in question, you can simply upload the new version of the file to the relevant location on your server, overwriting the existing file.

If you have edited/customized the file in question, you will need to either upload the new version of the file and re-apply any edits/customizations, or manually apply any changes in the new version to your existing edited/customized version of the file (see the release notes and changelog for details of file changes in the new version). Which method you choose will depend on the amount of changes in the new version of the file and how extensively you have edited/customized the original file. You will most likely want to choose the method which results in the least required work.

Configurable theme options


Flare theme includes the following configurable theme options:

  • Main navbar and brand display options – including breadcrumb display options
  • Sidebar options
  • Color Scheme and layout options
  • Resource Minification options
  • Theme debug options

These options can be configured by editing the theme-options.tpl file located within the includes directory, in the main flare theme directory, in accordance with the instructions below.

Each order form template also has a number of configurable options. Instructions for editing these options can be found in the relevant section below.

Main navbar and brand display options

Flare theme can be configured to display either an image logo or brand text in the main nav bar, or neither (a useful option if you are including Flare theme within your own website template). Additional options also allow you to you enable or disable the display of the following elements:

  • Breadcrumbs
  • Shopping cart icon
  • Notifications icon
  • Language icon
Option 1.1: enable or disable navbar brand display

This option allows you to specify whether or not the brand (either text or image based logo can be configured by subsequent options) is displayed in the main navbar and can be changed by editing line 25 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itBrandDisplay.

For example:

{assign var=itBrandDisplay value="enabled" scope="global"}

or:

{assign var=itBrandDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.2: specify navbar brand type

This option allows you to specify the type of brand to be displayed in the navbar, either text or an image based logo. This option can be changed by editing line 28 in the theme-options.tpl file, specifying a value of either text or logo for the variable itBrandType.

For example:

{assign var=itBrandType value="text" scope="global"}

or:

{assign var=itBrandType value="logo" scope="global"}

If no value is specified, the default behaviour is text.

Option 1.3: specify the navbar brand logo url (if applicable)

In order to use an image based logo, after specifying the value logo on line 31 (as described above), please provide the url path to your logo image by specifying a value for the variable itBrandLogoUrl on line 26 in the theme-options.tpl file.

For example:

{assign var=itBrandLogoUrl value="http://www.yoursite.com/logo.png" scope="global"}

Please note: the maximum recommended image height is 30px.

Option 1.4: specify navbar brand custom text (if applicable)

If you choose to use brand text rather than an image based logo, you can also provide optional custom text by specifying a value for the variable itBrandText on line 34 in the theme-options.tpl file.

For example:

{assign var=itBrandText value="My Company Name" scope="global"}

Please note: if you choose to use brand text, but do not specify a value for the variable itBrandText the company name, as specified in the WHMCS admin area, will be used.

Option 1.5: enable or disable breadcrumb display

This option allows you to specify whether or not the breadcrumb trail (showing the navigational path to the current page) is displayed below the main navbar. This option can be changed by editing line 37 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itBreadcrumbDisplay.

For example:

{assign var=itBreadcrumbDisplay value="enabled" scope="global"}

or:

{assign var=itBreadcrumbDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.6: enable or disable cart icon display on desktop view

This option allows you to specify whether or not the shopping cart icon (along with a label showing the current number if items in the shopping cart) is displayed in the main navbar on larger screen sizes (such as desktop or laptop computers). This option can be changed by editing line 40 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itCartIconDisplayDesktop.

For example:

{assign var=itCartIconDisplayDesktop value="enabled" scope="global"}

or:

{assign var=itBreadcrumbDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.7: enable or disable cart icon display on mobile view

You can also specify whether or not the shopping cart icon is displayed in the main navbar on smaller screen sizes (such as mobile or tablet devices). This option can be changed by editing line 43 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itCartIconDisplayMobile.

For example:

{assign var=itCartIconDisplayMobile value="enabled" scope="global"}

or:

{assign var=itCartIconDisplayMobile value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.8: enable or disable notifications icon display on desktop view

This option allows you to specify whether or not the notifications icon (along with popover notifications list) is displayed to logged-in users in the main navbar on larger screen sizes (such as desktop or laptop computers). This option can be changed by editing line 46 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itNotificationsIconDisplayDesktop.

For example:

{assign var=itNotificationsIconDisplayDesktop value="enabled" scope="global"}

or:

{assign var=itNotificationsIconDisplayDesktop value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.9: enable or disable notifications icon display on mobile view

You can also specify whether or not the notifications icon (along with popover notifications list) is displayed to logged-in users in the main navbar on smaller screen sizes (such as mobile or tablet devices). This option can be changed by editing line 49 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itNotificationsIconDisplayMobile.

For example:

{assign var=itNotificationsIconDisplayMobile value="enabled" scope="global"}

or:

{assign var=itNotificationsIconDisplayMobile value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.10: enable or disable navbar language icon display on desktop view

This option allows you to specify whether or not the language icon (along with popover language list) is displayed (when language change is enabled) in the main navbar on larger screen sizes (such as desktop or laptop computers). This option can be changed by editing line 52 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itLanguageIconDisplayDesktop.

For example:

{assign var=itLanguageIconDisplayDesktop value="enabled" scope="global"}

or:

{assign var=itLanguageIconDisplayDesktop value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.11: enable or disable navbar language icon display on mobile view

You can also specify whether or not the language icon (along with popover languages list) is displayed (when language change is enabled) in the main navbar on smaller screen sizes (such as mobile or tablet devices). This option can be changed by editing line 55 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itLanguageIconDisplayMobile.

For example:

{assign var=itLanguageIconDisplayMobile value="enabled" scope="global"}

or:

{assign var=itLanguageIconDisplayMobile value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.12: enable or disable footer language icon display

You can also choose to display the language icon (along with popover languages list) in the footer, either instead of or in addition to the navbar language icon. This can be a useful way to create more space in the main nabber if you have a large company name / logo, or additional navbar menu options, or if you simply want a less cluttered navbar. When this option is enabled the language icon will be displayed in the bottom right hand corner of the website footer, and applies to all screen sizes / devices.

This option can be changed by editing line 58 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itLanguageIconDisplayFooter.

For example:

{assign var=itLanguageIconDisplayFooter value="enabled" scope="global"}

or:

{assign var=itLanguageIconDisplayFooter value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Sidebar options

Flare theme allows you to specify whether or not the client area sidebar menus are displayed using the following options.

More information on client area sidebar menus (introduced in WHMCS version 6.0), including how to edit the menu content, can be found in the WHMCS documentation on the WHMCS website here.

If neither the primary or secondary sidebar is shown, the main content panel will automatically increase in size to use up the empty space.

Option 2.1: enable or disable primary sidebar display

This option allows you to choose whether or not the client area primary sidebar is displayed throughout your website. This option applies to all screen sizes / devices and can be changed by editing line 63 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itPrimarySidebar.

For example:

{assign var=itPrimarySidebar value="enabled" scope="global"}

or:

{assign var=itPrimarySidebar value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 2.2: enable or disable secondary sidebar display

This option allows you to choose whether or not the client area secondary sidebar is displayed throughout your website. This option applies to all screen sizes / devices and can be changed by editing line 66 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itSecondarySidebar.

For example:

{assign var=itSecondarySidebar value="enabled" scope="global"}

or:

{assign var=itSecondarySidebar value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Color scheme and layout options

Flare Theme includes five pre-defined color schemes: blue; cyan; orange; red; and green. You can also specify your own custom color scheme, and choose between a fixed width or fluid width layout

The color scheme and layout method can be specified using the options below.

Option 3.1: define color scheme to be used

A color scheme can be selected by specifying a value for the variable itColorScheme on line 71 in the theme-options.tpl file.

Acceptable values are: blue; cyan; orange; red; and green.

For example:

{assign var=itColorScheme value="blue" scope="global"}

or:

{assign var=itColorScheme value="cyan" scope="global"}

or:

{assign var=itColorScheme value="orange" scope="global"}

or:

{assign var=itColorScheme value="red" scope="global"}

or:

{assign var=itColorScheme value="green" scope="global"}

or:

{assign var=itColorScheme value="custom" scope="global"}

Please note: if you do not specify a color scheme, the default blue color scheme will be used.

If the custom value is specified, you must provide the name of the custom style-sheet to use in option 3.2 (see below).

The custom value was introduced in version 1.1.0.

Option 3.2: specify the custom style-sheet to use

If you have entered the value custom for option 3.1 (see above), you can use this option to define the name of your custom style-sheet, by entering the name as the value for the variable itColorSchemeCustomName on line 74 in the theme-options.tpl file.

You should enter the name of your custom style-sheet without the file extension (.css), for example if you custom style-sheet is called my-custom-style-sheet.css / my-custom-style-sheet.min.css you should enter my-custom-style-sheet.

Your custom style-sheet must be uploaded to the flare/css/ directory. You must upload both a minified and non minified version of your style-sheet, both should have the same name, but the minified version should finish with .min.css (eg. em>my-custom-style-sheet.css / my-custom-style-sheet.min.css).

For example:

{assign var=itColorSchemeCustomName value="my-custom-style-sheet" scope="global"}
Option 3.3: define layout method for navbar content

You can specify whether the inner navbar content has a fluid width (expands automatically to take up the available browser space) or fixed width (boxed) by specifying a value for itLayoutNav on line 77 in the theme-options.tpl file.

Acceptable values are: fluid; and fixed.

For example:

{assign var=itLayoutNav value="fluid" scope="global"}

or:

{assign var=itLayoutNav value="fixed" scope="global"}

Please note: if you do not specify a layout method, the default fluid width will be used.

This option was introduced in Flare WHMCS Theme version 1.0.2. Prior to version 1.0.2, the default fluid width layout was used.

Option 3.4: define layout method for main content

You can specify whether the main content has a fluid width (expands automatically to take up the available browser space) or fixed width (boxed) by specifying a value for itLayoutBody on line 80 in the theme-options.tpl file.

Acceptable values are: fluid; and fixed.

For example:

{assign var=itLayoutBody value="fluid" scope="global"}

or:

{assign var=itLayoutBody value="fixed" scope="global"}

Please note: if you do not specify a layout method, the default fluid width will be used.

This option was introduced in Flare WHMCS Theme version 1.0.2. Prior to version 1.0.2, the default fluid width layout was used.

Resource minification options

The following options allow you to define whether minified or full versions of the main theme and order form template JavaScript and CSS files are loaded. We would always recommend using minified versions for day to day use, but it can be useful to useful to load the full versions for customization/testing purposes.

These options were introduced in Flare theme version 2.1.0.

Option 4.1: enable or disable use of minified CSS

You can enable to disable the use of minified CSS by editing line 85 of the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itCSSMin.

For example:

{assign var=itCSSMin value="enabled" scope="global"}

or:

{assign var=itCSSMin value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 4.2: enable or disable use of minified JS

You can enable to disable the use of minified JS by editing line 88 of the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itJSMin.

For example:

{assign var=itJSMin value="enabled" scope="global"}

or:

{assign var=itJSMin value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Theme debug options

Flare theme also includes a debug option which can be used to provide useful information on theme options and function variables for development and trouble-shooting purposes.

Option 5.1: enable or disable theme debug mode

Theme debug mode can be enabled or disabled by editing line 93 in the theme-options.tpl file, specifying a value of either enabled or disabled for the variable itThemeDebug.

For example:

{assign var=itThemeDebug value="enabled" scope="global"}

or:

{assign var=itThemeDebug value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Configurable order form template options


Each order form / shopping cart template also has a number of configurable options.

These can be configured by editing the cart-options.tpl file in the relevant order form template folder.

Flare Standard order form template options

The Flare Standard order form template has a number of configurable options which apply to all included order form pages, unless specified otherwise.

Option 1.1: enable or disable sidebar display on order form / cart pages

This option allows you to choose whether or not the sidebar is displayed on all order form / cart pages. This option applies to large screen sizes / desktop devices and can be changed by editing line 24 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartSidebarDisplay.

For example:

{assign var=itCartSidebarDisplay value="enabled" scope="global"}

or:

{assign var=itCartSidebarDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.2: enable or disable mobile friendly sidebar display on order form / cart pages

This option allows you to choose whether or not the sidebar is displayed on all order form / cart pages. This option applies to small screen sizes / mobile devices and can be changed by editing line 27 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartSidebarMobileDisplay.

For example:

{assign var=itCartSidebarMobileDisplay value="enabled" scope="global"}

or:

{assign var=itCartSidebarMobileDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 2.1: enable or disable product category and view cart button on view products and view addons pages

This option allows you to choose whether or not the product categories dropdown menu and view cart button are shown at the top of the view products and view addons pages. This is a useful alternative way of linking to the various product categories and view cart page if you decide to disable the cart sidebar. This option can be configured by editing line 32 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartProductsButton.

For example:

{assign var=itCartProductsButton value="enabled" scope="global"}

or:

{assign var=itCartProductsButton value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 3.1: enable or disable auto scrolling order summary on configure product page

This option allows you to choose whether or not to enable auto scrolling for the order summary panel on the configure product page (i.e. the order summary panel scrolls along with the page). This option can be configured by editing line 37 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartScrollProductSummary.

For example:

{assign var=itCartScrollProductSummary value="enabled" scope="global"}

or:

{assign var=itCartScrollProductSummary value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 4.1: enable or disable currency chooser on all cart pages

This option allows you to choose whether or not the currency chooser button is shown at the bottom of relevant pages (when applicable). This is a useful alternative way of allowing users to change currency if you decide to disable the cart sidebar. This option can be configured by editing line 42 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartCurrencyChooser.

For example:

{assign var=itCartCurrencyChooser value="enabled" scope="global"}

or:

{assign var=itCartCurrencyChooser value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 5.1: select color scheme for iCheck checkbox and radio inputs

The Flare order form templates make use of the iCheck plugin to customise the display of checkbox and radio inputs, using the iCheck Flat skin. The plugin allows you to choose from a number of predefined color schemes. By default, the Flare order form templates will use either blue, red, orange, cyan or green, depending on which overall color scheme you have chosen in the main theme options, however you may wish to choose a different color scheme, for example if you have customised the theme to use your own color scheme.

This option can be changed by editing line 47 in the cart-options.tpl file, specifying a value of either default, black, grey, red, orange, green, yellow, blue, pink, aero or purple for the variable itCartiCheckColor.

For example:

{assign var=itCartiCheckColor value="default" scope="global"}

or:

{assign var=itCartiCheckColor value="grey" scope="global"}

If no value is specified, the default behaviour is default.

Option 6.1: Configure the number of products shown per row on the view products page

This option allows you to choose the number of products shown per row on the view products page, choosing between 1 and 4 products per row.

This option can be changed by editing line 52 in the cart-options.tpl file, specifying a value of either 1, 2, 3 or 4 for the variable itCartNumberProductsPerRow.

For example:

{assign var=itCartNumberProductsPerRow value="1" scope="global"}

or:

{assign var=itCartNumberProductsPerRow value="2" scope="global"}

If no value is specified, the default behaviour is 1.

This option was introduced in Flare theme version 2.2.0.

Option 6.2: Configure the number of addons shown per row on the view available addons page

This option allows you to choose the number of addons shown per row on the view available addons page, choosing between 1 and 4 addons per row.

This option can be changed by editing line 55 in the cart-options.tpl file, specifying a value of either 1, 2, 3 or 4 for the variable itCartNumberAddonsPerRow.

For example:

{assign var=itCartNumberAddonsPerRow value="1" scope="global"}

or:

{assign var=itCartNumberAddonsPerRow value="2" scope="global"}

If no value is specified, the default behaviour is 1.

This option was introduced in Flare theme version 2.2.0.

Option 7.1: enable or disable auto scrolling order summary on domain renewal page

This option allows you to choose whether or not to enable auto scrolling for the order summary panel on the domain renewal page (i.e. the order summary panel scrolls along with the page). This option can be configured by editing line 60 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartScrollRenewalSummary .

For example:

{assign var=itCartScrollRenewalSummary  value="enabled" scope="global"}

or:

{assign var=itCartScrollRenewalSummary  value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

This option was introduced in Flare theme version 2.6.0.

Flare Compare order form template options

The Flare Compare order form template has its own cart-options.tpl file, however these options will only apply to the Flare Compare view products page. This is because Flare Compare is a child template of the Flare Standard order form template, and all other cart pages are handled by the Flare Standard template.

Option 1.1: enable or disable sidebar display on order form / cart pages

This option allows you to choose whether or not the sidebar is displayed. This option applies to large screen sizes / desktop devices and can be changed by editing line 24 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartSidebarDisplay.

For example:

{assign var=itCartSidebarDisplay value="enabled" scope="global"}

or:

{assign var=itCartSidebarDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.2: enable or disable mobile friendly sidebar display on order form / cart pages

This option allows you to choose whether or not the sidebar is displayed. This option applies to small screen sizes / mobile devices and can be changed by editing line 27 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartSidebarMobileDisplay.

For example:

{assign var=itCartSidebarMobileDisplay value="enabled" scope="global"}

or:

{assign var=itCartSidebarMobileDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 2.1: enable or disable product category and view cart button on view products page

This option allows you to choose whether or not the product categories dropdown menu and view cart button are shown at the top of the view products page. This is a useful alternative way of linking to the various product categories and view cart page if you decide to disable the cart sidebar. This option can be configured by editing line 32 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartProductsButton.

For example:

{assign var=itCartProductsButton value="enabled" scope="global"}

or:

{assign var=itCartProductsButton value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 3.1: enable or disable currency chooser on all cart pages

This option allows you to choose whether or not the currency chooser button is shown at the bottom of the page (when applicable). This is a useful alternative way of allowing users to change currency if you decide to disable the cart sidebar. This option can be configured by editing line 37 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartCurrencyChooser.

For example:

{assign var=itCartCurrencyChooser value="enabled" scope="global"}

or:

{assign var=itCartCurrencyChooser value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 4.1: Configure the number of products shown per row on the view products page

This option allows you to choose the number of products shown per row on the view products page, choosing between 1 and 6 products per row.

This option can be changed by editing line 42 in the cart-options.tpl file, specifying a value of either 1, 2, 3, 4, 5 or 6 for the variable itCartNumberProductsPerRow.

For example:

{assign var=itCartNumberProductsPerRow value="1" scope="global"}

or:

{assign var=itCartNumberProductsPerRow value="2" scope="global"}

If no value is specified, the default behaviour is 1.

This option was introduced in Flare theme version 2.2.0.

Flare Slider order form template options

The Flare Slider order form template has its own cart-options.tpl file, however these options will only apply to the Flare Slider view products page. This is because Flare Slider is a child template of the Flare Standard order form template, and all other cart pages are handled by the Flare Standard template.

Option 1.1: enable or disable sidebar display on order form / cart pages

This option allows you to choose whether or not the sidebar is displayed. This option applies to large screen sizes / desktop devices and can be changed by editing line 24 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartSidebarDisplay.

For example:

{assign var=itCartSidebarDisplay value="enabled" scope="global"}

or:

{assign var=itCartSidebarDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 1.2: enable or disable mobile friendly sidebar display on order form / cart pages

This option allows you to choose whether or not the sidebar is displayed. This option applies to small screen sizes / mobile devices and can be changed by editing line 27 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartSidebarMobileDisplay.

For example:

{assign var=itCartSidebarMobileDisplay value="enabled" scope="global"}

or:

{assign var=itCartSidebarMobileDisplay value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 2.1: enable or disable product category and view cart button on view products page

This option allows you to choose whether or not the product categories dropdown menu and view cart button are shown at the top of the view products page. This is a useful alternative way of linking to the various product categories and view cart page if you decide to disable the cart sidebar. This option can be configured by editing line 32 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartProductsButton.

For example:

{assign var=itCartProductsButton value="enabled" scope="global"}

or:

{assign var=itCartProductsButton value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Option 3.1: enable or disable currency chooser on all cart pages

This option allows you to choose whether or not the currency chooser button is shown at the bottom of the page (when applicable). This is a useful alternative way of allowing users to change currency if you decide to disable the cart sidebar. This option can be configured by editing line 37 in the cart-options.tpl file, specifying a value of either enabled or disabled for the variable itCartCurrencyChooser.

For example:

{assign var=itCartCurrencyChooser value="enabled" scope="global"}

or:

{assign var=itCartCurrencyChooser value="disabled" scope="global"}

If no value is specified, the default behaviour is disabled.

Customizing Flare theme


All of our code is fully open, unencrypted and editable, meaning that should for any reason our products provided as are do not suit your exact requirements, you are free to customise the code as necessary. Whilst you are perfectly welcome to do this, please note that our support team is unable to provide support or assistance with this process. We are only able to provide assistance with the installation, configuration and use of our products as provided in accordance with our theme documentation.

Tip: it’s always a good idea to keep a record of any files that you edit/customize for future reference.

Customizing the themes CSS

There are two recommended methods for applying CSS customizations. By following one of these methods, it will be easier to upgrade to future versions of the theme.

Method 1 – minor edits

If you are only making minor changes/edits to the theme CSS, the easiest method is to add these to the custom.css file, located at flare/css/custom.css. The custom.css file is loaded after the main theme CSS files, so any styles defined in this file will override the styles defined in the main theme files.

By defining your custom styles in the custom.css file, rather than directly editing any of the main theme stylesheets, when you next apply a theme update which includes updated versions of the main CSS file, you can simply upload these updated files without worrying about overwriting any changes/edits you have made.

Method 2 – major edits

If you are making major changes/edits to the theme CSS, it is recommended to duplicate one of the existing main theme CSS files, such as flare-default.css or flare-green.css and make your changes in the duplicated file. You can then use options 3.1 and 3.2 in the theme-options.tpl file to load your customized style-sheet rather than any of the pre-defined styles.

Please note that when using this method, you will need to manually apply any style-sheet updates included in future theme upgrades to your custom style-sheet, if appplicable.

Trouble-shooting and support


If you can’t find a solution to your problem in this theme documentation or our frequently asked questions, please open a support ticket to request technical support.

Changelog and release history


Theme Version Release Date WHMCS Version Compatibility Release Notes
2.22.027 April 20248.10.0-8.10.1Release Notes
2.21.013 March 20248.9.0Release Notes
2.20.124 October 20238.8.0Release Notes
2.20.026 September 20238.8.0Release Notes
2.19.14 May 20238.7.2Release Notes
2.19.026 March 20238.7.0-8.7.1Release Notes
2.18.06 November 20228.6.0Release Notes
2.17.114 September 20228.5.0-8.5.1Release Notes
2.17.013 June 20228.5.0-8.5.1Release Notes
2.16.020 January 20228.4.0Release Notes
2.15.131 October 20218.3.1-8.3.2Release Notes
2.15.018 October 20218.3.0Release Notes
2.14.114 July 20218.2.1Release Notes
2.14.023 June 20218.2.0Release Notes
2.13.419 April 20218.1.2-8.1.3Release Notes
2.13.325 February 20218.1.2-8.1.3Release Notes
2.13.211 February 20218.1.1Release Notes
2.13.123 January 20218.1.0Release Notes
2.13.05 January 20218.1.0Release Notes
2.12.420 November 20208.0.1-8.0.4Release Notes
2.12.324 October 20208.0.0-8.0.1Release Notes
2.12.217 October 20208.0.1-8.0.3Release Notes
2.12.17 October 20208.0.1-8.0.3Release Notes
2.12.029 September 20208.0.0Release Notes
2.11.07 April 20207.10.0 - 7.10.2Release Notes
2.10.120 February 20207.9.2Release Notes
2.10.09 January 20207.9.0Release Notes
2.9.25 October 20197.8.0 - 7.8.3Release Notes
2.9.16 September 20197.8.0 - 7.8.3Release Notes
2.9.01 September 20197.8.0 - 7.8.1Release Notes
2.8.023 January 20197.7.0 - 7.7.1Release Notes
2.7.12 September 20187.6.0 - 7.6.1Release Notes
2.7.06 August 20187.6.0 - 7.6.1Release Notes
2.6.223 July 20187.5.0 - 7.5.2Release Notes
2.6.18 April 20187.5.0 - 7.5.2Release Notes
2.6.04 April 20187.5.0 - 7.5.2Release Notes
2.5.110 January 20187.4.0 - 7.4.3Release Notes
2.5.018 November 20177.4.0 - 7.4.3Release Notes
2.4.05 October 20177.3.0 - 7.3.1Release Notes
2.3.33 September 20177.2.2 - 7.2.3Release Notes
2.3.24 June 20177.2.2 - 7.2.3Release Notes
2.3.116 May 20177.2.0 - 7.2.1Release Notes
2.3.016 May 20177.2.0 - 7.2.1Release Notes
2.2.019 April 20177.1.0 - 7.1.2Release Notes
2.1.215 January 20177.1.0 - 7.1.2Release Notes
2.1.119 December 20167.1.0 - 7.1.2Release Notes
2.1.017 December 20167.1.0 - 7.1.2Release Notes
2.0.216 November 20167.0.1 - 7.0.2Release Notes
2.0.117 October 20177.0.1 - 7.0.2Release Notes
2.0.03 October 20167.0.0Release Notes
1.1.025 September 20166.3.1Release Notes
1.0.63 August 20166.3.1Release Notes
1.0.518 July 20166.3.1Release Notes
1.0.414 July 20166.3.1Release Notes
1.0.325 May 20166.3.1Release Notes
1.0.224 May 20166.3.1Release Notes
1.0.121 April 20166.3.1Release Notes
1.0.08 April 20166.3.0Release Notes