Version 7.0 Release Notes

From WHMCS Documentation

Release Information
Version: 7.0
Release Type: Release Candidate
Release Date: 16th September 2016
Distribution Types: Full Version Only

Version History

VersionRelease TypeRelease Date
7.0.0Beta 122nd July 2016
7.0.0Beta 25th August 2016
7.0.0Beta 325th August 2016
7.0.0RC 116th September 2016
7.0.0GA3rd October 2016
7.0.1Maintenance14th October 2016
7.0.2Maintenance28th November 2016
7.0.3TSR29th December 2016


Download the latest version of WHMCS from

Upgrade Process

View Standard Upgrade Steps

Release Notes

New PHP Version Requirements
WHMCS 7.0 requires PHP 5.6 or later. If you are running any versions earlier than PHP 5.6, you must upgrade PHP before attempting to upgrade to WHMCS 7.0. WHMCS 7.0 also requires ionCube Loader® v5.0.21 or later.
  • Version 7.0.0 System Requirements: WHMCS v7 minimum system requirements are PHP 5.6 and stable ionCube Loader 5.0.21 or later. WHMCS v7 also supports PHP 7 - in order to ensure complete compatibility, please install ionCube Loader 6.0.2 or later.
  • Automatic Updater - WHMCS 7.0 is the last update you will ever need to download! WHMCS 7.0 includes an Auto Update utility which allows you to install updates to WHMCS with just a few clicks. Built on the proven core of Composer, the WHMCS Auto Updater downloads, verifies, unpacks and performs database upgrades for WHMCS. The Auto Updater checks for updates as part of your system cron, and will provide administrators with alerts letting them know when a new release is available. Check our full article for more information and system requirements.
  • Domain Checker Improvements - The domain checker has been integrated into the shopping cart, and along with the new domain lookup functionality introduced in WHMCS 7.0 including spotlight TLDs and sale groups, is designed to offer a more streamlined and consistent domain lookup and purchase experience for end users. The domain checker file remains in place to provide redirects that will automatically redirect most previous domain checker based requests and form submissions to the new cart based domain lookup. The bulk domain check and bulk domain transfer facilities within the client area have been removed in 7.0. The new domain lookup functionality provided within the shopping cart in 7.0 is intended to deliver a more intuitive and optimised user experience for searching for and adding multiple domains to the shopping cart.
  • System Cron Update - WHMCS 7.0 introduces a new scheduling system that allows WHMCS the flexibility to perform automated tasks at intervals of less than every 24 hours.
Action Required
We recommend updating your configured system cron (cron.php) to run every 5 minutes or as frequently as your web hosting provider allows. (minimum once per hour) Learn more…
  • Ticket Feedback per Department - In WHMCS 7.0, you can now enable the email request for a user to provide feedback for their support ticket experience on a per department basis. Previously this was a global option that applied to all departments within the General Settings. On upgrade, if you have the Ticket Feedback feature enabled, it will be enabled by default for all existing departments. If you do not have it enabled, it will not be enabled for any departments automatically.
  • WHOIS Servers, Countries and Additional Domain Fields Overrides - WHMCS 7.0 introduces override capabilities to additional domain fields, whois servers and countries. These have been introduced to provide an easy way for customisations to these files to be maintained during automatic updates. In addition, the location and format used for some of these files has changed.
Important Note
If you have previously made customisations to whois servers, additional domain fields or countries and calling codes files, you will need to migrate your customisations to the new file locations and/or file formats. For more information please refer to the following documentation pages:
  • SSL Changes - The System URL and System SSL URL fields have been combined in WHMCS 7.0 to a single field. It is recommended that an SSL enabled URL be provided for the System URL at all times. When SSL is available, it will now be used for all requests, both admin and client side. If a System SSL URL was defined prior to upgrade, this value will be preserved and used for the System URL.
  • DuoSecurity - WHMCS 7.0 allows users of DuoSecurity to configure their own DuoSecurity Account Credentials. This makes DuoSecurity accessible to everyone and allows users to take advantage of the up to 10 free users offered by Duo.
