WHMCS 7.0.1

18 October 2016

WHMCS version 7.0.1 is now available (major release).

Upgrading to WHMCS 7.0.1

What's New in WHMCS 7.0.1

• Automatic Updates - Now updates are just a click away.
• Spotlight TLDs - Highlight your best selling TLDs and extensions to maximise conversions. Also includes sale groups that allow you to highlight extensions that are New, Hot and on Sale.
• PHP 7 Support - PHP 7 has been hailed as the most important update to PHP since the release of PHP 5 in 2004 due to the significant performance improvements and dramatically reduced memory consumption it offers.
• 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.
• 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.
• 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.
• WHOIS Servers, Countries and Additional Domain Fields Overrides - WHMCS 7.0 introduces override capabilities to additional domain fields, whois servers and countries.
• 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.
• 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.
• Smarty Security Policy Update - WHMCS 7.0 introduces support for Smarty Security Policies. The default policies are to allow all PHP functionality in system templates but only a restricted predefined list of functions and modifiers in email templates. For most use cases, these policies will not need to be modified. Learn more at Public Documentation for End Users.
• 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: https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer
• 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/.
• 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.