For any existing users subscribing to DuoSecurity through us, we will be reaching out to you shortly regarding migrating your subscriptions. Learn more…
  • Session Changes - In addition to the above, when SSL is available, session cookies will now have the secure flag set (CORE-10037) in accordance with PCI-DSSv3.1 requirements. This results in session data only being accessible via an SSL connection.
  • Removal of Client Dropdown Format setting -As of WHMCS 7.0, the Client Dropdown Format setting has been removed. In WHMCS 6.2 we introduced an improved client navigation experience using a combo box that provides a dropdown supporting text entry to filter the list of available clients to navigate to. The new dynamic dropdown displays clients names, company names and email addresses at all times and so this setting is no longer utilised.
  • Deprecation of Five Theme - With the release of WHMCS 7.0, we will no longer be shipping the "Five" client area theme (previously named "default" in WHMCS V5.x). Current installations of WHMCS will not have the "Five" theme removed, but this theme will not receive any further updates. While this theme will no longer be shipped or maintained, for users who are using it or have a custom theme based on it, it will continue to work but we offer no guarantee of compatibility with future releases. We strongly recommend that all new custom themes and templates are built based off the "Six" theme in order to take full advantage of the latest improvements and new functionality. Detailed information about the "Six" theme is available in our documentation at Customising the Six Theme.
  • Template Security Adjustments - Introduced in Version 7, if your template invokes & includes a PHP script by using the Smarty {include_php} syntax, the full path to the directory containing that script will need to be whitelisted in the 'trusted_dir' setting of your Policy.
  • Removal of Browser Tool - Previous versions of WHMCS contained a tool named "Browser" located under the Utilities menu. As of WHMCS 7.0, this utility has been removed. If you used this functionality to share a list of URLs with your staff, we recommend you instead create a set of bookmarks in your browser that can be exported and imported. For example, see:
  • Deprecation of InternetSecure Payment Processor - The InternetSecure payment processor service is being discontinued on August 31, 2016. As a result, we will no longer shipping the InternetSecure module. For existing installations, the module will not be removed, however users are recommended to find an alternative payment processor before that time. For a full list of payment gateway options, navigate to Setup > Payment Gateways within your WHMCS installation.
  • jQuery UI Library Update - The version of the jQuery UI library we ship with WHMCS has been updated from v1.11.2 to v1.11.4. As part of that update, we removed the tooltip functionality to resolve a compatibility issue with Bootstrap tooltips. If you were previously using jQuery UI tooltips, we recommend replacing it with the Bootstrap tooltip functionality should it be required in any custom code.
  • WHMCS Core Library move to vendor directory - WHMCS uses the Composer dependency management system for PHP to maintain our included libraries. These libraries can be found as subdirectories within the /vendor/ directory of a WHMCS installation. As of WHMCS 7.0, the core WHMCS PHP library is now also located in the /vendor/ directory similar to other Composer libraries. Previously these files would have been located in /includes/classes/WHMCS/.
We do not recommend nor support placing your own classes within the WHMCS namespace. WHMCS assumes full authority of the WHMCS namespace and classes directories and offer no guarantees that files you place there will not be overwritten or removed. The update process for version 7.0 will not remove any files in the historic location /includes/classes/ and will leave them untouched.
  • Dependency Updates - Our dependencies were updated to take advantage of the best and most modern features that are available. The Illuminate dependencies provided by Laravel, which form the basis of our Database ORM layer, reflect major changes to how these packages deal with objects. The Symfony dependencies were updated to allow easier access and manipulation native structural components. The latest version of PHPseclib added more IPv6 support, as well as included minor bug fixes. Below is a complete list of dependencies updated and removed in Version 7:

New Documentation Articles

Dependency Updates

  • Uninstalled
    • guzzle/guzzle (v3.9.3)
    • symfony/event-dispatcher (v2.8.11)
  • Installed
    • composer/composer (1.0.3)
    • composer/semver (1.4.2)
    • composer/spdx-licenses (1.1.4)
    • doctrine/inflector (v1.1.0)
    • guzzlehttp/guzzle (5.0.3)
    • guzzlehttp/ringphp (1.1.0)
    • guzzlehttp/streams (3.0.0)
    • illuminate/console (v5.2.37)
    • illuminate/contracts (v5.2.45)
    • justinrainbow/json-schema (1.6.1)
    • mtdowling/cron-expression (v1.1.0)
    • paragonie/random_compat (v1.4.1)
    • react/promise (v2.4.1)
    • symfony/console (v2.8.11)
    • symfony/finder (v2.8.7)
    • symfony/filesystem (v3.0.9)
    • symfony/polyfill-php55 (v1.2.0)
    • symfony/polyfill-php54 (v1.2.0)
    • symfony/polyfill-mbstring (v1.2.0)
    • symfony/process (v2.8.11)
    • seld/jsonlint (1.4.1)
    • seld/phar-utils (1.0.1)
  • Updated
    • illuminate/support (v4.1.30) to illuminate/support (v5.2.37)
    • illuminate/container (v4.1.30) to illuminate/container (v5.2.37)
    • illuminate/database (v4.1.30) to illuminate/database (v5.2.37)
    • illuminate/events (v4.1.30) to illuminate/events (v5.2.37)
    • knplabs/knp-menu (v2.1.0) to knplabs/knp-menu (v2.1.1)
    • league/climate (3.2.0) to league/climate (3.2.1)
    • monolog/monolog (1.17.2) to monolog/monolog (1.18.2)
    • nesbot/carbon (1.20.0) to nesbot/carbon (1.21.0)
    • php-imap/php-imap (2.0.4) to php-imap/php-imap (2.0.6)
    • phpmailer/phpmailer (v5.2.14) to phpmailer/phpmailer (v5.2.16)
    • phpseclib/phpseclib (1.0.0) to phpseclib/phpseclib (2.0.2)
    • rhumsaa/uuid (2.8.2) to ramsey/uuid (3.4.1)
    • smarty/smarty (v3.1.21) to smarty/smarty (v3.1.29)
    • symfony/http-foundation (v2.6.11) to symfony/http-foundation (v2.8.7)
    • symfony/translation (v2.6.11) to symfony/translation (v2.8.7)
    • symfony/yaml (v2.6.11) to symfony/yaml (v2.8.7)

Template Changes

Six Template

For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.

The following link provides a comparison of changes between 6.3.1 and 7.0.2.

There are no incremental changes for the Six template between versions 7.0.1 and 7.0.2.

Standard Cart Order Form

For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.

The following link provides a comparison of changes between 6.3.0 and 7.0.2:

The following link provides a comparison of changes between 7.0.1 and 7.0.2.