<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://3.19.219.109/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Cole</id>
		<title>WHMCS Documentation - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://3.19.219.109/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Cole"/>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/Special:Contributions/Cole"/>
		<updated>2026-04-03T20:43:34Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.29.1</generator>

	<entry>
		<id>http://3.19.219.109/index.php?title=Version_7.0.1_Release_Notes&amp;diff=20570</id>
		<title>Version 7.0.1 Release Notes</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Version_7.0.1_Release_Notes&amp;diff=20570"/>
				<updated>2016-10-14T18:10:17Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot; style=&amp;quot;max-width:370px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Release Information&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Version: 7.0.1&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Type: Release Candidate&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Date: 14th September 2016&amp;lt;br /&amp;gt;&lt;br /&gt;
Distribution Types: Full Version Only&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Version&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Type&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Date&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Release 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;14th October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download the latest version of WHMCS from http://download.whmcs.com/&lt;br /&gt;
&lt;br /&gt;
==Upgrade Process==&lt;br /&gt;
[[Upgrading|View Standard Upgrade Steps]]&lt;br /&gt;
&lt;br /&gt;
=== Six Template ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.1 and 7.0.0.&lt;br /&gt;
https://github.com/WHMCS/templates-six/compare/v6.3.1-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 7.0.0 and 7.0.1.&lt;br /&gt;
https://github.com/WHMCS/templates-six/compare/v7.0.0-release.1...v7.0.1-release.1&lt;br /&gt;
&lt;br /&gt;
==Changelog==&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.1|Version 7.0.1]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.1&amp;diff=20498</id>
		<title>Changelog:WHMCS V7.0.1</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.1&amp;diff=20498"/>
				<updated>2016-10-14T14:29:28Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Version 7.0.1 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-10479&amp;amp;nbsp;-&amp;amp;nbsp;Ensure email replies to support ticket notifications pipe properly in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10483&amp;amp;nbsp;-&amp;amp;nbsp;Do not present domain order workflow if &amp;amp;quot;I will use my own domain&amp;amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10484&amp;amp;nbsp;-&amp;amp;nbsp;Improve handling of domain attributes when adding product to cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10489&amp;amp;nbsp;-&amp;amp;nbsp;Fix non-functional mass action buttons in admin client summary page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10491&amp;amp;nbsp;-&amp;amp;nbsp;Improve functionality of Client Area service list filters&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10502&amp;amp;nbsp;-&amp;amp;nbsp;Ensure one year term for &amp;amp;quot;free&amp;amp;quot; domains adding in cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10505&amp;amp;nbsp;-&amp;amp;nbsp;Remove unnecessary option &amp;amp;quot;Admin Force SSL Access&amp;amp;quot; in general settings&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10509&amp;amp;nbsp;-&amp;amp;nbsp;Correct query for ungrouped invoice line item aggregation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10510&amp;amp;nbsp;-&amp;amp;nbsp;Ensure consistent argument separator use across various environments&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6454&amp;amp;nbsp;-&amp;amp;nbsp;eWAY Tokens - Prevent spaces being sent in EWAY_CARDNUMBER - V6110&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10488&amp;amp;nbsp;-&amp;amp;nbsp;Improve WHM package name auto detection logic&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10499&amp;amp;nbsp;-&amp;amp;nbsp;Update Spanish DomainIsUnavailable language string&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20494</id>
		<title>Version 7.0 Release Notes</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20494"/>
				<updated>2016-10-14T14:28:24Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot; style=&amp;quot;max-width:370px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Release Information&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Version: 7.0&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Type: Release Candidate&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Date: 16th September 2016&amp;lt;br /&amp;gt;&lt;br /&gt;
Distribution Types: Full Version Only&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Version&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Type&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Date&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;22nd July 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;5th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;25th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;RC 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;16th September 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;GA&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3rd October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;GA&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;14th October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download the latest version of WHMCS from http://download.whmcs.com/&lt;br /&gt;
&lt;br /&gt;
==Upgrade Process==&lt;br /&gt;
[[Upgrading|View Standard Upgrade Steps]]&lt;br /&gt;
&lt;br /&gt;
==Release Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-success&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; New PHP Version Requirements'''&amp;lt;br /&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''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 the latest Ioncube loader 6.0.2 or later.&lt;br /&gt;
 &lt;br /&gt;
* '''[[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.  [[Automatic Updater|Check our full article for more information and system requirements]].&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Action Required'''&amp;lt;br&amp;gt;We recommend updating your configured system cron (cron.php) to run every 5 minutes or as frequently as your web hosting provider allows. [[Cron_Tasks#System_Cron_Frequency|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-question-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Important Note'''&amp;lt;br&amp;gt;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:&lt;br /&gt;
*http://docs.whmcs.com/Additional_Domain_Fields&lt;br /&gt;
*http://docs.whmcs.com/WHOIS_Servers&lt;br /&gt;
*http://docs.whmcs.com/Customising_Countries_and_Calling_Codes&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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 [http://go.whmcs.com/918/duo-security-signup 10 free users offered by Duo].&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;For any existing users subscribing to DuoSecurity through us, we will be reaching out to you shortly regarding migrating your subscriptions. [[Duo_Security#WHMCS_DuoSecurity_Account_Migration|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''Deprecation of Five Theme''' - With the release of WHMCS 7.0, we will no longer be shipping the &amp;quot;Five&amp;quot; client area theme (previously named &amp;quot;default&amp;quot; in WHMCS V5.x).  Current installations of WHMCS will not have the &amp;quot;Five&amp;quot; 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 &amp;quot;Six&amp;quot; theme in order to take full advantage of the latest improvements and new functionality. Detailed information about the &amp;quot;Six&amp;quot; theme is available in our documentation at [[Customising the Six Theme]].&lt;br /&gt;
 &lt;br /&gt;
* '''[[Smarty Security Policy|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. [[Smarty Security Policy|Learn more at Public Documentation for End Users]].&lt;br /&gt;
&lt;br /&gt;
*'''[[Template_Syntax|Template Security Adjustments]]''' - Introduced in Version 7, if your template invokes &amp;amp; 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.&lt;br /&gt;
&lt;br /&gt;
* '''Removal of Browser Tool''' - Previous versions of WHMCS contained a tool named &amp;quot;Browser&amp;quot; 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&lt;br /&gt;
&lt;br /&gt;
* '''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 &amp;gt; Payment Gateways'' within your WHMCS installation.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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/.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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:&lt;br /&gt;
&lt;br /&gt;
==New Documentation Articles==&lt;br /&gt;
* [[Automatic Updater]]&lt;br /&gt;
* [[Smarty Security Policy]]&lt;br /&gt;
* [[Customising Countries and Calling Codes]]&lt;br /&gt;
* [[WHOIS Servers]]&lt;br /&gt;
* [[Additional Domain Fields]]&lt;br /&gt;
&lt;br /&gt;
===Dependency Updates===&lt;br /&gt;
&lt;br /&gt;
* '''Uninstalled'''&lt;br /&gt;
** guzzle/guzzle (v3.9.3)&lt;br /&gt;
** symfony/event-dispatcher (v2.8.11)&lt;br /&gt;
&lt;br /&gt;
* '''Installed'''&lt;br /&gt;
** composer/composer (1.0.3)&lt;br /&gt;
** composer/semver (1.4.2)&lt;br /&gt;
** composer/spdx-licenses (1.1.4)&lt;br /&gt;
** doctrine/inflector (v1.1.0)&lt;br /&gt;
** guzzlehttp/guzzle (5.0.3)&lt;br /&gt;
** guzzlehttp/ringphp (1.1.0)&lt;br /&gt;
** guzzlehttp/streams (3.0.0)&lt;br /&gt;
** illuminate/console (v5.2.37)&lt;br /&gt;
** illuminate/contracts (v5.2.45)&lt;br /&gt;
** justinrainbow/json-schema (1.6.1)&lt;br /&gt;
** mtdowling/cron-expression (v1.1.0)&lt;br /&gt;
** paragonie/random_compat (v1.4.1)&lt;br /&gt;
** react/promise (v2.4.1)&lt;br /&gt;
** symfony/console (v2.8.11)&lt;br /&gt;
** symfony/finder (v2.8.7)&lt;br /&gt;
** symfony/filesystem (v3.0.9)&lt;br /&gt;
** symfony/polyfill-php55 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-php54 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-mbstring (v1.2.0)&lt;br /&gt;
** symfony/process (v2.8.11)&lt;br /&gt;
** seld/jsonlint (1.4.1)&lt;br /&gt;
** seld/phar-utils (1.0.1)&lt;br /&gt;
&lt;br /&gt;
* '''Updated'''&lt;br /&gt;
** illuminate/support (v4.1.30) to illuminate/support (v5.2.37)&lt;br /&gt;
** illuminate/container (v4.1.30) to illuminate/container (v5.2.37)&lt;br /&gt;
** illuminate/database (v4.1.30) to illuminate/database (v5.2.37)&lt;br /&gt;
** illuminate/events (v4.1.30) to illuminate/events (v5.2.37)&lt;br /&gt;
** knplabs/knp-menu (v2.1.0) to knplabs/knp-menu (v2.1.1)&lt;br /&gt;
** league/climate (3.2.0) to league/climate (3.2.1)&lt;br /&gt;
** monolog/monolog (1.17.2) to monolog/monolog (1.18.2)&lt;br /&gt;
** nesbot/carbon (1.20.0) to nesbot/carbon (1.21.0)&lt;br /&gt;
** php-imap/php-imap (2.0.4) to php-imap/php-imap (2.0.6)&lt;br /&gt;
** phpmailer/phpmailer (v5.2.14) to phpmailer/phpmailer (v5.2.16)&lt;br /&gt;
** phpseclib/phpseclib (1.0.0) to phpseclib/phpseclib (2.0.2)&lt;br /&gt;
** rhumsaa/uuid (2.8.2) to ramsey/uuid (3.4.1)&lt;br /&gt;
** smarty/smarty (v3.1.21) to smarty/smarty (v3.1.29)&lt;br /&gt;
** symfony/http-foundation (v2.6.11) to symfony/http-foundation (v2.8.7)&lt;br /&gt;
** symfony/translation (v2.6.11) to symfony/translation (v2.8.7)&lt;br /&gt;
** symfony/yaml (v2.6.11) to symfony/yaml (v2.8.7)&lt;br /&gt;
&lt;br /&gt;
==Template Changes==&lt;br /&gt;
&lt;br /&gt;
=== Six Template ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.1 and 7.0.0-release.1.&lt;br /&gt;
https://github.com/WHMCS/templates-six/compare/v6.3.1-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
=== Standard Cart Order Form ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.0 and 7.0.0-release.1:&lt;br /&gt;
https://github.com/WHMCS/orderforms-standard_cart/compare/v6.3.0-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
==Changelog==&lt;br /&gt;
&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_1|Version 7.0.0 Beta 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_2|Version 7.0.0 Beta 2]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_3|Version 7.0.0 Beta 3]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_RC_1|Version 7.0.0 RC 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_GA|Version 7.0.0 GA]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.1|Version 7.0.1]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20490</id>
		<title>Version 7.0 Release Notes</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20490"/>
				<updated>2016-10-14T14:27:00Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Version History */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot; style=&amp;quot;max-width:370px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Release Information&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Version: 7.0&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Type: Release Candidate&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Date: 16th September 2016&amp;lt;br /&amp;gt;&lt;br /&gt;
Distribution Types: Full Version Only&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Version&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Type&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Date&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;22nd July 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;5th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;25th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;RC 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;16th September 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;GA&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3rd October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;GA&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;14th October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download the latest version of WHMCS from http://download.whmcs.com/&lt;br /&gt;
&lt;br /&gt;
==Upgrade Process==&lt;br /&gt;
[[Upgrading|View Standard Upgrade Steps]]&lt;br /&gt;
&lt;br /&gt;
==Release Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-success&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; New PHP Version Requirements'''&amp;lt;br /&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''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 the latest Ioncube loader 6.0.2 or later.&lt;br /&gt;
 &lt;br /&gt;
* '''[[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.  [[Automatic Updater|Check our full article for more information and system requirements]].&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Action Required'''&amp;lt;br&amp;gt;We recommend updating your configured system cron (cron.php) to run every 5 minutes or as frequently as your web hosting provider allows. [[Cron_Tasks#System_Cron_Frequency|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-question-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Important Note'''&amp;lt;br&amp;gt;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:&lt;br /&gt;
*http://docs.whmcs.com/Additional_Domain_Fields&lt;br /&gt;
*http://docs.whmcs.com/WHOIS_Servers&lt;br /&gt;
*http://docs.whmcs.com/Customising_Countries_and_Calling_Codes&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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 [http://go.whmcs.com/918/duo-security-signup 10 free users offered by Duo].&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;For any existing users subscribing to DuoSecurity through us, we will be reaching out to you shortly regarding migrating your subscriptions. [[Duo_Security#WHMCS_DuoSecurity_Account_Migration|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''Deprecation of Five Theme''' - With the release of WHMCS 7.0, we will no longer be shipping the &amp;quot;Five&amp;quot; client area theme (previously named &amp;quot;default&amp;quot; in WHMCS V5.x).  Current installations of WHMCS will not have the &amp;quot;Five&amp;quot; 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 &amp;quot;Six&amp;quot; theme in order to take full advantage of the latest improvements and new functionality. Detailed information about the &amp;quot;Six&amp;quot; theme is available in our documentation at [[Customising the Six Theme]].&lt;br /&gt;
 &lt;br /&gt;
* '''[[Smarty Security Policy|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. [[Smarty Security Policy|Learn more at Public Documentation for End Users]].&lt;br /&gt;
&lt;br /&gt;
*'''[[Template_Syntax|Template Security Adjustments]]''' - Introduced in Version 7, if your template invokes &amp;amp; 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.&lt;br /&gt;
&lt;br /&gt;
* '''Removal of Browser Tool''' - Previous versions of WHMCS contained a tool named &amp;quot;Browser&amp;quot; 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&lt;br /&gt;
&lt;br /&gt;
* '''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 &amp;gt; Payment Gateways'' within your WHMCS installation.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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/.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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:&lt;br /&gt;
&lt;br /&gt;
==New Documentation Articles==&lt;br /&gt;
* [[Automatic Updater]]&lt;br /&gt;
* [[Smarty Security Policy]]&lt;br /&gt;
* [[Customising Countries and Calling Codes]]&lt;br /&gt;
* [[WHOIS Servers]]&lt;br /&gt;
* [[Additional Domain Fields]]&lt;br /&gt;
&lt;br /&gt;
===Dependency Updates===&lt;br /&gt;
&lt;br /&gt;
* '''Uninstalled'''&lt;br /&gt;
** guzzle/guzzle (v3.9.3)&lt;br /&gt;
** symfony/event-dispatcher (v2.8.11)&lt;br /&gt;
&lt;br /&gt;
* '''Installed'''&lt;br /&gt;
** composer/composer (1.0.3)&lt;br /&gt;
** composer/semver (1.4.2)&lt;br /&gt;
** composer/spdx-licenses (1.1.4)&lt;br /&gt;
** doctrine/inflector (v1.1.0)&lt;br /&gt;
** guzzlehttp/guzzle (5.0.3)&lt;br /&gt;
** guzzlehttp/ringphp (1.1.0)&lt;br /&gt;
** guzzlehttp/streams (3.0.0)&lt;br /&gt;
** illuminate/console (v5.2.37)&lt;br /&gt;
** illuminate/contracts (v5.2.45)&lt;br /&gt;
** justinrainbow/json-schema (1.6.1)&lt;br /&gt;
** mtdowling/cron-expression (v1.1.0)&lt;br /&gt;
** paragonie/random_compat (v1.4.1)&lt;br /&gt;
** react/promise (v2.4.1)&lt;br /&gt;
** symfony/console (v2.8.11)&lt;br /&gt;
** symfony/finder (v2.8.7)&lt;br /&gt;
** symfony/filesystem (v3.0.9)&lt;br /&gt;
** symfony/polyfill-php55 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-php54 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-mbstring (v1.2.0)&lt;br /&gt;
** symfony/process (v2.8.11)&lt;br /&gt;
** seld/jsonlint (1.4.1)&lt;br /&gt;
** seld/phar-utils (1.0.1)&lt;br /&gt;
&lt;br /&gt;
* '''Updated'''&lt;br /&gt;
** illuminate/support (v4.1.30) to illuminate/support (v5.2.37)&lt;br /&gt;
** illuminate/container (v4.1.30) to illuminate/container (v5.2.37)&lt;br /&gt;
** illuminate/database (v4.1.30) to illuminate/database (v5.2.37)&lt;br /&gt;
** illuminate/events (v4.1.30) to illuminate/events (v5.2.37)&lt;br /&gt;
** knplabs/knp-menu (v2.1.0) to knplabs/knp-menu (v2.1.1)&lt;br /&gt;
** league/climate (3.2.0) to league/climate (3.2.1)&lt;br /&gt;
** monolog/monolog (1.17.2) to monolog/monolog (1.18.2)&lt;br /&gt;
** nesbot/carbon (1.20.0) to nesbot/carbon (1.21.0)&lt;br /&gt;
** php-imap/php-imap (2.0.4) to php-imap/php-imap (2.0.6)&lt;br /&gt;
** phpmailer/phpmailer (v5.2.14) to phpmailer/phpmailer (v5.2.16)&lt;br /&gt;
** phpseclib/phpseclib (1.0.0) to phpseclib/phpseclib (2.0.2)&lt;br /&gt;
** rhumsaa/uuid (2.8.2) to ramsey/uuid (3.4.1)&lt;br /&gt;
** smarty/smarty (v3.1.21) to smarty/smarty (v3.1.29)&lt;br /&gt;
** symfony/http-foundation (v2.6.11) to symfony/http-foundation (v2.8.7)&lt;br /&gt;
** symfony/translation (v2.6.11) to symfony/translation (v2.8.7)&lt;br /&gt;
** symfony/yaml (v2.6.11) to symfony/yaml (v2.8.7)&lt;br /&gt;
&lt;br /&gt;
==Template Changes==&lt;br /&gt;
&lt;br /&gt;
=== Six Template ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.1 and 7.0.0-release.1.&lt;br /&gt;
https://github.com/WHMCS/templates-six/compare/v6.3.1-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
=== Standard Cart Order Form ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.0 and 7.0.0-release.1:&lt;br /&gt;
https://github.com/WHMCS/orderforms-standard_cart/compare/v6.3.0-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
==Changelog==&lt;br /&gt;
&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_1|Version 7.0.0 Beta 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_2|Version 7.0.0 Beta 2]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_3|Version 7.0.0 Beta 3]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_RC_1|Version 7.0.0 RC 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_GA|Version 7.0.0 GA]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Version_7.0.1_Release_Notes&amp;diff=20486</id>
		<title>Version 7.0.1 Release Notes</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Version_7.0.1_Release_Notes&amp;diff=20486"/>
				<updated>2016-10-14T14:24:54Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Created page with &amp;quot;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot; style=&amp;quot;max-width:370px;&amp;quot;&amp;gt; &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Release Information&amp;lt;/span&amp;gt; &amp;lt;br /&amp;gt; Version: 7.0.1&amp;lt;br /&amp;gt; Release Type: Release Candidate&amp;lt;br /&amp;gt; Release...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot; style=&amp;quot;max-width:370px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Release Information&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Version: 7.0.1&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Type: Release Candidate&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Date: 14th September 2016&amp;lt;br /&amp;gt;&lt;br /&gt;
Distribution Types: Full Version Only&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Version&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Type&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Date&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Release 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;14th October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download the latest version of WHMCS from http://download.whmcs.com/&lt;br /&gt;
&lt;br /&gt;
==Upgrade Process==&lt;br /&gt;
[[Upgrading|View Standard Upgrade Steps]]&lt;br /&gt;
&lt;br /&gt;
==Changelog==&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.1|Version 7.0.1]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.1&amp;diff=20482</id>
		<title>Changelog:WHMCS V7.0.1</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.1&amp;diff=20482"/>
				<updated>2016-10-14T14:19:24Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Created page with &amp;quot; &amp;lt;noinclude&amp;gt;Version X.X.X Release Notes&amp;lt;/noinclude&amp;gt;  == Maintenance == CORE-10479&amp;amp;nbsp;-&amp;amp;nbsp;Ensure email replies to support ticket notifications pipe properly in all sce...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Version X.X.X Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-10479&amp;amp;nbsp;-&amp;amp;nbsp;Ensure email replies to support ticket notifications pipe properly in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10483&amp;amp;nbsp;-&amp;amp;nbsp;Do not present domain order workflow if &amp;amp;quot;I will use my own domain&amp;amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10484&amp;amp;nbsp;-&amp;amp;nbsp;Improve handling of domain attributes when adding product to cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10489&amp;amp;nbsp;-&amp;amp;nbsp;Fix non-functional mass action buttons in admin client summary page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10491&amp;amp;nbsp;-&amp;amp;nbsp;Improve functionality of Client Area service list filters&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10502&amp;amp;nbsp;-&amp;amp;nbsp;Ensure one year term for &amp;amp;quot;free&amp;amp;quot; domains adding in cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10505&amp;amp;nbsp;-&amp;amp;nbsp;Remove unnecessary option &amp;amp;quot;Admin Force SSL Access&amp;amp;quot; in general settings&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10509&amp;amp;nbsp;-&amp;amp;nbsp;Correct query for ungrouped invoice line item aggregation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10510&amp;amp;nbsp;-&amp;amp;nbsp;Ensure consistent argument separator use across various environments&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6454&amp;amp;nbsp;-&amp;amp;nbsp;eWAY Tokens - Prevent spaces being sent in EWAY_CARDNUMBER - V6110&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10488&amp;amp;nbsp;-&amp;amp;nbsp;Improve WHM package name auto detection logic&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10499&amp;amp;nbsp;-&amp;amp;nbsp;Update Spanish DomainIsUnavailable language string&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.1_GA&amp;diff=20478</id>
		<title>Changelog:WHMCS V7.0.1 GA</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.1_GA&amp;diff=20478"/>
				<updated>2016-10-14T13:53:07Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Created page with &amp;quot;&amp;lt;noinclude&amp;gt;Version X.X.X Release Notes&amp;lt;/noinclude&amp;gt;  == Maintenance == CORE-10479&amp;amp;nbsp;-&amp;amp;nbsp;Ensure email replies to support ticket notifications pipe properly in all scen...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version X.X.X Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-10479&amp;amp;nbsp;-&amp;amp;nbsp;Ensure email replies to support ticket notifications pipe properly in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10483&amp;amp;nbsp;-&amp;amp;nbsp;Ensure customers can properly skip domain registration if &amp;amp;quot;I will use my own domain&amp;amp;quot; is selected&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10484&amp;amp;nbsp;-&amp;amp;nbsp;Resolve bug in passing a domain into the shopping cart product add to cart routine&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10489&amp;amp;nbsp;-&amp;amp;nbsp;Fix non-functional mass action buttons in admin client summary page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10491&amp;amp;nbsp;-&amp;amp;nbsp;Improve functionality of Client Area service list filters&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10502&amp;amp;nbsp;-&amp;amp;nbsp;Ensure free domains adding in cart are set to one year only&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10505&amp;amp;nbsp;-&amp;amp;nbsp;Remove Admin Force SSL Access option under general settings&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10509&amp;amp;nbsp;-&amp;amp;nbsp;Correct query for ungrouped invoice line item aggregation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10510&amp;amp;nbsp;-&amp;amp;nbsp;Ensure consistent argument separator use across various PHP environments and configurations&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6454&amp;amp;nbsp;-&amp;amp;nbsp;eWAY Tokens - Prevent spaces being sent in EWAY_CARDNUMBER - V6110&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
CORE-10488&amp;amp;nbsp;-&amp;amp;nbsp;Improve logic for auto detecting appropriate WHM package names&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10499&amp;amp;nbsp;-&amp;amp;nbsp;Update Spanish DomainIsUnavailable language string&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20426</id>
		<title>Version 7.0 Release Notes</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20426"/>
				<updated>2016-10-05T15:43:39Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot; style=&amp;quot;max-width:370px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Release Information&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Version: 7.0&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Type: Release Candidate&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Date: 16th September 2016&amp;lt;br /&amp;gt;&lt;br /&gt;
Distribution Types: Full Version Only&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Version&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Type&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Date&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;22nd July 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;5th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;25th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;RC 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;16th September 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;GA&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3rd October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download the latest version of WHMCS from http://download.whmcs.com/&lt;br /&gt;
&lt;br /&gt;
==Upgrade Process==&lt;br /&gt;
[[Upgrading|View Standard Upgrade Steps]]&lt;br /&gt;
&lt;br /&gt;
==Release Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-success&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; New PHP Version Requirements'''&amp;lt;br /&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''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 the latest Ioncube loader 6.0.2 or later.&lt;br /&gt;
 &lt;br /&gt;
* '''[[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.  [[Automatic Updater|Check our full article for more information and system requirements]].&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Action Required'''&amp;lt;br&amp;gt;We recommend updating your configured system cron (cron.php) to run every 5 minutes or as frequently as your web hosting provider allows. [[Cron_Tasks#System_Cron_Frequency|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-question-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Important Note'''&amp;lt;br&amp;gt;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:&lt;br /&gt;
*http://docs.whmcs.com/Additional_Domain_Fields&lt;br /&gt;
*http://docs.whmcs.com/WHOIS_Servers&lt;br /&gt;
*http://docs.whmcs.com/Customising_Countries_and_Calling_Codes&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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 [http://go.whmcs.com/918/duo-security-signup 10 free users offered by Duo].&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;For any existing users subscribing to DuoSecurity through us, we will be reaching out to you shortly regarding migrating your subscriptions. [[Duo_Security#WHMCS_DuoSecurity_Account_Migration|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''Deprecation of Five Theme''' - With the release of WHMCS 7.0, we will no longer be shipping the &amp;quot;Five&amp;quot; client area theme (previously named &amp;quot;default&amp;quot; in WHMCS V5.x).  Current installations of WHMCS will not have the &amp;quot;Five&amp;quot; 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 &amp;quot;Six&amp;quot; theme in order to take full advantage of the latest improvements and new functionality. Detailed information about the &amp;quot;Six&amp;quot; theme is available in our documentation at [[Customising the Six Theme]].&lt;br /&gt;
 &lt;br /&gt;
* '''[[Smarty Security Policy|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. [[Smarty Security Policy|Learn more at Public Documentation for End Users]].&lt;br /&gt;
&lt;br /&gt;
*'''[[Template_Syntax|Template Security Adjustments]]''' - Introduced in Version 7, if your template invokes &amp;amp; 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.&lt;br /&gt;
&lt;br /&gt;
* '''Removal of Browser Tool''' - Previous versions of WHMCS contained a tool named &amp;quot;Browser&amp;quot; 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&lt;br /&gt;
&lt;br /&gt;
* '''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 &amp;gt; Payment Gateways'' within your WHMCS installation.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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/.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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:&lt;br /&gt;
&lt;br /&gt;
==New Documentation Articles==&lt;br /&gt;
* [[Automatic Updater]]&lt;br /&gt;
* [[Smarty Security Policy]]&lt;br /&gt;
* [[Customising Countries and Calling Codes]]&lt;br /&gt;
* [[WHOIS Servers]]&lt;br /&gt;
* [[Additional Domain Fields]]&lt;br /&gt;
&lt;br /&gt;
===Dependency Updates===&lt;br /&gt;
&lt;br /&gt;
* '''Uninstalled'''&lt;br /&gt;
** guzzle/guzzle (v3.9.3)&lt;br /&gt;
** symfony/event-dispatcher (v2.8.11)&lt;br /&gt;
&lt;br /&gt;
* '''Installed'''&lt;br /&gt;
** composer/composer (1.0.3)&lt;br /&gt;
** composer/semver (1.4.2)&lt;br /&gt;
** composer/spdx-licenses (1.1.4)&lt;br /&gt;
** doctrine/inflector (v1.1.0)&lt;br /&gt;
** guzzlehttp/guzzle (5.0.3)&lt;br /&gt;
** guzzlehttp/ringphp (1.1.0)&lt;br /&gt;
** guzzlehttp/streams (3.0.0)&lt;br /&gt;
** illuminate/console (v5.2.37)&lt;br /&gt;
** illuminate/contracts (v5.2.45)&lt;br /&gt;
** justinrainbow/json-schema (1.6.1)&lt;br /&gt;
** mtdowling/cron-expression (v1.1.0)&lt;br /&gt;
** paragonie/random_compat (v1.4.1)&lt;br /&gt;
** react/promise (v2.4.1)&lt;br /&gt;
** symfony/console (v2.8.11)&lt;br /&gt;
** symfony/finder (v2.8.7)&lt;br /&gt;
** symfony/filesystem (v3.0.9)&lt;br /&gt;
** symfony/polyfill-php55 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-php54 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-mbstring (v1.2.0)&lt;br /&gt;
** symfony/process (v2.8.11)&lt;br /&gt;
** seld/jsonlint (1.4.1)&lt;br /&gt;
** seld/phar-utils (1.0.1)&lt;br /&gt;
&lt;br /&gt;
* '''Updated'''&lt;br /&gt;
** illuminate/support (v4.1.30) to illuminate/support (v5.2.37)&lt;br /&gt;
** illuminate/container (v4.1.30) to illuminate/container (v5.2.37)&lt;br /&gt;
** illuminate/database (v4.1.30) to illuminate/database (v5.2.37)&lt;br /&gt;
** illuminate/events (v4.1.30) to illuminate/events (v5.2.37)&lt;br /&gt;
** knplabs/knp-menu (v2.1.0) to knplabs/knp-menu (v2.1.1)&lt;br /&gt;
** league/climate (3.2.0) to league/climate (3.2.1)&lt;br /&gt;
** monolog/monolog (1.17.2) to monolog/monolog (1.18.2)&lt;br /&gt;
** nesbot/carbon (1.20.0) to nesbot/carbon (1.21.0)&lt;br /&gt;
** php-imap/php-imap (2.0.4) to php-imap/php-imap (2.0.6)&lt;br /&gt;
** phpmailer/phpmailer (v5.2.14) to phpmailer/phpmailer (v5.2.16)&lt;br /&gt;
** phpseclib/phpseclib (1.0.0) to phpseclib/phpseclib (2.0.2)&lt;br /&gt;
** rhumsaa/uuid (2.8.2) to ramsey/uuid (3.4.1)&lt;br /&gt;
** smarty/smarty (v3.1.21) to smarty/smarty (v3.1.29)&lt;br /&gt;
** symfony/http-foundation (v2.6.11) to symfony/http-foundation (v2.8.7)&lt;br /&gt;
** symfony/translation (v2.6.11) to symfony/translation (v2.8.7)&lt;br /&gt;
** symfony/yaml (v2.6.11) to symfony/yaml (v2.8.7)&lt;br /&gt;
&lt;br /&gt;
==Template Changes==&lt;br /&gt;
&lt;br /&gt;
=== Six Template ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.1 and 7.0.0-release.1.&lt;br /&gt;
https://github.com/WHMCS/templates-six/compare/v6.3.1-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
=== Standard Cart Order Form ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.0 and 7.0.0-release.1:&lt;br /&gt;
https://github.com/WHMCS/orderforms-standard_cart/compare/v6.3.0-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
==Changelog==&lt;br /&gt;
&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_1|Version 7.0.0 Beta 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_2|Version 7.0.0 Beta 2]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_3|Version 7.0.0 Beta 3]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_RC_1|Version 7.0.0 RC 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_GA|Version 7.0.0 GA]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Smarty_Security_Policy&amp;diff=20422</id>
		<title>Smarty Security Policy</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Smarty_Security_Policy&amp;diff=20422"/>
				<updated>2016-10-05T15:36:46Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;&amp;lt;i class=&amp;quot;fa fa-question-circle&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; This page describes a feature available in version 7.0 and above&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
WHMCS 7.0 introduces a new security hardening measure called Smarty Security Policies. WHMCS utilizes a system policy for system wide use, and a mail policy specifically for stored and dynamic email based templates.&lt;br /&gt;
&lt;br /&gt;
The settings enforced by a WHMCS Smarty Security Policy are the same as those defined by the Smarty library itself. You can learn more about about these settings from the Smarty documentation: http://www.smarty.net/docs/en/advanced.features.tpl&lt;br /&gt;
&lt;br /&gt;
By default, WHMCS does not define any PHP functionality restrictions for the system policy (except to honor the pre-existing {php} tag setting as configured in Setup &amp;gt;&amp;gt; Security).  All templates that use this policy are file based (for example, themes and order forms) which require file level access and therefore are automatically implicitly trusted.  Because custom themes are much more likely to have additional PHP oriented logic, any restrictions defined by WHMCS could result in website rendering issues. It is completely within your discretion to determine if implicit trust at the file level is invalid and you may make any appropriate restrictions for this system policy.&lt;br /&gt;
&lt;br /&gt;
The mail policy restricts what PHP functionality can be used in email based templates. The default mail policy will limit the use of variable modifiers (http://www.smarty.net/docs/en/language.modifiers.tpl) to the following: &lt;br /&gt;
&lt;br /&gt;
*escape&lt;br /&gt;
*count&lt;br /&gt;
*urlencode&lt;br /&gt;
*ucfirst&lt;br /&gt;
*date_format&lt;br /&gt;
&lt;br /&gt;
The default mail policy restricts the use of native PHP functions to the following:&lt;br /&gt;
&lt;br /&gt;
*isset&lt;br /&gt;
*empty&lt;br /&gt;
*count&lt;br /&gt;
*sizeof&lt;br /&gt;
*in_array&lt;br /&gt;
*is_array&lt;br /&gt;
*time&lt;br /&gt;
*nl2br&lt;br /&gt;
&lt;br /&gt;
Finally, the default mail policy blocks these smarty tags:&lt;br /&gt;
&lt;br /&gt;
* block&lt;br /&gt;
* function&lt;br /&gt;
* include&lt;br /&gt;
&lt;br /&gt;
The default mail policy will not allow for the inclusion of any calls to static classes, fetching any data from php streams, or accessing any super global variables. &lt;br /&gt;
&lt;br /&gt;
If you want to redefine either the system or mail policy, you can do this by adding a $smarty_security_policy setting to your configuration.php. Here's an example that limits email templates (by modifying the mail policy) to 'ucwords' as the only native PHP function allowed, while not changing the default restrictions on variable modifiers:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;php&amp;quot;&amp;gt;&lt;br /&gt;
// Smarty custom email based template policy:&lt;br /&gt;
$smarty_security_policy =&amp;gt; array(&lt;br /&gt;
    'mail' =&amp;gt; array(&lt;br /&gt;
        'php_functions' =&amp;gt; array(&lt;br /&gt;
            'ucwords',&lt;br /&gt;
        ),&lt;br /&gt;
    ),&lt;br /&gt;
);&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Using {include_php} Syntax===&lt;br /&gt;
&lt;br /&gt;
Smarty has deprecated the {include_php} syntax, but WHMCS currently supports this behavior via Policies.  If your template invokes &amp;amp; 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;php&amp;quot;&amp;gt;&lt;br /&gt;
// Smarty custom email based template policy:&lt;br /&gt;
$smarty_security_policy =&amp;gt; array(&lt;br /&gt;
    'system' =&amp;gt; array(&lt;br /&gt;
        'trusted_dir' =&amp;gt; array(&lt;br /&gt;
            '/path/to/folder',&lt;br /&gt;
        ),&lt;br /&gt;
    ),&lt;br /&gt;
);&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Please refer to the [http://www.smarty.net/docs/en/advanced.features.tpl#advanced.features.security/ Smarty documentation] for all possible settings and what behavior to expect when assigning array and boolean values.&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Template_Syntax&amp;diff=20418</id>
		<title>Template Syntax</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Template_Syntax&amp;diff=20418"/>
				<updated>2016-10-05T15:33:19Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The basic template syntax can be seen by looking at the templates. Template files use regular HTML along with tags for where the WHMCS data is inserted into them. All pages have specific variables which you can use. A complete list of variables on a page is available by entering the following tag into the template:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;&amp;lt;center&amp;gt;'''{debug}'''&amp;lt;/center&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The next access to the page using that template file after adding this code will show a popup window. This window will show all the different variables which you can use on the page. Access variables using the {$variable} syntax.&lt;br /&gt;
&lt;br /&gt;
==Common Template Variables Available on All Pages==&lt;br /&gt;
&lt;br /&gt;
The following is a list of template variables available for use in all the template files of WHMCS:&lt;br /&gt;
&lt;br /&gt;
*{$BASE_PATH_CSS} - The base URL to common CSS assets.&lt;br /&gt;
*{$BASE_PATH_FONTS} - The base URL to common font assets.&lt;br /&gt;
*{$BASE_PATH_IMG} - The base URL to common image assets.&lt;br /&gt;
*{$BASE_PATH_JS} - The base URL to common Javascript assets.&lt;br /&gt;
*{$charset} - The configured character set.&lt;br /&gt;
*{$client} - The currently logged in [http://docs.whmcs.com/classes/classes/WHMCS.User.Client.html Client], or ''null'' if a client is not logged in.&lt;br /&gt;
*{$companyname} - The configured company name&lt;br /&gt;
*{$date_day} - The current calendar day.&lt;br /&gt;
*{$date_month} - The current calendar month.&lt;br /&gt;
*{$date_year} - The current calendar year.&lt;br /&gt;
*{filename} - The basename of the current file requested by the web browser.&lt;br /&gt;
*{$language} - The name of the language to display to the user.&lt;br /&gt;
*{$loggedin} - ''true'' or ''false'' depending on if a client is logged in.&lt;br /&gt;
*{$logo} - The path to the configured logo image. &lt;br /&gt;
*{$pagetitle} - The current page's title.&lt;br /&gt;
*{$reCaptchaPublicKey} - The configured [https://www.google.com/recaptcha/intro/index.html reCAPTCHA] site key. This can be an empty string if the WHMCS installation does not use Google reCAPTCHA.&lt;br /&gt;
*{$systemNonSSLURL} - The configured non-SSL URL.&lt;br /&gt;
*{$systemsslurl} - The configured SSL URL.&lt;br /&gt;
*{$systemurl} - The URL to the WHMCS system. Either the SSL or non-SSL URL depending on whether the current page loaded via HTTPS.&lt;br /&gt;
*{$template} - The name of the template used for display.&lt;br /&gt;
*{$todaysdate} - The current date, presented in &amp;quot;l, jS F Y&amp;quot; format.&lt;br /&gt;
*{$token} - A [https://en.wikipedia.org/wiki/Cross-site_request_forgery CSRF] token to use on POST forms.&lt;br /&gt;
*{$WEB_ROOT} - Your WHMCS system's base URL.&lt;br /&gt;
&lt;br /&gt;
===Custom Template Variables===&lt;br /&gt;
The template parameters available in templates will vary depending upon the page/object being requested.&lt;br /&gt;
&lt;br /&gt;
Should you require additional content or variables that are not defined by default, you can add to them using hooks.  The following hooks are available for these purposes:&lt;br /&gt;
&lt;br /&gt;
* Client Area: ''[[Hooks:ClientAreaPage]]''&lt;br /&gt;
* Admin Area: ''[[Hooks:AdminAreaPage]]''&lt;br /&gt;
* Email Messages: ''[[Hooks:EmailPreSend]]''&lt;br /&gt;
&lt;br /&gt;
==Displaying Text to Logged In Users Only==&lt;br /&gt;
&lt;br /&gt;
To display something on the page only if a user is logged in, use the following syntax:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;smarty&amp;quot;&amp;gt;&lt;br /&gt;
{if $loggedin}&lt;br /&gt;
    &amp;lt;p&amp;gt;User is logged in so display client only information&amp;lt;/p&amp;gt;&lt;br /&gt;
{else}&lt;br /&gt;
    &amp;lt;p&amp;gt;User is not logged in so display this&amp;lt;/p&amp;gt;&lt;br /&gt;
{/if}&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Displaying Text if Certain Conditions Are Met==&lt;br /&gt;
&lt;br /&gt;
It can often be necessary to display text or messages when certain conditions are met. For example, you might want to add extra text output when iterating through products. (Or, payment gateways, or display card scheme logos associated with your merchant account, etc.). Achieve this by using the if statement syntax:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;smarty&amp;quot;&amp;gt;{if $gateway.name eq &amp;quot;PayPal&amp;quot;}We accept PayPal{/if}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This example would display the message &amp;quot;We accept PayPal&amp;quot; if that option is available on the checkout page. This can be used for any variable.&lt;br /&gt;
&lt;br /&gt;
==Translating Language Strings==&lt;br /&gt;
&lt;br /&gt;
WHMCS provides the {lang} function for templates to present text in the user's language. Call it with the &amp;quot;key&amp;quot; parameter representing the key in the language to translate.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;smarty&amp;quot;&amp;gt;&lt;br /&gt;
{** &lt;br /&gt;
 * Defined as $_LANG['forgotpw'] in language files:&lt;br /&gt;
 *&lt;br /&gt;
 * Display &amp;quot;&amp;lt;strong&amp;gt;Forgot Password?&amp;lt;/strong&amp;gt;&amp;quot; in English&lt;br /&gt;
 * or &amp;quot;&amp;lt;strong&amp;gt;¿Perdiste la contraseña?&amp;lt;/strong&amp;gt;&amp;quot; in Spanish.&lt;br /&gt;
 *}&lt;br /&gt;
&amp;lt;strong&amp;gt;{lang key=&amp;quot;forgotpw&amp;quot;}&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Use dots (&amp;quot;.&amp;quot;) to concatenate nested language keys. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;smarty&amp;quot;&amp;gt;&lt;br /&gt;
{** &lt;br /&gt;
 * Defined as $_LANG['clientHomePanels']['unpaidInvoices'] in language files:&lt;br /&gt;
 *&lt;br /&gt;
 * Display &amp;quot;&amp;lt;strong&amp;gt;Unpaid Invoices&amp;lt;/strong&amp;gt;&amp;quot; in English&lt;br /&gt;
 * or &amp;quot;&amp;lt;strong&amp;gt;Facturas Pendientes&amp;lt;/strong&amp;gt;&amp;quot; in Spanish.&lt;br /&gt;
 *}&lt;br /&gt;
&amp;lt;strong&amp;gt;{lang key=&amp;quot;clientHomePanels.unpaidInvoices&amp;quot;}&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some language strings contain variable substitution. Variables for substitution begin with a colon (&amp;quot;:&amp;quot;). Declare those variables and their values as parameters to the '''{lang}''' function:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;smarty&amp;quot;&amp;gt;&lt;br /&gt;
{**&lt;br /&gt;
 * Defined as $_LANG['clientHomePanels']['creditBalance'] in language files:&lt;br /&gt;
 *&lt;br /&gt;
 * Display &amp;quot;&amp;lt;p&amp;gt;You have a credit balance of $100.00.&amp;lt;/p&amp;gt;&amp;quot; in English&lt;br /&gt;
 * or &amp;quot;&amp;lt;p&amp;gt;Usted tiene un saldo acreedor de $100.00.&amp;lt;/p&amp;gt;&amp;quot; in Spanish.&lt;br /&gt;
 *}&lt;br /&gt;
&amp;lt;p&amp;gt;{lang key=&amp;quot;clientHomePanels.creditBalance&amp;quot; creditBalance=&amp;quot;$100&amp;quot;}&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Using {include_php} Syntax==&lt;br /&gt;
If your template invokes &amp;amp; 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. &lt;br /&gt;
&lt;br /&gt;
For more information please refer to [[Smarty Security Policy|Smarty Security Policy]] section.&lt;br /&gt;
&lt;br /&gt;
==More Information==&lt;br /&gt;
&lt;br /&gt;
For further documentation on template customisations, see the official Smarty 3 documentation @ http://www.smarty.net/docs/en/&lt;br /&gt;
&lt;br /&gt;
{{Developer_Links}}&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Smarty_Security_Policy&amp;diff=20410</id>
		<title>Smarty Security Policy</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Smarty_Security_Policy&amp;diff=20410"/>
				<updated>2016-10-04T19:01:25Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;&amp;lt;i class=&amp;quot;fa fa-question-circle&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; This page describes a feature available in version 7.0 and above&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
WHMCS 7.0 introduces a new security hardening measure called Smarty Security Policies. WHMCS utilizes a system policy for system wide use, and a mail policy specifically for stored and dynamic email based templates.&lt;br /&gt;
&lt;br /&gt;
The settings enforced by a WHMCS Smarty Security Policy are the same as those defined by the Smarty library itself. You can learn more about about these settings from the Smarty documentation: http://www.smarty.net/docs/en/advanced.features.tpl&lt;br /&gt;
&lt;br /&gt;
By default, WHMCS does not define any PHP functionality restrictions for the system policy (except to honor the pre-existing {php} tag setting as configured in Setup &amp;gt;&amp;gt; Security).  All templates that use this policy are file based (for example, themes and order forms) which require file level access and therefore are automatically implicitly trusted.  Because custom themes are much more likely to have additional PHP oriented logic, any restrictions defined by WHMCS could result in website rendering issues. It is completely within your discretion to determine if implicit trust at the file level is invalid and you may make any appropriate restrictions for this system policy.&lt;br /&gt;
&lt;br /&gt;
The mail policy restricts what PHP functionality can be used in email based templates. The default mail policy will limit the use of variable modifiers (http://www.smarty.net/docs/en/language.modifiers.tpl) to the following: &lt;br /&gt;
&lt;br /&gt;
*escape&lt;br /&gt;
*count&lt;br /&gt;
*urlencode&lt;br /&gt;
*ucfirst&lt;br /&gt;
*date_format&lt;br /&gt;
&lt;br /&gt;
The default mail policy restricts the use of native PHP functions to the following:&lt;br /&gt;
&lt;br /&gt;
*isset&lt;br /&gt;
*empty&lt;br /&gt;
*count&lt;br /&gt;
*sizeof&lt;br /&gt;
*in_array&lt;br /&gt;
*is_array&lt;br /&gt;
*time&lt;br /&gt;
*nl2br&lt;br /&gt;
&lt;br /&gt;
Finally, the default mail policy blocks these smarty tags:&lt;br /&gt;
&lt;br /&gt;
* block&lt;br /&gt;
* function&lt;br /&gt;
* include&lt;br /&gt;
&lt;br /&gt;
The default mail policy will not allow for the inclusion of any calls to static classes, fetching any data from php streams, or accessing any super global variables. &lt;br /&gt;
&lt;br /&gt;
If you want to redefine either the system or mail policy, you can do this by adding a $smarty_security_policy setting to your configuration.php. Here's an example that limits email templates (by modifying the mail policy) to 'ucwords' as the only native PHP function allowed, while not changing the default restrictions on variable modifiers:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;php&amp;quot;&amp;gt;&lt;br /&gt;
// Smarty custom email based template policy:&lt;br /&gt;
$smarty_security_policy =&amp;gt; array(&lt;br /&gt;
    'mail' =&amp;gt; array(&lt;br /&gt;
        'php_functions' =&amp;gt; array(&lt;br /&gt;
            'ucwords',&lt;br /&gt;
        ),&lt;br /&gt;
    ),&lt;br /&gt;
);&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Smarty has deprecated the {include_php} syntax, but WHMCS currently supports this behavior via Policies.  If your template invokes &amp;amp; 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.&lt;br /&gt;
&lt;br /&gt;
Please refer to the [http://www.smarty.net/docs/en/advanced.features.tpl#advanced.features.security/ Smarty documentation] for all possible settings and what behavior to expect when assigning array and boolean values.&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20398</id>
		<title>Version 7.0 Release Notes</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20398"/>
				<updated>2016-10-03T19:42:55Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Version History */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot; style=&amp;quot;max-width:370px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Release Information&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Version: 7.0&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Type: Release Candidate&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Date: 16th September 2016&amp;lt;br /&amp;gt;&lt;br /&gt;
Distribution Types: Full Version Only&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Version&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Type&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Date&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;22nd July 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;5th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;25th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;RC 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;16th September 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;GA&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3rd October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download the latest version of WHMCS from http://download.whmcs.com/&lt;br /&gt;
&lt;br /&gt;
==Upgrade Process==&lt;br /&gt;
[[Upgrading|View Standard Upgrade Steps]]&lt;br /&gt;
&lt;br /&gt;
==Release Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-success&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; New PHP Version Requirements'''&amp;lt;br /&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''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 the latest Ioncube loader 6.0.2 or later.&lt;br /&gt;
 &lt;br /&gt;
* '''[[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.  [[Automatic Updater|Check our full article for more information and system requirements]].&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Action Required'''&amp;lt;br&amp;gt;We recommend updating your configured system cron (cron.php) to run every 5 minutes or as frequently as your web hosting provider allows. [[Cron_Tasks#System_Cron_Frequency|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-question-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Important Note'''&amp;lt;br&amp;gt;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:&lt;br /&gt;
*http://docs.whmcs.com/Additional_Domain_Fields&lt;br /&gt;
*http://docs.whmcs.com/WHOIS_Servers&lt;br /&gt;
*http://docs.whmcs.com/Customising_Countries_and_Calling_Codes&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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 [http://go.whmcs.com/918/duo-security-signup 10 free users offered by Duo].&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;For any existing users subscribing to DuoSecurity through us, we will be reaching out to you shortly regarding migrating your subscriptions. [[Duo_Security#WHMCS_DuoSecurity_Account_Migration|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''Deprecation of Five Theme''' - With the release of WHMCS 7.0, we will no longer be shipping the &amp;quot;Five&amp;quot; client area theme (previously named &amp;quot;default&amp;quot; in WHMCS V5.x).  Current installations of WHMCS will not have the &amp;quot;Five&amp;quot; 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 &amp;quot;Six&amp;quot; theme in order to take full advantage of the latest improvements and new functionality. Detailed information about the &amp;quot;Six&amp;quot; theme is available in our documentation at [[Customising the Six Theme]].&lt;br /&gt;
 &lt;br /&gt;
* '''[[Smarty Security Policy|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. [[Smarty Security Policy|Learn more at Public Documentation for End Users]].&lt;br /&gt;
&lt;br /&gt;
* '''Removal of Browser Tool''' - Previous versions of WHMCS contained a tool named &amp;quot;Browser&amp;quot; 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&lt;br /&gt;
&lt;br /&gt;
* '''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 &amp;gt; Payment Gateways'' within your WHMCS installation.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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/.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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:&lt;br /&gt;
&lt;br /&gt;
==New Documentation Articles==&lt;br /&gt;
* [[Automatic Updater]]&lt;br /&gt;
* [[Smarty Security Policy]]&lt;br /&gt;
* [[Customising Countries and Calling Codes]]&lt;br /&gt;
* [[WHOIS Servers]]&lt;br /&gt;
* [[Additional Domain Fields]]&lt;br /&gt;
&lt;br /&gt;
===Dependency Updates===&lt;br /&gt;
&lt;br /&gt;
* '''Uninstalled'''&lt;br /&gt;
** guzzle/guzzle (v3.9.3)&lt;br /&gt;
** symfony/event-dispatcher (v2.8.11)&lt;br /&gt;
&lt;br /&gt;
* '''Installed'''&lt;br /&gt;
** composer/composer (1.0.3)&lt;br /&gt;
** composer/semver (1.4.2)&lt;br /&gt;
** composer/spdx-licenses (1.1.4)&lt;br /&gt;
** doctrine/inflector (v1.1.0)&lt;br /&gt;
** guzzlehttp/guzzle (5.0.3)&lt;br /&gt;
** guzzlehttp/ringphp (1.1.0)&lt;br /&gt;
** guzzlehttp/streams (3.0.0)&lt;br /&gt;
** illuminate/console (v5.2.37)&lt;br /&gt;
** illuminate/contracts (v5.2.45)&lt;br /&gt;
** justinrainbow/json-schema (1.6.1)&lt;br /&gt;
** mtdowling/cron-expression (v1.1.0)&lt;br /&gt;
** paragonie/random_compat (v1.4.1)&lt;br /&gt;
** react/promise (v2.4.1)&lt;br /&gt;
** symfony/console (v2.8.11)&lt;br /&gt;
** symfony/finder (v2.8.7)&lt;br /&gt;
** symfony/filesystem (v3.0.9)&lt;br /&gt;
** symfony/polyfill-php55 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-php54 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-mbstring (v1.2.0)&lt;br /&gt;
** symfony/process (v2.8.11)&lt;br /&gt;
** seld/jsonlint (1.4.1)&lt;br /&gt;
** seld/phar-utils (1.0.1)&lt;br /&gt;
&lt;br /&gt;
* '''Updated'''&lt;br /&gt;
** illuminate/support (v4.1.30) to illuminate/support (v5.2.37)&lt;br /&gt;
** illuminate/container (v4.1.30) to illuminate/container (v5.2.37)&lt;br /&gt;
** illuminate/database (v4.1.30) to illuminate/database (v5.2.37)&lt;br /&gt;
** illuminate/events (v4.1.30) to illuminate/events (v5.2.37)&lt;br /&gt;
** knplabs/knp-menu (v2.1.0) to knplabs/knp-menu (v2.1.1)&lt;br /&gt;
** league/climate (3.2.0) to league/climate (3.2.1)&lt;br /&gt;
** monolog/monolog (1.17.2) to monolog/monolog (1.18.2)&lt;br /&gt;
** nesbot/carbon (1.20.0) to nesbot/carbon (1.21.0)&lt;br /&gt;
** php-imap/php-imap (2.0.4) to php-imap/php-imap (2.0.6)&lt;br /&gt;
** phpmailer/phpmailer (v5.2.14) to phpmailer/phpmailer (v5.2.16)&lt;br /&gt;
** phpseclib/phpseclib (1.0.0) to phpseclib/phpseclib (2.0.2)&lt;br /&gt;
** rhumsaa/uuid (2.8.2) to ramsey/uuid (3.4.1)&lt;br /&gt;
** smarty/smarty (v3.1.21) to smarty/smarty (v3.1.29)&lt;br /&gt;
** symfony/http-foundation (v2.6.11) to symfony/http-foundation (v2.8.7)&lt;br /&gt;
** symfony/translation (v2.6.11) to symfony/translation (v2.8.7)&lt;br /&gt;
** symfony/yaml (v2.6.11) to symfony/yaml (v2.8.7)&lt;br /&gt;
&lt;br /&gt;
==Template Changes==&lt;br /&gt;
&lt;br /&gt;
=== Six Template ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.1 and 7.0.0-release.1.&lt;br /&gt;
https://github.com/WHMCS/templates-six/compare/v6.3.1-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
=== Standard Cart Order Form ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.0 and 7.0.0-release.1:&lt;br /&gt;
https://github.com/WHMCS/orderforms-standard_cart/compare/v6.3.0-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
==Changelog==&lt;br /&gt;
&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_1|Version 7.0.0 Beta 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_2|Version 7.0.0 Beta 2]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_3|Version 7.0.0 Beta 3]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_RC_1|Version 7.0.0 RC 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_GA|Version 7.0.0 GA]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20390</id>
		<title>Version 7.0 Release Notes</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Version_7.0_Release_Notes&amp;diff=20390"/>
				<updated>2016-10-03T16:15:53Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Template Changes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot; style=&amp;quot;max-width:370px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Release Information&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Version: 7.0&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Type: Release Candidate&amp;lt;br /&amp;gt;&lt;br /&gt;
Release Date: 16th September 2016&amp;lt;br /&amp;gt;&lt;br /&gt;
Distribution Types: Full Version Only&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Version&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Type&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Release Date&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;22nd July 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;5th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Beta 3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;25th August 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;RC 1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;16th September 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;7.0.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;GA&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xx October 2016&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download the latest version of WHMCS from http://download.whmcs.com/&lt;br /&gt;
&lt;br /&gt;
==Upgrade Process==&lt;br /&gt;
[[Upgrading|View Standard Upgrade Steps]]&lt;br /&gt;
&lt;br /&gt;
==Release Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-success&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; New PHP Version Requirements'''&amp;lt;br /&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''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 the latest Ioncube loader 6.0.2 or later.&lt;br /&gt;
 &lt;br /&gt;
* '''[[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.  [[Automatic Updater|Check our full article for more information and system requirements]].&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-warning fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Action Required'''&amp;lt;br&amp;gt;We recommend updating your configured system cron (cron.php) to run every 5 minutes or as frequently as your web hosting provider allows. [[Cron_Tasks#System_Cron_Frequency|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-question-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Important Note'''&amp;lt;br&amp;gt;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:&lt;br /&gt;
*http://docs.whmcs.com/Additional_Domain_Fields&lt;br /&gt;
*http://docs.whmcs.com/WHOIS_Servers&lt;br /&gt;
*http://docs.whmcs.com/Customising_Countries_and_Calling_Codes&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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 [http://go.whmcs.com/918/duo-security-signup 10 free users offered by Duo].&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-warning&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;For any existing users subscribing to DuoSecurity through us, we will be reaching out to you shortly regarding migrating your subscriptions. [[Duo_Security#WHMCS_DuoSecurity_Account_Migration|Learn more…]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
 &lt;br /&gt;
* '''Deprecation of Five Theme''' - With the release of WHMCS 7.0, we will no longer be shipping the &amp;quot;Five&amp;quot; client area theme (previously named &amp;quot;default&amp;quot; in WHMCS V5.x).  Current installations of WHMCS will not have the &amp;quot;Five&amp;quot; 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 &amp;quot;Six&amp;quot; theme in order to take full advantage of the latest improvements and new functionality. Detailed information about the &amp;quot;Six&amp;quot; theme is available in our documentation at [[Customising the Six Theme]].&lt;br /&gt;
 &lt;br /&gt;
* '''[[Smarty Security Policy|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. [[Smarty Security Policy|Learn more at Public Documentation for End Users]].&lt;br /&gt;
&lt;br /&gt;
* '''Removal of Browser Tool''' - Previous versions of WHMCS contained a tool named &amp;quot;Browser&amp;quot; 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&lt;br /&gt;
&lt;br /&gt;
* '''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 &amp;gt; Payment Gateways'' within your WHMCS installation.&lt;br /&gt;
 &lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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/.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-alert-info&amp;quot;&amp;gt;'''&amp;lt;i class=&amp;quot;fa fa-info-circle fa-fw&amp;quot;&amp;gt;&amp;lt;/i&amp;gt; Information'''&amp;lt;br&amp;gt;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.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* '''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:&lt;br /&gt;
&lt;br /&gt;
==New Documentation Articles==&lt;br /&gt;
* [[Automatic Updater]]&lt;br /&gt;
* [[Smarty Security Policy]]&lt;br /&gt;
* [[Customising Countries and Calling Codes]]&lt;br /&gt;
* [[WHOIS Servers]]&lt;br /&gt;
* [[Additional Domain Fields]]&lt;br /&gt;
&lt;br /&gt;
===Dependency Updates===&lt;br /&gt;
&lt;br /&gt;
* '''Uninstalled'''&lt;br /&gt;
** guzzle/guzzle (v3.9.3)&lt;br /&gt;
** symfony/event-dispatcher (v2.8.11)&lt;br /&gt;
&lt;br /&gt;
* '''Installed'''&lt;br /&gt;
** composer/composer (1.0.3)&lt;br /&gt;
** composer/semver (1.4.2)&lt;br /&gt;
** composer/spdx-licenses (1.1.4)&lt;br /&gt;
** doctrine/inflector (v1.1.0)&lt;br /&gt;
** guzzlehttp/guzzle (5.0.3)&lt;br /&gt;
** guzzlehttp/ringphp (1.1.0)&lt;br /&gt;
** guzzlehttp/streams (3.0.0)&lt;br /&gt;
** illuminate/console (v5.2.37)&lt;br /&gt;
** illuminate/contracts (v5.2.45)&lt;br /&gt;
** justinrainbow/json-schema (1.6.1)&lt;br /&gt;
** mtdowling/cron-expression (v1.1.0)&lt;br /&gt;
** paragonie/random_compat (v1.4.1)&lt;br /&gt;
** react/promise (v2.4.1)&lt;br /&gt;
** symfony/console (v2.8.11)&lt;br /&gt;
** symfony/finder (v2.8.7)&lt;br /&gt;
** symfony/filesystem (v3.0.9)&lt;br /&gt;
** symfony/polyfill-php55 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-php54 (v1.2.0)&lt;br /&gt;
** symfony/polyfill-mbstring (v1.2.0)&lt;br /&gt;
** symfony/process (v2.8.11)&lt;br /&gt;
** seld/jsonlint (1.4.1)&lt;br /&gt;
** seld/phar-utils (1.0.1)&lt;br /&gt;
&lt;br /&gt;
* '''Updated'''&lt;br /&gt;
** illuminate/support (v4.1.30) to illuminate/support (v5.2.37)&lt;br /&gt;
** illuminate/container (v4.1.30) to illuminate/container (v5.2.37)&lt;br /&gt;
** illuminate/database (v4.1.30) to illuminate/database (v5.2.37)&lt;br /&gt;
** illuminate/events (v4.1.30) to illuminate/events (v5.2.37)&lt;br /&gt;
** knplabs/knp-menu (v2.1.0) to knplabs/knp-menu (v2.1.1)&lt;br /&gt;
** league/climate (3.2.0) to league/climate (3.2.1)&lt;br /&gt;
** monolog/monolog (1.17.2) to monolog/monolog (1.18.2)&lt;br /&gt;
** nesbot/carbon (1.20.0) to nesbot/carbon (1.21.0)&lt;br /&gt;
** php-imap/php-imap (2.0.4) to php-imap/php-imap (2.0.6)&lt;br /&gt;
** phpmailer/phpmailer (v5.2.14) to phpmailer/phpmailer (v5.2.16)&lt;br /&gt;
** phpseclib/phpseclib (1.0.0) to phpseclib/phpseclib (2.0.2)&lt;br /&gt;
** rhumsaa/uuid (2.8.2) to ramsey/uuid (3.4.1)&lt;br /&gt;
** smarty/smarty (v3.1.21) to smarty/smarty (v3.1.29)&lt;br /&gt;
** symfony/http-foundation (v2.6.11) to symfony/http-foundation (v2.8.7)&lt;br /&gt;
** symfony/translation (v2.6.11) to symfony/translation (v2.8.7)&lt;br /&gt;
** symfony/yaml (v2.6.11) to symfony/yaml (v2.8.7)&lt;br /&gt;
&lt;br /&gt;
==Template Changes==&lt;br /&gt;
&lt;br /&gt;
=== Six Template ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.1 and 7.0.0-release.1.&lt;br /&gt;
https://github.com/WHMCS/templates-six/compare/v6.3.1-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
=== Standard Cart Order Form ===&lt;br /&gt;
For a list of changed files and graphical view of the exact changes, please refer to the Github repo below.&lt;br /&gt;
&lt;br /&gt;
The following link provides a comparison of changes between 6.3.0 and 7.0.0-release.1:&lt;br /&gt;
https://github.com/WHMCS/orderforms-standard_cart/compare/v6.3.0-release.1...v7.0.0-release.1&lt;br /&gt;
&lt;br /&gt;
==Changelog==&lt;br /&gt;
&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_1|Version 7.0.0 Beta 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_2|Version 7.0.0 Beta 2]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_Beta_3|Version 7.0.0 Beta 3]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_RC_1|Version 7.0.0 RC 1]]&lt;br /&gt;
* [[Changelog:WHMCS_V7.0.0_GA|Version 7.0.0 GA]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_RC_1&amp;diff=20250</id>
		<title>Changelog:WHMCS V7.0.0 RC 1</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_RC_1&amp;diff=20250"/>
				<updated>2016-09-17T00:23:48Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Implemented ====&lt;br /&gt;
FEATURE-1097&amp;amp;nbsp;-&amp;amp;nbsp;Implement Recaptcha V2 to ticket submission and contact form&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1312&amp;amp;nbsp;-&amp;amp;nbsp;Add support for using direct user accounts with DuoSecurity module&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Maintenance ====&lt;br /&gt;
CORE-9973&amp;amp;nbsp;-&amp;amp;nbsp;Improve styling of the Mass Update Items popup on the Client Summary page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10057&amp;amp;nbsp;-&amp;amp;nbsp;Improve search results when searching invoices with MariaDB 10.0.25&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10078&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX of bulk update of items in admin client summary&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10297&amp;amp;nbsp;-&amp;amp;nbsp;Add Suspension Reason to Get Clients Products API&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10330&amp;amp;nbsp;-&amp;amp;nbsp;Update to .tr whois servers&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10331&amp;amp;nbsp;-&amp;amp;nbsp;Update to .istanbul whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10334&amp;amp;nbsp;-&amp;amp;nbsp;Improve usability in domain pricing setup with smaller resolutions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10344&amp;amp;nbsp;-&amp;amp;nbsp;Improve display of Support Ticket Statuses with no Latin characters&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10350&amp;amp;nbsp;-&amp;amp;nbsp;Remove double or trailing slash for system url in various admin notifications&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10354&amp;amp;nbsp;-&amp;amp;nbsp;Improve stability of automatic updater&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10356&amp;amp;nbsp;-&amp;amp;nbsp;Optimise memory usage in client area language locale loading&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10360&amp;amp;nbsp;-&amp;amp;nbsp;Ensure that PHP unlimited memory_limit set is properly respected&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10365&amp;amp;nbsp;-&amp;amp;nbsp;Introduction of additional hook points&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10366&amp;amp;nbsp;-&amp;amp;nbsp;Improve compatibility of &amp;amp;quot;Add to Cart&amp;amp;quot; button with translations enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10370&amp;amp;nbsp;-&amp;amp;nbsp;Rename System Health &amp;amp;amp; Updates Help Utility to System Health Status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10375&amp;amp;nbsp;-&amp;amp;nbsp;Provide backwards compatibility for the &amp;amp;#039;template&amp;amp;#039; variable to Smarty templates&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10393&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Markdown line break is cross platform friendly&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10409&amp;amp;nbsp;-&amp;amp;nbsp;Ensure NewTLDs addon module is properly returning support email field&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10411&amp;amp;nbsp;-&amp;amp;nbsp;Fix bug resulting in error when making changes to &amp;amp;quot;My Details&amp;amp;quot; in client area&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10421&amp;amp;nbsp;-&amp;amp;nbsp;Implement &amp;amp;#039;EmailPreLog&amp;amp;#039; hook&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10430&amp;amp;nbsp;-&amp;amp;nbsp;Ensure emails with attachments are sending correctly under certain conditions&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Modules ====&lt;br /&gt;
MODULE-6432&amp;amp;nbsp;-&amp;amp;nbsp;[Nominet] Specify xsi:schemaLocation in contact extension of contact creation command&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Languages ====&lt;br /&gt;
CORE-10304&amp;amp;nbsp;-&amp;amp;nbsp;Ensure order form honours orderforms.addedToCartRemove language string&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10346&amp;amp;nbsp;-&amp;amp;nbsp;Danish Translation additions and improvements&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_RC_1&amp;diff=20242</id>
		<title>Changelog:WHMCS V7.0.0 RC 1</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_RC_1&amp;diff=20242"/>
				<updated>2016-09-16T21:47:52Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Maintenance */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Implemented ==&lt;br /&gt;
FEATURE-1097&amp;amp;nbsp;-&amp;amp;nbsp;Implement Recaptcha V2 to ticket submission and contact form&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1312&amp;amp;nbsp;-&amp;amp;nbsp;Add support for using direct user accounts with DuoSecurity module&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-9973&amp;amp;nbsp;-&amp;amp;nbsp;Improve styling of the Mass Update Items popup on the Client Summary page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10057&amp;amp;nbsp;-&amp;amp;nbsp;Improve search results when searching invoices with MariaDB 10.0.25&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10078&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX of bulk update of items in admin client summary&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10297&amp;amp;nbsp;-&amp;amp;nbsp;Add Suspension Reason to Get Clients Products API&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10330&amp;amp;nbsp;-&amp;amp;nbsp;Update to .tr whois servers&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10331&amp;amp;nbsp;-&amp;amp;nbsp;Update to .istanbul whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10334&amp;amp;nbsp;-&amp;amp;nbsp;Improve usability in domain pricing setup with smaller resolutions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10344&amp;amp;nbsp;-&amp;amp;nbsp;Improve display of Support Ticket Statuses with no Latin characters&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10350&amp;amp;nbsp;-&amp;amp;nbsp;Remove double or trailing slash for system url in various admin notifications&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10354&amp;amp;nbsp;-&amp;amp;nbsp;Improve stability of automatic updater&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10356&amp;amp;nbsp;-&amp;amp;nbsp;Optimise memory usage in client area language locale loading&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10360&amp;amp;nbsp;-&amp;amp;nbsp;Ensure that PHP unlimited memory_limit set is properly respected&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10365&amp;amp;nbsp;-&amp;amp;nbsp;Introduction of additional hook points&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10366&amp;amp;nbsp;-&amp;amp;nbsp;Improve compatibility of &amp;amp;quot;Add to Cart&amp;amp;quot; button with translations enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10370&amp;amp;nbsp;-&amp;amp;nbsp;Rename System Health &amp;amp;amp; Updates Help Utility to System Health Status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10375&amp;amp;nbsp;-&amp;amp;nbsp;Provide backwards compatibility for the &amp;amp;#039;template&amp;amp;#039; variable to Smarty templates&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10393&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Markdown line break is cross platform friendly&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10409&amp;amp;nbsp;-&amp;amp;nbsp;Ensure NewTLDs addon module is properly returning support email field&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10411&amp;amp;nbsp;-&amp;amp;nbsp;Fix bug resulting in error when making changes to &amp;amp;quot;My Details&amp;amp;quot; in client area&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10421&amp;amp;nbsp;-&amp;amp;nbsp;Implement &amp;amp;#039;EmailPreLog&amp;amp;#039; hook&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10430&amp;amp;nbsp;-&amp;amp;nbsp;Ensure emails with attachments are sending correctly under certain conditions&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6432&amp;amp;nbsp;-&amp;amp;nbsp;[Nominet] Specify xsi:schemaLocation in contact extension of contact creation command&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10304&amp;amp;nbsp;-&amp;amp;nbsp;Ensure order form honours orderforms.addedToCartRemove language string&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10346&amp;amp;nbsp;-&amp;amp;nbsp;Danish Translation additions and improvements&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19966</id>
		<title>Changelog:WHMCS V7.0.0 Beta 3</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19966"/>
				<updated>2016-08-25T20:22:55Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Maintenance ====&lt;br /&gt;
CORE-7118&amp;amp;nbsp;(#4368)&amp;amp;nbsp;-&amp;amp;nbsp;Render line breaks in product description on configure product step of shopping cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8936&amp;amp;nbsp;-&amp;amp;nbsp;Fix status colours not being displayed correctly for non-english languages&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9103&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9563&amp;amp;nbsp;-&amp;amp;nbsp;Provide more concise logging of application links activation failure following cPanel Error ID introduction&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10043&amp;amp;nbsp;-&amp;amp;nbsp;Ensure escalation rules ignore original ticket after ticket merge&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10059&amp;amp;nbsp;-&amp;amp;nbsp;Introduce global admin area check for MySQL strict mode&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10104&amp;amp;nbsp;-&amp;amp;nbsp;Update to .au whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10153&amp;amp;nbsp;-&amp;amp;nbsp;Remove soon to be discontinued app store references&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10175&amp;amp;nbsp;-&amp;amp;nbsp;Ensure merged tickets are excluded from ticketsallactive admin template variable&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10187&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ma whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10188&amp;amp;nbsp;-&amp;amp;nbsp;Update to .mg whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10250&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ph whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10254&amp;amp;nbsp;-&amp;amp;nbsp;Add support for header and footer templates in PDF invoice generation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10266&amp;amp;nbsp;-&amp;amp;nbsp;Correct mapping of lastLoginHostname field in User Client class&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10276&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Last Login Date in admin area shows valid data on no logins&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10277&amp;amp;nbsp;-&amp;amp;nbsp;Implement Spotlight TLDs to Product Domain ordering process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10283&amp;amp;nbsp;-&amp;amp;nbsp;Introduce ability to search by invoice number in Intelligent Search&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10285&amp;amp;nbsp;-&amp;amp;nbsp;Add auto update environment compatibility checks to update page and health status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10290&amp;amp;nbsp;-&amp;amp;nbsp;Implement client side validation logic for credit card input via admin UI&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10291&amp;amp;nbsp;-&amp;amp;nbsp;Fix incorrect path reference leading to open_basedir warning&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10293&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Ticket Feedback per departments is triggered in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10296&amp;amp;nbsp;-&amp;amp;nbsp;Improve upgrade stability with multiple Ticket Feedback departments set&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10301&amp;amp;nbsp;-&amp;amp;nbsp;Improve cron behavior with certain types of client profiles&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10312&amp;amp;nbsp;-&amp;amp;nbsp;Implement Captcha support in new Domain Lookup&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10323&amp;amp;nbsp;-&amp;amp;nbsp;Update Nominet module compatibility with TLS requirements&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Modules ====&lt;br /&gt;
MODULE-6439&amp;amp;nbsp;-&amp;amp;nbsp;Improve logging of manual Futurepay payments&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9932&amp;amp;nbsp;-&amp;amp;nbsp;Improve tabOverviewReplacementTemplate functionality with URLs&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== API ====&lt;br /&gt;
CORE-10090&amp;amp;nbsp;-&amp;amp;nbsp;Add Required and Raw Name for GetProducts API configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10108&amp;amp;nbsp;-&amp;amp;nbsp;Exclude merged tickets from GetStats API response&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Languages ====&lt;br /&gt;
CORE-10119&amp;amp;nbsp;-&amp;amp;nbsp;Dutch language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10284&amp;amp;nbsp;-&amp;amp;nbsp;Russian language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19958</id>
		<title>Changelog:WHMCS V7.0.0 Beta 3</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19958"/>
				<updated>2016-08-25T20:18:16Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Maintenance */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Implemented ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-7118&amp;amp;nbsp;(#4368)&amp;amp;nbsp;-&amp;amp;nbsp;Render line breaks in product description on configure product step of shopping cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8936&amp;amp;nbsp;-&amp;amp;nbsp;Fix status colours not being displayed correctly for non-english languages&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9103&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9563&amp;amp;nbsp;-&amp;amp;nbsp;Provide more concise logging of application links activation failure following cPanel Error ID introduction&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10043&amp;amp;nbsp;-&amp;amp;nbsp;Ensure escalation rules ignore original ticket after ticket merge&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10059&amp;amp;nbsp;-&amp;amp;nbsp;Introduce global admin area check for MySQL strict mode&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10104&amp;amp;nbsp;-&amp;amp;nbsp;Update to .au whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10153&amp;amp;nbsp;-&amp;amp;nbsp;Remove soon to be discontinued app store references&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10175&amp;amp;nbsp;-&amp;amp;nbsp;Ensure merged tickets are excluded from ticketsallactive admin template variable&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10187&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ma whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10188&amp;amp;nbsp;-&amp;amp;nbsp;Update to .mg whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10250&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ph whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10254&amp;amp;nbsp;-&amp;amp;nbsp;Add support for header and footer templates in PDF invoice generation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10266&amp;amp;nbsp;-&amp;amp;nbsp;Correct mapping of lastLoginHostname field in User Client class&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10276&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Last Login Date in admin area shows valid data on no logins&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10277&amp;amp;nbsp;-&amp;amp;nbsp;Implement Spotlight TLDs to Product Domain ordering process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10283&amp;amp;nbsp;-&amp;amp;nbsp;Introduce ability to search by invoice number in Intelligent Search&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10285&amp;amp;nbsp;-&amp;amp;nbsp;Add auto update environment compatibility checks to update page and health status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10290&amp;amp;nbsp;-&amp;amp;nbsp;Implement client side validation logic for credit card input via admin UI&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10291&amp;amp;nbsp;-&amp;amp;nbsp;Fix incorrect path reference leading to open_basedir warning&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10293&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Ticket Feedback per departments is triggered in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10296&amp;amp;nbsp;-&amp;amp;nbsp;Improve upgrade stability with multiple Ticket Feedback departments set&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10301&amp;amp;nbsp;-&amp;amp;nbsp;Improve cron behavior with certain types of client profiles&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10312&amp;amp;nbsp;-&amp;amp;nbsp;Implement Captcha support in new Domain Lookup&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10323&amp;amp;nbsp;-&amp;amp;nbsp;Update Nominet module compatibility with TLS requirements&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6439&amp;amp;nbsp;-&amp;amp;nbsp;Improve logging of manual Futurepay payments&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9932&amp;amp;nbsp;-&amp;amp;nbsp;Improve tabOverviewReplacementTemplate functionality with URLs&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== API ==&lt;br /&gt;
CORE-10090&amp;amp;nbsp;-&amp;amp;nbsp;Add Required and Raw Name for GetProducts API configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10108&amp;amp;nbsp;-&amp;amp;nbsp;Exclude merged tickets from GetStats API response&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10119&amp;amp;nbsp;-&amp;amp;nbsp;Dutch language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10284&amp;amp;nbsp;-&amp;amp;nbsp;Russian language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19954</id>
		<title>Changelog:WHMCS V7.0.0 Beta 3</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19954"/>
				<updated>2016-08-25T20:17:24Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Maintenance */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Implemented ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-7118&amp;amp;nbsp;(#4368)&amp;amp;nbsp;-&amp;amp;nbsp;Render line breaks in product description on configure product step of shopping cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8936&amp;amp;nbsp;-&amp;amp;nbsp;Fix status colours not being displayed correctly for non-english languages&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9103&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9563&amp;amp;nbsp;-&amp;amp;nbsp;Provide more concise logging of application links activation failure following cPanel Error ID introduction&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10043&amp;amp;nbsp;-&amp;amp;nbsp;Ensure escalation rules ignore original ticket after ticket merge&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10059&amp;amp;nbsp;-&amp;amp;nbsp;Introduce global admin area check for MySQL strict mode&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10104&amp;amp;nbsp;-&amp;amp;nbsp;Update to .au whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10153&amp;amp;nbsp;-&amp;amp;nbsp;Remove soon to be discontinued app store references&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10175&amp;amp;nbsp;-&amp;amp;nbsp;Ensure merged tickets are excluded from ticketsallactive admin template variable&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10187&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ma whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10188&amp;amp;nbsp;-&amp;amp;nbsp;Update to .mg whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10250&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ph whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10254&amp;amp;nbsp;-&amp;amp;nbsp;Add support for header and footer templates in PDF invoice generation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10266&amp;amp;nbsp;-&amp;amp;nbsp;Correct mapping of lastLoginHostname field in User Client class&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10276&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Last Login Date in admin area shows valid data on no logins&amp;lt;br &lt;br /&gt;
CORE-10277&amp;amp;nbsp;-&amp;amp;nbsp;Implement Spotlight TLDs to Product Domain ordering process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10283&amp;amp;nbsp;-&amp;amp;nbsp;Introduce ability to search by invoice number in Intelligent Search&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10285&amp;amp;nbsp;-&amp;amp;nbsp;Add auto update environment compatibility checks to update page and health status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10290&amp;amp;nbsp;-&amp;amp;nbsp;Implement client side validation logic for credit card input via admin UI&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10291&amp;amp;nbsp;-&amp;amp;nbsp;Fix incorrect path reference leading to open_basedir warning&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10293&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Ticket Feedback per departments is triggered in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10296&amp;amp;nbsp;-&amp;amp;nbsp;Improve upgrade stability with multiple Ticket Feedback departments set&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10301&amp;amp;nbsp;-&amp;amp;nbsp;Improve cron behavior with certain types of client profiles&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10312&amp;amp;nbsp;-&amp;amp;nbsp;Implement Captcha support in new Domain Lookup&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10323&amp;amp;nbsp;-&amp;amp;nbsp;Update Nominet module compatibility with TLS requirements&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6439&amp;amp;nbsp;-&amp;amp;nbsp;Improve logging of manual Futurepay payments&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9932&amp;amp;nbsp;-&amp;amp;nbsp;Improve tabOverviewReplacementTemplate functionality with URLs&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== API ==&lt;br /&gt;
CORE-10090&amp;amp;nbsp;-&amp;amp;nbsp;Add Required and Raw Name for GetProducts API configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10108&amp;amp;nbsp;-&amp;amp;nbsp;Exclude merged tickets from GetStats API response&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10119&amp;amp;nbsp;-&amp;amp;nbsp;Dutch language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10284&amp;amp;nbsp;-&amp;amp;nbsp;Russian language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=PDF_Invoice_Customisation&amp;diff=19950</id>
		<title>PDF Invoice Customisation</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=PDF_Invoice_Customisation&amp;diff=19950"/>
				<updated>2016-08-25T20:09:58Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are 2 invoice templates. One is for the client area invoice ('''viewinvoice.tpl'''). The other is for the PDF version of an invoice ('''invoicepdf.tpl'''). The templates are found in the active WHMCS template folder.&lt;br /&gt;
&lt;br /&gt;
==Modifying the Logo==&lt;br /&gt;
&lt;br /&gt;
The logo displayed on the PDF invoices is in the '''/assets/img/''' folder.  To change this logo, upload the required logo to the /assets/img/ folder. The name of the file should be &amp;quot;logo.jpg&amp;quot; or &amp;quot;logo.png&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The width of the logo image can be changed in the invoicepdf.tpl template file. On line 4, adjust the last number &amp;quot;75&amp;quot; before the closing bracket );. This variable defines the image width. A developer can then experiment increasing and decreasing it until happy.&lt;br /&gt;
&lt;br /&gt;
==Header &amp;amp; Footer==&lt;br /&gt;
&lt;br /&gt;
It is possible to have a header and/or footer automatically repeat on every page of a multi-page PDF invoice.&lt;br /&gt;
The following template files, if present in your theme, will be automatically included for every rendered PDF page:&lt;br /&gt;
&lt;br /&gt;
*invoicepdfheader.tpl&lt;br /&gt;
&lt;br /&gt;
*invoicepdffooter.tpl&lt;br /&gt;
&lt;br /&gt;
Only the respective header or footer file is required. For example, if you just want a customized footer on each page, you only need to create invoicepdffooter.tpl. These files must be located in the same directory as the invoicepdf.tpl template file.&lt;br /&gt;
During template processing, Smarty will provide each of these template files the same variables as invoicepdf.tpl.&lt;br /&gt;
&lt;br /&gt;
==Editing Text &amp;amp; Content==&lt;br /&gt;
&lt;br /&gt;
A developer can customise the PDF invoices. This includes adding or removing text, altering the layout or adding further images &amp;amp; formatting.  Do this by editing the template file '''invoicepdf.tpl''' in the active template folder. The file contains all the code relating to the layout and display of the invoice in its PDF format. A basic working knowledge of PHP coding to understand and modify the file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-related-pages&amp;quot;&amp;gt;PDF's generate using TCPDF. A full list of functions to help you build the template is available@ http://www.tcpdf.org/doc/code/classTCPDF.html&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Displaying Custom Fields==&lt;br /&gt;
&lt;br /&gt;
It is possible to display Custom fields on printable and PDF invoices. Do this by ticking the '''Setup &amp;gt; Custom Client Fields &amp;gt; Show on Invoice''' option.&lt;br /&gt;
&lt;br /&gt;
The following variables are available for use in the invoicepdf.tpl file. Obtain further data by running SQL queries from within the PHP template.&lt;br /&gt;
&lt;br /&gt;
*$invoiceid - The ID of the invoice&lt;br /&gt;
*$invoicenum - The custom number of the invoice (only set when proforma or sequential invoicing is enabled)&lt;br /&gt;
*$datecreated - Creation Date of the invoice&lt;br /&gt;
*$duedate - Due date of the invoice&lt;br /&gt;
*$datepaid - Shows paid date/time if invoice status is Paid&lt;br /&gt;
*$userid - Client ID Number&lt;br /&gt;
*$clientsdetails[&amp;quot;firstname&amp;quot;] - Client Info First Name&lt;br /&gt;
*$clientsdetails[&amp;quot;lastname&amp;quot;] - Client Info Last Name&lt;br /&gt;
*$clientsdetails[&amp;quot;companyname&amp;quot;] - Client Info Company Name&lt;br /&gt;
*$clientsdetails[&amp;quot;fieldname&amp;quot;] - etc...&lt;br /&gt;
*$clientsdetails[&amp;quot;customfields1&amp;quot;] - Client Info Custom Field #1&lt;br /&gt;
*$subtotal&lt;br /&gt;
*$tax&lt;br /&gt;
*$taxrate&lt;br /&gt;
*$credit&lt;br /&gt;
*$total&lt;br /&gt;
*$status - Paid, Unpaid or Cancelled&lt;br /&gt;
*$paymentmethod&lt;br /&gt;
*$notes&lt;br /&gt;
*$companyname - The Company Name&lt;br /&gt;
*$companyurl - The Default Website URL&lt;br /&gt;
*$companyaddress - The Company Address&lt;br /&gt;
*$invoiceitems - Array of invoice items&lt;br /&gt;
&lt;br /&gt;
==Changing/Translating Filename==&lt;br /&gt;
The default filename for invoices is Invoice-xxx. For quotes, this is Quote-xxx. For both, xxx is the ID of the invoice or quote. It may be desirable to change the filenames the clients see or translate into other languages. Achieve this in the same way as any text within WHMCS, by using the [[Language Files]]. Look for the strings:&lt;br /&gt;
&lt;br /&gt;
 $_LANG['invoicefilename'] = &amp;quot;Invoice-&amp;quot;;&lt;br /&gt;
 $_LANG['quotefilename'] = &amp;quot;Quote-&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==Reducing the Filesize of PDFs==&lt;br /&gt;
&lt;br /&gt;
The bulk of the file size for PDFs generated by WHMCS come from the embedded font files for UTF-8. Because the UTF-8 charset has a large range of supported characters, this means it takes up more space than say the iso-8859-1 charset. Unlike UTF-8, iso-8859-1, only supports A-Z 0-9 and other standard characters.&lt;br /&gt;
&lt;br /&gt;
If no clients are using special characters in their names/addresses then UTF-8 is not required. It is then possible to reduce the filesize of PDF's by changing the font. To do that, go to '''Setup &amp;gt; General Settings &amp;gt; Invoices &amp;gt; TCPDF Font'''. Once there, change the selection from &amp;quot;Freesans&amp;quot; to &amp;quot;Helvetica&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==Additional Fonts==&lt;br /&gt;
&lt;br /&gt;
The use of certain special characters may not be available in the standard font. So, WHMCS supply an alternative font type that supports Czech, Russian, Arabic &amp;amp; Persian among others. To install:&lt;br /&gt;
# Download the font files from the URL below.&lt;br /&gt;
# Upload into the '''/vendor/tecnick.com/tcpdf/fonts/''' (if you are using WHMCS 6.0 or 6.1) or '''/vendor/tecnickcom/tcpdf/fonts/''' (if you are using WHMCS 6.2 or newer) folder.&lt;br /&gt;
# Specify the custom font name '''dejavusans''' in '''Setup &amp;gt; General Settings &amp;gt; Invoices &amp;gt; TCPDF Font'''.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-related-pages&amp;quot;&amp;gt;http://www.whmcs.com/download/106/dejavusans_tcpdf_font&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Accented Characters===&lt;br /&gt;
Due to a PHP limitation, the translations of the &amp;quot;Paid&amp;quot; and &amp;quot;Unpaid&amp;quot; text on the PDF Invoices may not display upper-case accented characters.&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-related-pages&amp;quot;&amp;gt;To resolve this please refer to http://forum.whmcs.com/showthread.php?t=45594&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Question Marks===&lt;br /&gt;
Sometimes, question marks appear in the PDF files in place of non-Latin or accented characters. This can suggest the character is not supported by the font. The first thing to try is setting the font to &amp;quot;Freesans&amp;quot; in '''Setup &amp;gt; General Settings &amp;gt; Invoicing'''.&lt;br /&gt;
&lt;br /&gt;
If the problem persists, please download and install &amp;quot;dejavusans&amp;quot; as described above [[#Additional_Fonts|Additional Fonts]]. This font pack contains more characters than standard ones so stands the best chance of working with these characters.&lt;br /&gt;
&lt;br /&gt;
===TCPDF error: Missing or incorrect image file===&lt;br /&gt;
This means the logo.png or logo.jpg file in your /assets/img/ folder is missing or is not a valid image file. This is the image used when creating the pdf invoice. Please re-save the image file and re-upload to the /assets/img directory.&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19942</id>
		<title>Changelog:WHMCS V7.0.0 Beta 3</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19942"/>
				<updated>2016-08-25T20:04:27Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Implemented ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-7118&amp;amp;nbsp;(#4368)&amp;amp;nbsp;-&amp;amp;nbsp;Render line breaks in product description on configure product step of shopping cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8936&amp;amp;nbsp;-&amp;amp;nbsp;Fix status colours not being displayed correctly for non-english languages&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9103&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9563&amp;amp;nbsp;-&amp;amp;nbsp;Provide more concise logging of application links activation failure following cPanel Error ID introduction&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10043&amp;amp;nbsp;-&amp;amp;nbsp;Ensure escalation rules ignore original ticket after ticket merge&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10059&amp;amp;nbsp;-&amp;amp;nbsp;Introduce global admin area check for MySQL strict mode&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10104&amp;amp;nbsp;-&amp;amp;nbsp;Update to .au whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10153&amp;amp;nbsp;-&amp;amp;nbsp;Remove soon to be discontinued app store references&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10175&amp;amp;nbsp;-&amp;amp;nbsp;Ensure merged tickets are excluded from ticketsallactive admin template variable&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10187&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ma whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10188&amp;amp;nbsp;-&amp;amp;nbsp;Update to .mg whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10250&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ph whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10254&amp;amp;nbsp;-&amp;amp;nbsp;Add support for header and footer templates in PDF invoice generation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10266&amp;amp;nbsp;-&amp;amp;nbsp;Correct mapping of lastLoginHostname field in User Client class&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10276&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Last Login Date in admin area shows valid data on no logins&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: SBCL-906&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10277&amp;amp;nbsp;-&amp;amp;nbsp;Implement Spotlight TLDs to Product Domain ordering process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10283&amp;amp;nbsp;-&amp;amp;nbsp;Introduce ability to search by invoice number in Intelligent Search&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10285&amp;amp;nbsp;-&amp;amp;nbsp;Add auto update environment compatibility checks to update page and health status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10290&amp;amp;nbsp;-&amp;amp;nbsp;Implement client side validation logic for credit card input via admin UI&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10291&amp;amp;nbsp;-&amp;amp;nbsp;Fix incorrect path reference leading to open_basedir warning&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10293&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Ticket Feedback per departments is triggered in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10296&amp;amp;nbsp;-&amp;amp;nbsp;Improve upgrade stability with multiple Ticket Feedback departments set&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10301&amp;amp;nbsp;-&amp;amp;nbsp;Improve cron behavior with certain types of client profiles&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10312&amp;amp;nbsp;-&amp;amp;nbsp;Implement Captcha support in new Domain Lookup&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10323&amp;amp;nbsp;-&amp;amp;nbsp;Update Nominet module compatibility with TLS requirements&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6439&amp;amp;nbsp;-&amp;amp;nbsp;Improve logging of manual Futurepay payments&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9932&amp;amp;nbsp;-&amp;amp;nbsp;Improve tabOverviewReplacementTemplate functionality with URLs&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== API ==&lt;br /&gt;
CORE-10090&amp;amp;nbsp;-&amp;amp;nbsp;Add Required and Raw Name for GetProducts API configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10108&amp;amp;nbsp;-&amp;amp;nbsp;Exclude merged tickets from GetStats API response&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10119&amp;amp;nbsp;-&amp;amp;nbsp;Dutch language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10284&amp;amp;nbsp;-&amp;amp;nbsp;Russian language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19938</id>
		<title>Changelog:WHMCS V7.0.0 Beta 3</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19938"/>
				<updated>2016-08-25T20:03:32Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Version 7.0.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Implemented ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-7118&amp;amp;nbsp;(#4368)&amp;amp;nbsp;-&amp;amp;nbsp;Render line breaks in product description on configure product step of shopping cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8936&amp;amp;nbsp;-&amp;amp;nbsp;Fix status colours not being displayed correctly for non-english languages&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9103&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9563&amp;amp;nbsp;-&amp;amp;nbsp;Provide more concise logging of application links activation failure following cPanel Error ID introduction&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10043&amp;amp;nbsp;-&amp;amp;nbsp;Ensure escalation rules ignore original ticket after ticket merge&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10059&amp;amp;nbsp;-&amp;amp;nbsp;Introduce global admin area check for MySQL strict mode&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10104&amp;amp;nbsp;-&amp;amp;nbsp;Update to .au whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10153&amp;amp;nbsp;-&amp;amp;nbsp;Remove soon to be discontinued app store references&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10175&amp;amp;nbsp;-&amp;amp;nbsp;Ensure merged tickets are excluded from ticketsallactive admin template variable&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10187&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ma whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10188&amp;amp;nbsp;-&amp;amp;nbsp;Update to .mg whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10250&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ph whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10254&amp;amp;nbsp;-&amp;amp;nbsp;Add support for header and footer templates in PDF invoice generation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10266&amp;amp;nbsp;-&amp;amp;nbsp;Correct mapping of lastLoginHostname field in User Client class&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10276&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Last Login Date in admin area shows valid data on no logins&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: SBCL-906&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10277&amp;amp;nbsp;-&amp;amp;nbsp;Implement Spotlight TLDs to Product Domain ordering process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10283&amp;amp;nbsp;-&amp;amp;nbsp;Introduce ability to search by invoice number in Intelligent Search&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10285&amp;amp;nbsp;-&amp;amp;nbsp;Add auto update environment compatibility checks to update page and health status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10290&amp;amp;nbsp;-&amp;amp;nbsp;Implement client side validation logic for credit card input via admin UI&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10291&amp;amp;nbsp;-&amp;amp;nbsp;Fix incorrect path reference leading to open_basedir warning&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10293&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Ticket Feedback per departments is triggered in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10296&amp;amp;nbsp;-&amp;amp;nbsp;Improve upgrade stability with multiple Ticket Feedback departments set&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10301&amp;amp;nbsp;-&amp;amp;nbsp;Improve cron behavior with certain types of client profiles&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10312&amp;amp;nbsp;-&amp;amp;nbsp;Implement Captcha support in new Domain Lookup&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10323&amp;amp;nbsp;-&amp;amp;nbsp;Update Nominet module compatibility with TLS requirements&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6439&amp;amp;nbsp;-&amp;amp;nbsp;Improve logging of manual Futurepay payments&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9932&amp;amp;nbsp;-&amp;amp;nbsp;Improve tabOverviewReplacementTemplate functionality with URLs&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== API ==&lt;br /&gt;
CORE-10090&amp;amp;nbsp;-&amp;amp;nbsp;Add Required and Raw Name for GetProducts API configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10108&amp;amp;nbsp;-&amp;amp;nbsp;Exclude merged tickets from GetStats API response&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10119&amp;amp;nbsp;-&amp;amp;nbsp;Dutch language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10284&amp;amp;nbsp;-&amp;amp;nbsp;Russian language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19934</id>
		<title>Changelog:WHMCS V7.0.0 Beta 3</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_3&amp;diff=19934"/>
				<updated>2016-08-25T20:02:52Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Created page with &amp;quot; &amp;lt;noinclude&amp;gt;Version 7.0.0 Beta 3 Release Notes&amp;lt;/noinclude&amp;gt;  == Implemented ==   == Maintenance == CORE-7118&amp;amp;nbsp;(#4368)&amp;amp;nbsp;-&amp;amp;nbsp;Render line breaks in product descript...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Version 7.0.0 Beta 3 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Implemented ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Maintenance ==&lt;br /&gt;
CORE-7118&amp;amp;nbsp;(#4368)&amp;amp;nbsp;-&amp;amp;nbsp;Render line breaks in product description on configure product step of shopping cart&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8936&amp;amp;nbsp;-&amp;amp;nbsp;Fix status colours not being displayed correctly for non-english languages&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9103&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9563&amp;amp;nbsp;-&amp;amp;nbsp;Provide more concise logging of application links activation failure following cPanel Error ID introduction&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10043&amp;amp;nbsp;-&amp;amp;nbsp;Ensure escalation rules ignore original ticket after ticket merge&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10059&amp;amp;nbsp;-&amp;amp;nbsp;Introduce global admin area check for MySQL strict mode&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10104&amp;amp;nbsp;-&amp;amp;nbsp;Update to .au whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10153&amp;amp;nbsp;-&amp;amp;nbsp;Remove soon to be discontinued app store references&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10175&amp;amp;nbsp;-&amp;amp;nbsp;Ensure merged tickets are excluded from ticketsallactive admin template variable&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10187&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ma whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10188&amp;amp;nbsp;-&amp;amp;nbsp;Update to .mg whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10250&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ph whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10254&amp;amp;nbsp;-&amp;amp;nbsp;Add support for header and footer templates in PDF invoice generation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10266&amp;amp;nbsp;-&amp;amp;nbsp;Correct mapping of lastLoginHostname field in User Client class&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10276&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Last Login Date in admin area shows valid data on no logins&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: SBCL-906&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10277&amp;amp;nbsp;-&amp;amp;nbsp;Implement Spotlight TLDs to Product Domain ordering process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10283&amp;amp;nbsp;-&amp;amp;nbsp;Introduce ability to search by invoice number in Intelligent Search&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10285&amp;amp;nbsp;-&amp;amp;nbsp;Add auto update environment compatibility checks to update page and health status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10290&amp;amp;nbsp;-&amp;amp;nbsp;Implement client side validation logic for credit card input via admin UI&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10291&amp;amp;nbsp;-&amp;amp;nbsp;Fix incorrect path reference leading to open_basedir warning&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10293&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Ticket Feedback per departments is triggered in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10296&amp;amp;nbsp;-&amp;amp;nbsp;Improve upgrade stability with multiple Ticket Feedback departments set&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10301&amp;amp;nbsp;-&amp;amp;nbsp;Improve cron behavior with certain types of client profiles&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10312&amp;amp;nbsp;-&amp;amp;nbsp;Implement Captcha support in new Domain Lookup&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10323&amp;amp;nbsp;-&amp;amp;nbsp;Update Nominet module compatibility with TLS requirements&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Modules ==&lt;br /&gt;
MODULE-6439&amp;amp;nbsp;-&amp;amp;nbsp;Improve logging of manual Futurepay payments&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9932&amp;amp;nbsp;-&amp;amp;nbsp;Improve tabOverviewReplacementTemplate functionality with URLs&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== API ==&lt;br /&gt;
CORE-10090&amp;amp;nbsp;-&amp;amp;nbsp;Add Required and Raw Name for GetProducts API configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10108&amp;amp;nbsp;-&amp;amp;nbsp;Exclude merged tickets from GetStats API response&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Languages ==&lt;br /&gt;
CORE-10119&amp;amp;nbsp;-&amp;amp;nbsp;Dutch language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10284&amp;amp;nbsp;-&amp;amp;nbsp;Russian language translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19738</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19738"/>
				<updated>2016-08-05T20:28:01Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Checking for Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateAvailableNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:Configureupdatesettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Modal-update.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowCustomisedFiles.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowBegin.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateSuccessful.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:UpdateAvailableNotification.png&amp;diff=19734</id>
		<title>File:UpdateAvailableNotification.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:UpdateAvailableNotification.png&amp;diff=19734"/>
				<updated>2016-08-05T20:27:39Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19730</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19730"/>
				<updated>2016-08-05T20:23:57Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Checking for Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:Configureupdatesettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Modal-update.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowCustomisedFiles.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowBegin.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateSuccessful.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19726</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19726"/>
				<updated>2016-08-05T20:23:23Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Starting the Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateConfirmPassword.png|center]]&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:Configureupdatesettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Modal-update.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowCustomisedFiles.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowBegin.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateSuccessful.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:UpdateNowBegin.png&amp;diff=19722</id>
		<title>File:UpdateNowBegin.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:UpdateNowBegin.png&amp;diff=19722"/>
				<updated>2016-08-05T20:23:02Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19718</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19718"/>
				<updated>2016-08-05T20:20:26Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Checking for Custom Files */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateConfirmPassword.png|center]]&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:Configureupdatesettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Modal-update.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowCustomisedFiles.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowThirdStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateSuccessful.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:UpdateNowCustomisedFiles.png&amp;diff=19714</id>
		<title>File:UpdateNowCustomisedFiles.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:UpdateNowCustomisedFiles.png&amp;diff=19714"/>
				<updated>2016-08-05T20:20:02Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19710</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19710"/>
				<updated>2016-08-05T20:17:16Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Finalizing the Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateConfirmPassword.png|center]]&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:Configureupdatesettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Modal-update.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowSecondStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowThirdStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateSuccessful.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:UpdateSuccessful.png&amp;diff=19706</id>
		<title>File:UpdateSuccessful.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:UpdateSuccessful.png&amp;diff=19706"/>
				<updated>2016-08-05T20:16:51Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:UpdateFinished.png&amp;diff=19702</id>
		<title>File:UpdateFinished.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:UpdateFinished.png&amp;diff=19702"/>
				<updated>2016-08-05T20:15:36Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Cole uploaded a new version of &amp;amp;quot;File:UpdateFinished.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19698</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19698"/>
				<updated>2016-08-05T20:13:27Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Checking for Updates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateConfirmPassword.png|center]]&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:Configureupdatesettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Modal-update.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowSecondStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowThirdStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateFinished.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:UpdateAvailable.png&amp;diff=19694</id>
		<title>File:UpdateAvailable.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:UpdateAvailable.png&amp;diff=19694"/>
				<updated>2016-08-05T20:12:37Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19690</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19690"/>
				<updated>2016-08-05T20:02:30Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Setting a Maintenance Message */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateConfirmPassword.png|center]]&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableBody.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:Configureupdatesettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Modal-update.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowSecondStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowThirdStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateFinished.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:Configureupdatesettings.png&amp;diff=19686</id>
		<title>File:Configureupdatesettings.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:Configureupdatesettings.png&amp;diff=19686"/>
				<updated>2016-08-05T20:02:07Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:EmptyConfigureUpdateSettings.png&amp;diff=19682</id>
		<title>File:EmptyConfigureUpdateSettings.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:EmptyConfigureUpdateSettings.png&amp;diff=19682"/>
				<updated>2016-08-05T19:55:15Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Cole uploaded a new version of &amp;amp;quot;File:EmptyConfigureUpdateSettings.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Updater Configuration settings allow admins to set the custom install path, the release channel, and the maintenance mode message displayed to clients&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:EmptyConfigureUpdateSettings.png&amp;diff=19678</id>
		<title>File:EmptyConfigureUpdateSettings.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:EmptyConfigureUpdateSettings.png&amp;diff=19678"/>
				<updated>2016-08-05T19:49:19Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Cole uploaded a new version of &amp;amp;quot;File:EmptyConfigureUpdateSettings.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Updater Configuration settings allow admins to set the custom install path, the release channel, and the maintenance mode message displayed to clients&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:EmptyConfigureUpdateSettings.png&amp;diff=19674</id>
		<title>File:EmptyConfigureUpdateSettings.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:EmptyConfigureUpdateSettings.png&amp;diff=19674"/>
				<updated>2016-08-05T19:48:54Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Cole uploaded a new version of &amp;amp;quot;File:EmptyConfigureUpdateSettings.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Updater Configuration settings allow admins to set the custom install path, the release channel, and the maintenance mode message displayed to clients&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=File:EmptyConfigureUpdateSettings.png&amp;diff=19670</id>
		<title>File:EmptyConfigureUpdateSettings.png</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=File:EmptyConfigureUpdateSettings.png&amp;diff=19670"/>
				<updated>2016-08-05T19:47:14Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: Cole uploaded a new version of &amp;amp;quot;File:EmptyConfigureUpdateSettings.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Updater Configuration settings allow admins to set the custom install path, the release channel, and the maintenance mode message displayed to clients&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19666</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19666"/>
				<updated>2016-08-05T19:04:00Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Beginning the Update Process */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateConfirmPassword.png|center]]&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableBody.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:EmptyConfigureUpdateSettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Modal-update.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowSecondStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowThirdStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateFinished.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19646</id>
		<title>Automatic Updater</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Automatic_Updater&amp;diff=19646"/>
				<updated>2016-08-05T14:24:36Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Requirements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
*The Automatic Updater requires at least 250 MB of free disk space&lt;br /&gt;
*The Automatic Updater requires PHP setting allow_url_fopen = true&lt;br /&gt;
*The Automatic Updater requires PHP setting open_basedir to include entire WHMCS docroot&lt;br /&gt;
*The Automatic Updater can take a few minutes, so you'll need to ensure that you allow long running php processes in your webserver&lt;br /&gt;
*The Automatic Updater will be extracting a .zip file. Therefore you must have enabled zip in your PHP binary or have the proc_open PHP function enabled.&lt;br /&gt;
&lt;br /&gt;
== Checking for Updates ==&lt;br /&gt;
&lt;br /&gt;
Introduced in WHMCS 7.0.0, the Automatic Updater provides admins with a quick and easy way to update to new versions of WHMCS with just a few clicks in the admin area interface. The system will check for new updates on each cron run. Upon logging into the WHMCS admin area, a notification will appear in the top right corner of admin area. This alert will let the admin know if a new version of WHMCS is available, or if the version of WHMCS that is currently installed is the latest version. Below are examples of what these notifications look like:&lt;br /&gt;
&lt;br /&gt;
 [[File:UpdateNotification.png|center]]&lt;br /&gt;
&lt;br /&gt;
Admins can also manually check for updates by navigating to the Utilities top menu in the admin area interface and select Update WHMCS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:WHMCSUpdateMenu.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once selected, the admin will be asked to confirm their password, as only admin users that have the &amp;quot;Update WHMCS&amp;quot; admin role will be able to access the updater.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateConfirmPassword.png|center]]&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Once in the Automatic Update interface, admins can tell at a glance what version of WHMCS that is installed, as well as check for updates using the Check for Updates button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:NoNewUpdatesAreAvailable.png|center]]&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableNotice.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By clicking Check for Updates, the version indicated in Your Version on the left side of the version summary will stay the same, but the information presented in the Latest Version on the right side of the version summary may be updated depending if a new update is available. It should also be noted that the Check Now button also indicates the last time an update check was performed. If a new version is available for upgrade, admins can then begin the update process by clicking the Update Now button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateAvailableBody.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Update Settings ==&lt;br /&gt;
&lt;br /&gt;
The Automatic Updater also presents admins with the ability to configure update settings such as choosing an update channel, setting a temporary update path, and setting an update maintenance message for customers. Note that accessing the update configuration page requires &amp;quot;Modify Update Configuration&amp;quot; administrator role, which is separate from &amp;quot;Update WHMCS&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
=== Choosing an Upgrade Channel ===&lt;br /&gt;
&lt;br /&gt;
The automatic updater provides admins with the ability to set the release stability that they are comfortable receiving. Admins will be able to select from the following channels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Channel'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;'''Description'''&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Stable&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Recommended for most installations of WHMCS, the Stable channel will present admins with the latest stable version that has been released by WHMCS.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Release Candidate&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Release Candidate will be able to upgrade to the latest Release Candidate builds of WHMCS, or the latest stable version of WHMCS - whichever is newer. This means if WHMCS is upgraded to 7.0.0-rc.1, when 7.0.0-GA is released, the admin will be prompted to upgrade to the general availability that was just released.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Beta&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Admins subscribed to the Beta release channel will be able to download the newest beta, release candidates, and stable versions of WHMCS. This is for testing installations, as it will allow admins to update to the latest WHMCS (beta, rc, or stable). WHMCS recommends development licenses use this channel.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Current Version&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;By selecting this channel, admins are electing to only receive maintenance updates for the major/minor version they are on. For example if the installed version of WHMCS is running 7.0.0-GA, admins will be offered 7.0.1-GA, but not 7.1.0. This channel is useful if the installed version of WHMCS has a number of 3rd party modules and customizations that need to be tested before upgrading to a new production release.&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Setting a Temporary Update Path ===&lt;br /&gt;
&lt;br /&gt;
The temporary path is used for staging files during an update. For security reasons it is recommended that this directory be located outside the public doc root, just like the attachments, templates_c, and downloads directories. The path must be an absolute path (i.e. /home/whmcsuser/tmp instead of ~/tmp) and must be writable by the admin that is running PHP. &lt;br /&gt;
&lt;br /&gt;
=== Setting a Maintenance Message ===&lt;br /&gt;
&lt;br /&gt;
Admins can use this option to set a message that will be displayed to users in the client area whenever an update is in progress, as the client and admin areas will be unavailable during an update. &lt;br /&gt;
&lt;br /&gt;
[[File:EmptyConfigureUpdateSettings.png|center]]&lt;br /&gt;
&lt;br /&gt;
== Performing an Update ==&lt;br /&gt;
&lt;br /&gt;
=== Beginning the Update Process ===&lt;br /&gt;
&lt;br /&gt;
Once the update configuration options have been set, admins can begin the update process. Before the update process begins, WHMCS strongly recommends that admins backup their current installation and database. WHMCS also recommends that at least 250 MB of disk space is available before beginning the update process. Once comfortable with the available disk space and backups have been made to the current installation and database, the admin can start the update by clicking the Continue button.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowFirstStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Checking for Custom Files ===&lt;br /&gt;
The next step in the upgrade process checks the current installation for customized files, such as template files, language translations, whois server entries, and additional domain fields. It's important to review these files, as just like in previous updates, any update applied to the installation of WHMCS will override any custom changes. Before continuing to the next step in the upgrade process, it is wise to backup any customized files in order to quickly apply them again after the update has been complete. WHMCS has also included changes to how admins can customize the additional domain fields, country / calling codes, and whois server entries so that admins can preserve changes between updates. To view this documentation, please refer to following documentation pages:&lt;br /&gt;
&lt;br /&gt;
*[http://docs.whmcs.com/Customising_Countries_and_Calling_Codes/ Customized Countries and Calling Codes]&lt;br /&gt;
*[http://docs.whmcs.com/WHOIS_Servers/ WHOIS Servers]&lt;br /&gt;
*[http://docs.whmcs.com/Additional_Domain_Fields/ Additional Domain Fields]&lt;br /&gt;
 &lt;br /&gt;
[[File:UpdateNowSecondStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Starting the Update ===&lt;br /&gt;
&lt;br /&gt;
Once an admin is comfortable with the status of their custom files, the next step in the update process is to start the update itself. It's important to note that this third step is the point of no return - one the update has started, there is no pausing or stopping the process, and it is strongly recommended that admins stay on this page and do not navigate away using their browser. When ready to begin, click the Update Now button. &lt;br /&gt;
&lt;br /&gt;
[[File:UpdateNowThirdStep.png|center]]&lt;br /&gt;
&lt;br /&gt;
=== Finalizing the Update ===&lt;br /&gt;
&lt;br /&gt;
The final step of the update process is confirmation that the update has been completed. The system will present the admin with an Update Completed message, along with a link to the current version's release notes.&lt;br /&gt;
&lt;br /&gt;
[[File:UpdateFinished.png|center]]&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19634</id>
		<title>Changelog:WHMCS V7.0.0 Beta 2</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19634"/>
				<updated>2016-08-05T13:39:11Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Implemented ====&lt;br /&gt;
FEATURE-1502&amp;amp;nbsp;-&amp;amp;nbsp;Use SSL for all client facing page requests when SSL is enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Maintenance ====&lt;br /&gt;
CORE-8945&amp;amp;nbsp;-&amp;amp;nbsp;Prevent erroneous default payment method changed log entry on client profile save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9285&amp;amp;nbsp;-&amp;amp;nbsp;Only run QuoteCreated hook after quote has been fully saved&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9590&amp;amp;nbsp;-&amp;amp;nbsp;Improve Product Addon Associated Downloads box resizing&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9759&amp;amp;nbsp;-&amp;amp;nbsp;Keep hostname separate from domain name registration on View Cart page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9830&amp;amp;nbsp;-&amp;amp;nbsp;Improve enable domain renewal orders support with Six template&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9890&amp;amp;nbsp;-&amp;amp;nbsp;Provide consistent language translation when viewing invoices using View as Client link &amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9244&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9993&amp;amp;nbsp;-&amp;amp;nbsp;Ensure password verification failure fails gracefully when password hash is unknown&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10037&amp;amp;nbsp;-&amp;amp;nbsp;Set secure flag for session cookies when using SSL&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10096&amp;amp;nbsp;-&amp;amp;nbsp;Add whois server for .family extension&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10134&amp;amp;nbsp;-&amp;amp;nbsp;Apply Markdown to Escalation Rule replies&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10196&amp;amp;nbsp;-&amp;amp;nbsp;Pressing enter on admin client services page should save changes&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10224&amp;amp;nbsp;-&amp;amp;nbsp;Ensure eNom Namespinner Configuration Modal closes on save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10225&amp;amp;nbsp;-&amp;amp;nbsp;Improve stability of Health and Updates page when an SSL URL is defined&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10226&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Second Level TLD availability displays correctly in Spotlight TLDs&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10228&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Health and Updates are sorted by severity&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10229&amp;amp;nbsp;-&amp;amp;nbsp;Allow users to step backwards within setup wizard&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10230&amp;amp;nbsp;-&amp;amp;nbsp;Email templates should always be stored without entity encoding&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10235&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX when editing a ticket reply&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10236&amp;amp;nbsp;-&amp;amp;nbsp;Setup Wizard language defaults to Arabic under certain conditions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10239&amp;amp;nbsp;-&amp;amp;nbsp;Allow user to trigger invoice mark paid routine for Unpaid invoices with zero balance due&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10240&amp;amp;nbsp;-&amp;amp;nbsp;Report printable view should retain print mode when altering filter&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10241&amp;amp;nbsp;-&amp;amp;nbsp;Intelligent search should allow searching by invoice number for invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10247&amp;amp;nbsp;-&amp;amp;nbsp;Improve wording of final step of Setup Wizard  &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10253&amp;amp;nbsp;-&amp;amp;nbsp;Improve image display uploaded from Setup Wizard in system emails&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10255&amp;amp;nbsp;-&amp;amp;nbsp;Add trusted_dir to Smarty Security Policy&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10256&amp;amp;nbsp;-&amp;amp;nbsp;Use logo uploaded via Setup Wizard for PDF invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10261&amp;amp;nbsp;-&amp;amp;nbsp;Ensure new invoice will generate on upgrade of product for which renewal invoice has already been generated&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-7163&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10263&amp;amp;nbsp;-&amp;amp;nbsp;Remove unnecessary warnings when saving addon modules configuring settings&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10267&amp;amp;nbsp;-&amp;amp;nbsp;Ensure server module screen displays FriendlyName and default values for fields&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Modules ====&lt;br /&gt;
MODULE-6215&amp;amp;nbsp;-&amp;amp;nbsp;OVH module update to support .fr domains&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6388&amp;amp;nbsp;-&amp;amp;nbsp;[PayPal] Pass new service price for service when upgrading configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6423&amp;amp;nbsp;-&amp;amp;nbsp;InternetSecure: No longer ship module due to service discontinuation&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6428&amp;amp;nbsp;-&amp;amp;nbsp;WorldPay FuturePay: Allow viewing token via credit card modal without credit cards being enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== API ====&lt;br /&gt;
CORE-10252&amp;amp;nbsp;-&amp;amp;nbsp;Allow overriding of registration and renewal price for domains in orders via admin UI and API&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Languages ====&lt;br /&gt;
CORE-10248&amp;amp;nbsp;-&amp;amp;nbsp;Hebrew language Admin and Client area translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10265&amp;amp;nbsp;-&amp;amp;nbsp;Make hard-coded language translatable in credit card template&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19622</id>
		<title>Changelog:WHMCS V7.0.0 Beta 2</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19622"/>
				<updated>2016-08-05T13:35:45Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Implemented ====&lt;br /&gt;
FEATURE-1502&amp;amp;nbsp;-&amp;amp;nbsp;Use SSL for all client facing page requests when SSL is enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Maintenance ====&lt;br /&gt;
CORE-8945&amp;amp;nbsp;-&amp;amp;nbsp;Prevent erroneous default payment method changed log entry on client profile save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9285&amp;amp;nbsp;-&amp;amp;nbsp;Only run QuoteCreated hook after quote has been fully saved&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9590&amp;amp;nbsp;-&amp;amp;nbsp;Improve Product Addon Associated Downloads box resizing&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9759&amp;amp;nbsp;-&amp;amp;nbsp;Keep hostname separate from domain name registration on View Cart page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9830&amp;amp;nbsp;-&amp;amp;nbsp;Improve enable domain renewal orders support with Six template&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9890&amp;amp;nbsp;-&amp;amp;nbsp;Provide consistent language translation when viewing invoices using View as Client link &amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9244&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9993&amp;amp;nbsp;-&amp;amp;nbsp;Ensure password verification failure fails gracefully when password hash is unknown&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10037&amp;amp;nbsp;-&amp;amp;nbsp;Set secure flag for session cookies when using SSL&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10096&amp;amp;nbsp;-&amp;amp;nbsp;Add whois server for .family extension&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10134&amp;amp;nbsp;-&amp;amp;nbsp;Apply Markdown to Escalation Rule replies&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10196&amp;amp;nbsp;-&amp;amp;nbsp;Pressing enter on admin client services page should save changes&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10224&amp;amp;nbsp;-&amp;amp;nbsp;Ensure eNom Namespinner Configuration Modal closes on save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10225&amp;amp;nbsp;-&amp;amp;nbsp;Improve stability of Health and Updates page when an SSL URL is defined&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10226&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Second Level TLD availability displays correctly in Spotlight TLDs&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10228&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Health and Updates are sorted by severity&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10229&amp;amp;nbsp;-&amp;amp;nbsp;Allow users to step backwards within setup wizard&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10230&amp;amp;nbsp;-&amp;amp;nbsp;Email templates should always be stored without entity encoding&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10235&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX when editing a ticket reply&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10236&amp;amp;nbsp;-&amp;amp;nbsp;Setup Wizard language defaults to Arabic under certain conditions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10239&amp;amp;nbsp;-&amp;amp;nbsp;Allow user to trigger invoice mark paid routine for Unpaid invoices with zero balance due&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10240&amp;amp;nbsp;-&amp;amp;nbsp;Report printable view should retain print mode when altering filter&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10241&amp;amp;nbsp;-&amp;amp;nbsp;Intelligent search should allow searching by invoice number for invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10247&amp;amp;nbsp;-&amp;amp;nbsp;Improve wording of final step of Setup Wizard  &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10253&amp;amp;nbsp;-&amp;amp;nbsp;Improve image display uploaded from Setup Wizard in system emails&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10255&amp;amp;nbsp;-&amp;amp;nbsp;Add trusted_dir to Smarty Security Policy&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10256&amp;amp;nbsp;-&amp;amp;nbsp;Use logo uploaded via Setup Wizard for PDF invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10261&amp;amp;nbsp;-&amp;amp;nbsp;Ensure new invoice will generate on upgrade of product for which renewal invoice has already been generated&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-7163&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10263&amp;amp;nbsp;-&amp;amp;nbsp;Remove unnecessary warnings when saving addon modules configuring settings&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10267&amp;amp;nbsp;-&amp;amp;nbsp;Ensure server module screen displays FriendlyName and default values for fields&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Modules ====&lt;br /&gt;
MODULE-6215&amp;amp;nbsp;-&amp;amp;nbsp;OVH module update to support .fr domains&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6388&amp;amp;nbsp;-&amp;amp;nbsp;[PayPal] Pass new service price for service when upgrading configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6423&amp;amp;nbsp;-&amp;amp;nbsp;InternetSecure: No longer ship module due to service discontinuation&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6428&amp;amp;nbsp;-&amp;amp;nbsp;WorldPay FuturePay: Allow viewing token via credit card modal without credit cards being enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10151&amp;amp;nbsp;-&amp;amp;nbsp;FreeRadius module MySQL updates &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== API ====&lt;br /&gt;
CORE-10252&amp;amp;nbsp;-&amp;amp;nbsp;Allow overriding of registration and renewal price for domains in orders via admin UI and API&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Languages ====&lt;br /&gt;
CORE-10248&amp;amp;nbsp;-&amp;amp;nbsp;Hebrew language Admin and Client area translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10265&amp;amp;nbsp;-&amp;amp;nbsp;Make hard-coded language translatable in credit card template&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19618</id>
		<title>Changelog:WHMCS V7.0.0 Beta 2</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19618"/>
				<updated>2016-08-05T13:34:56Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Maintenance */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Implemented ====&lt;br /&gt;
FEATURE-1502&amp;amp;nbsp;-&amp;amp;nbsp;Use SSL for all client facing page requests when SSL is enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Maintenance ====&lt;br /&gt;
CORE-8945&amp;amp;nbsp;-&amp;amp;nbsp;Prevent erroneous default payment method changed log entry on client profile save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9285&amp;amp;nbsp;-&amp;amp;nbsp;Only run QuoteCreated hook after quote has been fully saved&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9590&amp;amp;nbsp;-&amp;amp;nbsp;Improve Product Addon Associated Downloads box resizing&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9759&amp;amp;nbsp;-&amp;amp;nbsp;Keep hostname separate from domain name registration on View Cart page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9830&amp;amp;nbsp;-&amp;amp;nbsp;Improve enable domain renewal orders support with Six template&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9890&amp;amp;nbsp;-&amp;amp;nbsp;Provide consistent language translation when viewing invoices using View as Client link &amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9244&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9993&amp;amp;nbsp;-&amp;amp;nbsp;Ensure password verification failure fails gracefully when password hash is unknown&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10037&amp;amp;nbsp;-&amp;amp;nbsp;Set secure flag for session cookies when using SSL&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10096&amp;amp;nbsp;-&amp;amp;nbsp;Add whois server for .family extension&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10134&amp;amp;nbsp;-&amp;amp;nbsp;Apply Markdown to Escalation Rule replies&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10196&amp;amp;nbsp;-&amp;amp;nbsp;Pressing enter on admin client services page should save changes&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10224&amp;amp;nbsp;-&amp;amp;nbsp;Ensure eNom Namespinner Configuration Modal closes on save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10225&amp;amp;nbsp;-&amp;amp;nbsp;Improve stability of Health and Updates page when an SSL URL is defined&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10226&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Second Level TLD availability displays correctly in Spotlight TLDs&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10228&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Health and Updates are sorted by severity&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10229&amp;amp;nbsp;-&amp;amp;nbsp;Allow users to step backwards within setup wizard&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10230&amp;amp;nbsp;-&amp;amp;nbsp;Email templates should always be stored without entity encoding&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10235&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX when editing a ticket reply&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10236&amp;amp;nbsp;-&amp;amp;nbsp;Setup Wizard language defaults to Arabic under certain conditions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10239&amp;amp;nbsp;-&amp;amp;nbsp;Allow user to trigger invoice mark paid routine for Unpaid invoices with zero balance due&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10240&amp;amp;nbsp;-&amp;amp;nbsp;Report printable view should retain print mode when altering filter&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10241&amp;amp;nbsp;-&amp;amp;nbsp;Intelligent search should allow searching by invoice number for invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10247&amp;amp;nbsp;-&amp;amp;nbsp;Improve wording of final step of Setup Wizard  &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10253&amp;amp;nbsp;-&amp;amp;nbsp;Improve image display uploaded from Setup Wizard in system emails&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10255&amp;amp;nbsp;-&amp;amp;nbsp;Add trusted_dir to Smarty Security Policy&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10256&amp;amp;nbsp;-&amp;amp;nbsp;Use logo uploaded via Setup Wizard for PDF invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10261&amp;amp;nbsp;-&amp;amp;nbsp;Ensure new invoice will generate on upgrade of product for which renewal invoice has already been generated&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-7163&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10263&amp;amp;nbsp;-&amp;amp;nbsp;Remove unnecessary warnings when saving addon modules configuring settings&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10267&amp;amp;nbsp;-&amp;amp;nbsp;Ensure server module screen displays FriendlyName and default values for fields&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Modules ====&lt;br /&gt;
MODULE-6215&amp;amp;nbsp;-&amp;amp;nbsp;OVH module update to support .fr domains&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6388&amp;amp;nbsp;-&amp;amp;nbsp;[PayPal] Pass new service price for service when upgrading configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6423&amp;amp;nbsp;-&amp;amp;nbsp;InternetSecure: No longer ship module due to service discontinuation&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6428&amp;amp;nbsp;-&amp;amp;nbsp;WorldPay FuturePay: Allow viewing token via credit card modal without credit cards being enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10151&amp;amp;nbsp;-&amp;amp;nbsp;FreeRadius module MySQL updates &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== API ====&lt;br /&gt;
CORE-10252&amp;amp;nbsp;-&amp;amp;nbsp;Allow overriding of registration and renewal price for domains in orders via admin UI and API&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Languages ====&lt;br /&gt;
CORE-10248&amp;amp;nbsp;-&amp;amp;nbsp;Hebrew language Admin and Client area translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10265&amp;amp;nbsp;-&amp;amp;nbsp;Make hard-coded language translatable in credit card template&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Release_Notes&amp;diff=19614</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Release_Notes&amp;diff=19614"/>
				<updated>2016-08-05T13:33:56Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;table class=&amp;quot;table table-striped&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;'''Version Number'''&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;'''First Release Date'''&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;'''Release Notes'''&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 7.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;22nd July 2016&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 7.0 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 6.3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;29th March 2016&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 6.3 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 6.2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;25th November 2015&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 6.2 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 6.1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;10th September 2015&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 6.1 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 6.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;15th April 2015&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 6.0 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 5.3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;27th September 2013&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 5.3 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 5.2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;1st February 2013&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 5.2 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 5.1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;11th May 2012&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 5.1 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 5.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;7th October 2011&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 5.0 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 4.5&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;19th April 2011&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 4.5 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 4.4&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;1st December 2010&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 4.4 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 4.3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;20th July 2010&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 4.3 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 4.2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;5th February 2010&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 4.2 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 4.1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;26th August 2009&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 4.1 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Version 4.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;6th May 2009&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[[Version 4.0 Release Notes|View Release Notes]]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;docs-related-pages&amp;quot;&amp;gt;[[Security Levels]] | [http://blog.whmcs.com/?t=106987 About Release Numbering]&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19606</id>
		<title>Changelog:WHMCS V7.0.0 Beta 2</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19606"/>
				<updated>2016-08-05T13:30:25Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Implemented ====&lt;br /&gt;
FEATURE-1502&amp;amp;nbsp;-&amp;amp;nbsp;Use SSL for all client facing page requests when SSL is enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Maintenance ====&lt;br /&gt;
CORE-8945&amp;amp;nbsp;-&amp;amp;nbsp;Prevent erroneous default payment method changed log entry on client profile save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9285&amp;amp;nbsp;-&amp;amp;nbsp;Only run QuoteCreated hook after quote has been fully saved&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9590&amp;amp;nbsp;-&amp;amp;nbsp;Improve Product Addon Associated Downloads box resizing&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9759&amp;amp;nbsp;-&amp;amp;nbsp;Keep hostname separate from domain name registration on View Cart page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9830&amp;amp;nbsp;-&amp;amp;nbsp;Improve enable domain renewal orders support with Six template&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9890&amp;amp;nbsp;-&amp;amp;nbsp;Provide consistent language translation when viewing invoices using View as Client link &amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9244&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9993&amp;amp;nbsp;-&amp;amp;nbsp;Ensure password verification failure fails gracefully when password hash is unknown&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10037&amp;amp;nbsp;-&amp;amp;nbsp;Set secure flag for session cookies when using SSL&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10096&amp;amp;nbsp;-&amp;amp;nbsp;Add whois server for .family extension&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10134&amp;amp;nbsp;-&amp;amp;nbsp;Apply Markdown to Escalation Rule replies&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10196&amp;amp;nbsp;-&amp;amp;nbsp;Pressing enter on admin client services page should save changes&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10224&amp;amp;nbsp;-&amp;amp;nbsp;Ensure eNom Namespinner Configuration Modal closes on save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10225&amp;amp;nbsp;-&amp;amp;nbsp;Improve stability of Health and Updates page when an SSL URL is defined&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10226&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Second Level TLD availability displays correctly in Spotlight TLDs&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10228&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Health and Updates are sorted by severity&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10229&amp;amp;nbsp;-&amp;amp;nbsp;Allow users to step backwards within setup wizard&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10230&amp;amp;nbsp;-&amp;amp;nbsp;Email templates should always be stored without entity encoding&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10235&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX when editing a ticket reply&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10236&amp;amp;nbsp;-&amp;amp;nbsp;Setup Wizard language defaults to Arabic under certain conditions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10239&amp;amp;nbsp;-&amp;amp;nbsp;Allow user to trigger invoice mark paid routine for Unpaid invoices with zero balance due&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10240&amp;amp;nbsp;-&amp;amp;nbsp;Report printable view should retain print mode when altering filter&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10241&amp;amp;nbsp;-&amp;amp;nbsp;Intelligent search should allow searching by invoice number for invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10247&amp;amp;nbsp;-&amp;amp;nbsp;Improve wording of final step of Setup Wizard  &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10253&amp;amp;nbsp;-&amp;amp;nbsp;Improve image display uploaded from Setup Wizard in system emails&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10255&amp;amp;nbsp;-&amp;amp;nbsp;Add trusted_dir to Smarty Security Policy&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10256&amp;amp;nbsp;-&amp;amp;nbsp;Use logo uploaded via Setup Wizard for PDF invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10261&amp;amp;nbsp;-&amp;amp;nbsp;Ensure new invoice will generate on upgrade of product for which renewal invoice has already been generated&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-7163&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10263&amp;amp;nbsp;-&amp;amp;nbsp;Remove unnecessary warnings when saving addon modules configuring settings&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10267&amp;amp;nbsp;-&amp;amp;nbsp;Ensure server module screen displays FriendlyName and default values for fields&amp;lt;br /&amp;gt;&lt;br /&gt;
DEV-342&amp;amp;nbsp;-&amp;amp;nbsp;Implement updater maintenance message display during update process&amp;lt;br /&amp;gt;&lt;br /&gt;
VSIX-832&amp;amp;nbsp;-&amp;amp;nbsp;Language fallback now matches language specified in general settings&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Modules ====&lt;br /&gt;
MODULE-6215&amp;amp;nbsp;-&amp;amp;nbsp;OVH module update to support .fr domains&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6388&amp;amp;nbsp;-&amp;amp;nbsp;[PayPal] Pass new service price for service when upgrading configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6423&amp;amp;nbsp;-&amp;amp;nbsp;InternetSecure: No longer ship module due to service discontinuation&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6428&amp;amp;nbsp;-&amp;amp;nbsp;WorldPay FuturePay: Allow viewing token via credit card modal without credit cards being enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10151&amp;amp;nbsp;-&amp;amp;nbsp;FreeRadius module MySQL updates &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== API ====&lt;br /&gt;
CORE-10252&amp;amp;nbsp;-&amp;amp;nbsp;Allow overriding of registration and renewal price for domains in orders via admin UI and API&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Languages ====&lt;br /&gt;
CORE-10248&amp;amp;nbsp;-&amp;amp;nbsp;Hebrew language Admin and Client area translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10265&amp;amp;nbsp;-&amp;amp;nbsp;Make hard-coded language translatable in credit card template&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19602</id>
		<title>Changelog:WHMCS V7.0.0 Beta 2</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_2&amp;diff=19602"/>
				<updated>2016-08-05T13:29:19Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Implemented ====&lt;br /&gt;
FEATURE-1502&amp;amp;nbsp;-&amp;amp;nbsp;Use SSL for all client facing page requests when SSL is enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Maintenance ====&lt;br /&gt;
CORE-8945&amp;amp;nbsp;-&amp;amp;nbsp;Prevent erroneous default payment method changed log entry on client profile save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9285&amp;amp;nbsp;-&amp;amp;nbsp;Only run QuoteCreated hook after quote has been fully saved&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9590&amp;amp;nbsp;-&amp;amp;nbsp;Improve Product Addon Associated Downloads box resizing&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9759&amp;amp;nbsp;-&amp;amp;nbsp;Keep hostname separate from domain name registration on View Cart page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9830&amp;amp;nbsp;-&amp;amp;nbsp;Improve enable domain renewal orders support with Six template&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9890&amp;amp;nbsp;-&amp;amp;nbsp;Provide consistent language translation when viewing invoices using View as Client link &amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9244&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9993&amp;amp;nbsp;-&amp;amp;nbsp;Ensure password verification failure fails gracefully when password hash is unknown&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10037&amp;amp;nbsp;-&amp;amp;nbsp;Set secure flag for session cookies when using SSL&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10096&amp;amp;nbsp;-&amp;amp;nbsp;Add whois server for .family extension&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10134&amp;amp;nbsp;-&amp;amp;nbsp;Apply Markdown to Escalation Rule replies&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10196&amp;amp;nbsp;-&amp;amp;nbsp;Pressing enter on admin client services page should save changes&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10224&amp;amp;nbsp;-&amp;amp;nbsp;Ensure eNom Namespinner Configuration Modal closes on save&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10225&amp;amp;nbsp;-&amp;amp;nbsp;Improve stability of Health and Updates page when an SSL URL is defined&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10226&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Second Level TLD availability displays correctly in Spotlight TLDs&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10228&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Health and Updates are sorted by severity&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10229&amp;amp;nbsp;-&amp;amp;nbsp;Allow users to step backwards within setup wizard&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10230&amp;amp;nbsp;-&amp;amp;nbsp;Email templates should always be stored without entity encoding&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10235&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX when editing a ticket reply&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10236&amp;amp;nbsp;-&amp;amp;nbsp;Setup Wizard language defaults to Arabic under certain conditions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10239&amp;amp;nbsp;-&amp;amp;nbsp;Allow user to trigger invoice mark paid routine for Unpaid invoices with zero balance due&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10240&amp;amp;nbsp;-&amp;amp;nbsp;Report printable view should retain print mode when altering filter&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10241&amp;amp;nbsp;-&amp;amp;nbsp;Intelligent search should allow searching by invoice number for invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10247&amp;amp;nbsp;-&amp;amp;nbsp;Improve wording of final step of Setup Wizard  &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10253&amp;amp;nbsp;-&amp;amp;nbsp;Improve image display uploaded from Setup Wizard in system emails&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10255&amp;amp;nbsp;-&amp;amp;nbsp;Add trusted_dir to Smarty Security Policy&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10256&amp;amp;nbsp;-&amp;amp;nbsp;Use logo uploaded via Setup Wizard for PDF invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10261&amp;amp;nbsp;-&amp;amp;nbsp;Ensure new invoice will generate on upgrade of product for which renewal invoice has already been generated&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-7163&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10263&amp;amp;nbsp;-&amp;amp;nbsp;Remove unnecessary warnings when saving addon modules configuring settings&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10267&amp;amp;nbsp;-&amp;amp;nbsp;Ensure server module screen displays FriendlyName and default values for fields&amp;lt;br /&amp;gt;&lt;br /&gt;
DEV-342&amp;amp;nbsp;-&amp;amp;nbsp;Implement updater maintenance message display during update process&amp;lt;br /&amp;gt;&lt;br /&gt;
VSIX-832&amp;amp;nbsp;-&amp;amp;nbsp;Language fallback now matches language specified in general settings&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Modules ====&lt;br /&gt;
MODULE-6215&amp;amp;nbsp;-&amp;amp;nbsp;OVH module update to support .fr domains&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6388&amp;amp;nbsp;-&amp;amp;nbsp;[PayPal] Pass new service price for service when upgrading configurable options&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6423&amp;amp;nbsp;-&amp;amp;nbsp;InternetSecure: No longer ship module due to service discontinuation&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6428&amp;amp;nbsp;-&amp;amp;nbsp;WorldPay FuturePay: Allow viewing token via credit card modal without credit cards being enabled&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10151&amp;amp;nbsp;-&amp;amp;nbsp;FreeRadius module MySQL updates &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Languages ====&lt;br /&gt;
CORE-10248&amp;amp;nbsp;-&amp;amp;nbsp;Hebrew language Admin and Client area translation &amp;amp;amp; improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10265&amp;amp;nbsp;-&amp;amp;nbsp;Make hard-coded language translatable in credit card template&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== API ====&lt;br /&gt;
CORE-10252&amp;amp;nbsp;-&amp;amp;nbsp;Allow overriding of registration and renewal price for domains in orders via admin UI and API&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_1&amp;diff=19598</id>
		<title>Changelog:WHMCS V7.0.0 Beta 1</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_1&amp;diff=19598"/>
				<updated>2016-08-05T13:24:32Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Implemented ====&lt;br /&gt;
FEATURE-1058&amp;amp;nbsp;-&amp;amp;nbsp;Featured Spotlight TLD Promotion&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1080&amp;amp;nbsp;-&amp;amp;nbsp;New update notification display in admin header&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1458&amp;amp;nbsp;-&amp;amp;nbsp;APIs for setting configuration values and activating/configuring modules&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1459&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for new installation configuration&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1460&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for configuring General Settings&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1461&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for configuring Payment Gateways&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1462&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for configuring Domains&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1463&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for configuring Servers&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1464&amp;amp;nbsp;-&amp;amp;nbsp;Shortcut to access Quick Start Setup Wizard&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1494&amp;amp;nbsp;-&amp;amp;nbsp;Simple Product Configuration Mode for Provisioning Modules Module Settings&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1499&amp;amp;nbsp;-&amp;amp;nbsp;Support for Customisations/Overrides to WHOIS Servers&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1505&amp;amp;nbsp;-&amp;amp;nbsp;Support for Customisations/Overrides to Additional Domain Fields&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1512&amp;amp;nbsp;-&amp;amp;nbsp;Support for Customisations/Overrides to Countries&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1543&amp;amp;nbsp;-&amp;amp;nbsp;Optimisations to PayPal Integration for Improved Conversion Rates&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Maintenance ====&lt;br /&gt;
ADDON-5988&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Bulk Pricing Updater addon respects &amp;amp;#039;ID Protection&amp;amp;#039; filter on domains&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8188&amp;amp;nbsp;-&amp;amp;nbsp;Improve XCache compatibility with viewing invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8910&amp;amp;nbsp;-&amp;amp;nbsp;Improve widget placement customization on the admin homepage&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9112&amp;amp;nbsp;-&amp;amp;nbsp;Properly hide &amp;amp;#039;default gateway&amp;amp;#039; option from client&amp;amp;#039;s profile when &amp;amp;#039;Clients Choose Gateway&amp;amp;#039; option is not ticked&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9272&amp;amp;nbsp;-&amp;amp;nbsp;Improve text wrapping support in buttons in the client area&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9458&amp;amp;nbsp;-&amp;amp;nbsp;Improve messaging when attempting to download a file while not authenticated in the client area&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9485&amp;amp;nbsp;-&amp;amp;nbsp;Ensure registrarfunctions is available when using ClientAreaCustomButtonArray in registrar modules&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9604&amp;amp;nbsp;-&amp;amp;nbsp;Improve recalculate tax option during checkout when not logged into client area&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9695&amp;amp;nbsp;-&amp;amp;nbsp;Provide consistency in the password strength checking during the order process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9696&amp;amp;nbsp;-&amp;amp;nbsp;Convert mixed case capitalization when &amp;amp;#039;Use My Own Domain&amp;amp;#039; is selected to lower case&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9697&amp;amp;nbsp;-&amp;amp;nbsp;Fix one time affiliate payout option to allow consistent enabling and disabling of option&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9703&amp;amp;nbsp;-&amp;amp;nbsp;Ensure quotes obey client&amp;amp;#039;s tax exempt status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9710&amp;amp;nbsp;-&amp;amp;nbsp;Ensure referral status is properly styled for all languages in client area affiliate page&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-10052&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9778&amp;amp;nbsp;-&amp;amp;nbsp;Ensure OpenID &amp;amp;#039;cancel&amp;amp;#039; and &amp;amp;#039;return to cPanel&amp;amp;#039; links function properly&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9810&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Addon Name is available in Addon Welcome email&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9815&amp;amp;nbsp;-&amp;amp;nbsp;Improve formatting of SSL order date in SSL Configuration Process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9845&amp;amp;nbsp;-&amp;amp;nbsp;Disable &amp;amp;quot;Renew Now&amp;amp;quot; homepage button if renewal is disabled on Domains Expiring Soon home panel&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9859&amp;amp;nbsp;-&amp;amp;nbsp;Ensure the ticket priority and status opened by guests are displayed in the default language&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9897&amp;amp;nbsp;-&amp;amp;nbsp;Improve performance of domain checker with 900+ TLD prices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9915&amp;amp;nbsp;-&amp;amp;nbsp;Improve success messaging upon saving Easy Translation fields&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9963&amp;amp;nbsp;-&amp;amp;nbsp;Preserve input values of Invoice Add Payment tab upon validation failure&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9983&amp;amp;nbsp;-&amp;amp;nbsp;Improve admin email reply processing for piped emails containing certain characters&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9989&amp;amp;nbsp;-&amp;amp;nbsp;Improve Mass Pay process to remove unnecessary Credit Applied/Removed transaction history&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9992&amp;amp;nbsp;-&amp;amp;nbsp;Update .me whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9995&amp;amp;nbsp;-&amp;amp;nbsp;Increase size of group for Subscription ID on Client Hosting/Domain Pages&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9997&amp;amp;nbsp;-&amp;amp;nbsp;Explicity define the response type for markdown preview requests&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10000&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Hidden Configurable Options are not shown on Order Confirmation Email&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10003&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ao whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10007&amp;amp;nbsp;-&amp;amp;nbsp;Update to .pro whois server&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: MODULE-6405&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10008&amp;amp;nbsp;-&amp;amp;nbsp;Adding any status to admin ticket filter should show all tickets&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10009&amp;amp;nbsp;-&amp;amp;nbsp;Improve the display of plain text emails&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10012&amp;amp;nbsp;-&amp;amp;nbsp;Ensure users imported with cPanel/WHM Utility can log in&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10014&amp;amp;nbsp;-&amp;amp;nbsp;Generate more user friendly passwords with reset password &amp;amp;amp; send option in client details page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10019&amp;amp;nbsp;-&amp;amp;nbsp;Add ability to enable ticket feedback request on close on a per department basis&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10023&amp;amp;nbsp;-&amp;amp;nbsp;Update .club whois match string&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10025&amp;amp;nbsp;-&amp;amp;nbsp;Extend CC expiration date support in order process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10054&amp;amp;nbsp;-&amp;amp;nbsp;Update to .pro whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10058&amp;amp;nbsp;-&amp;amp;nbsp;Resolve PHP notices generated by pop cron run&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10061&amp;amp;nbsp;-&amp;amp;nbsp;Improve domain status filtering in client area with certain languages&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10068&amp;amp;nbsp;-&amp;amp;nbsp;Improve selected currency display on mobile platforms and lower resolutions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10069&amp;amp;nbsp;-&amp;amp;nbsp;Ensure jQuery calls won&amp;amp;#039;t conflict with other JS libraries for Two-Factor Auth Activation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10086&amp;amp;nbsp;-&amp;amp;nbsp;Improve handling of Knowledge Base links that contain apostrophes&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10111&amp;amp;nbsp;-&amp;amp;nbsp;Remove client dropdown format setting&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10112&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX of Client Selectize Dropdown&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10117&amp;amp;nbsp;-&amp;amp;nbsp;Remove browser utility from Utilities menu&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10123&amp;amp;nbsp;-&amp;amp;nbsp;Create module class autoloader&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10144&amp;amp;nbsp;-&amp;amp;nbsp;Do not invoke hooks or language files in Chatstack instantiation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10147&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Fraud Check error messages appear in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10182&amp;amp;nbsp;-&amp;amp;nbsp;Do not show secure notice in shopping cart when SSL is not available&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10190&amp;amp;nbsp;-&amp;amp;nbsp;Add further protection for HTTPoxy&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10192&amp;amp;nbsp;-&amp;amp;nbsp;Add notice about free disk space required to perform an update&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Modules ====&lt;br /&gt;
MODULE-6373&amp;amp;nbsp;-&amp;amp;nbsp;[Plesk] Improve handling of connection errors on clientsservices.php&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6397&amp;amp;nbsp;-&amp;amp;nbsp;[ResellerClub] Update DNS Manager to limit DNS results to 50 per page&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6402&amp;amp;nbsp;-&amp;amp;nbsp;[EnomSSL] Only run DeleteFromCart when cart is empty&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6417&amp;amp;nbsp;-&amp;amp;nbsp;[eNom] Provide in-product guidance on creating API Tokens&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6421&amp;amp;nbsp;-&amp;amp;nbsp;[PayPal] Ensure a3 value on subscription value does not exceed 2dp&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9700&amp;amp;nbsp;-&amp;amp;nbsp;Pass serviceID value when cancelling PayPal Subscriptions on upgrade orders&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== API ====&lt;br /&gt;
CORE-8502&amp;amp;nbsp;-&amp;amp;nbsp;Improve AdminAreaPage hook functionality in populating variables&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8549&amp;amp;nbsp;-&amp;amp;nbsp;Improve API stability by allowing customization of deserialization length&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: MODULE-6261&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9639&amp;amp;nbsp;-&amp;amp;nbsp;Update Client API doesn&amp;amp;#039;t call ClientEdit Hook&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9982&amp;amp;nbsp;-&amp;amp;nbsp;Ensure API:getclientsproducts returns name value&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9986&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10042&amp;amp;nbsp;-&amp;amp;nbsp;Improve UpdateContact API support of &amp;amp;#039;password2&amp;amp;#039; parameter&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10050&amp;amp;nbsp;-&amp;amp;nbsp;Improve ClientAreaPageLogin hook &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10066&amp;amp;nbsp;-&amp;amp;nbsp;Hook ContactEdit should provide previous contact data as part of its input params&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10075&amp;amp;nbsp;-&amp;amp;nbsp;Ensure GetTickets API call does not return merged tickets&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Languages ====&lt;br /&gt;
CORE-9889&amp;amp;nbsp;-&amp;amp;nbsp;Fix German Domain Register menu item translation string&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9958&amp;amp;nbsp;-&amp;amp;nbsp;French client area translation additions and improvements&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9962&amp;amp;nbsp;-&amp;amp;nbsp;Portuguese translation additions and improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9967&amp;amp;nbsp;-&amp;amp;nbsp;English language translation additions and improvements&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10221&amp;amp;nbsp;-&amp;amp;nbsp;Spanish Language translation additions and improvement&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: ADDON-5987&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	<entry>
		<id>http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_1&amp;diff=19594</id>
		<title>Changelog:WHMCS V7.0.0 Beta 1</title>
		<link rel="alternate" type="text/html" href="http://3.19.219.109/index.php?title=Changelog:WHMCS_V7.0.0_Beta_1&amp;diff=19594"/>
				<updated>2016-08-05T13:24:02Z</updated>
		
		<summary type="html">&lt;p&gt;Cole: /* Implemented */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;[[Version 7.0 Release Notes]]&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Implemented ====&lt;br /&gt;
FEATURE-1058&amp;amp;nbsp;-&amp;amp;nbsp;Featured Spotlight TLD Promotion&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1080&amp;amp;nbsp;-&amp;amp;nbsp;New update notification display in admin header&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1458&amp;amp;nbsp;-&amp;amp;nbsp;APIs for setting configuration values and activating/configuring modules&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1459&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for new installation configuration&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1460&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for configuring General Settings&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1461&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for configuring Payment Gateways&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1462&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for configuring Domains&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1463&amp;amp;nbsp;-&amp;amp;nbsp;Quick Start Setup Wizard for configuring Servers&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1464&amp;amp;nbsp;-&amp;amp;nbsp;Shortcut to access Quick Start Setup Wizard&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1494&amp;amp;nbsp;-&amp;amp;nbsp;Simple Product Configuration Mode for Provisioning Modules Module Settings&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1499&amp;amp;nbsp;-&amp;amp;nbsp;Support for Customisations/Overrides to WHOIS Servers&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1505&amp;amp;nbsp;-&amp;amp;nbsp;Support for Customisations/Overrides to Additional Domain Fields&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1512&amp;amp;nbsp;-&amp;amp;nbsp;Support for Customisations/Overrides to Countries&amp;lt;br /&amp;gt;&lt;br /&gt;
FEATURE-1543&amp;amp;nbsp;-&amp;amp;nbsp;Optimisations to PayPal Integration for Improved Conversion Rates&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Maintenance ===&lt;br /&gt;
ADDON-5988&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Bulk Pricing Updater addon respects &amp;amp;#039;ID Protection&amp;amp;#039; filter on domains&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8188&amp;amp;nbsp;-&amp;amp;nbsp;Improve XCache compatibility with viewing invoices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8910&amp;amp;nbsp;-&amp;amp;nbsp;Improve widget placement customization on the admin homepage&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9112&amp;amp;nbsp;-&amp;amp;nbsp;Properly hide &amp;amp;#039;default gateway&amp;amp;#039; option from client&amp;amp;#039;s profile when &amp;amp;#039;Clients Choose Gateway&amp;amp;#039; option is not ticked&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9272&amp;amp;nbsp;-&amp;amp;nbsp;Improve text wrapping support in buttons in the client area&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9458&amp;amp;nbsp;-&amp;amp;nbsp;Improve messaging when attempting to download a file while not authenticated in the client area&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9485&amp;amp;nbsp;-&amp;amp;nbsp;Ensure registrarfunctions is available when using ClientAreaCustomButtonArray in registrar modules&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9604&amp;amp;nbsp;-&amp;amp;nbsp;Improve recalculate tax option during checkout when not logged into client area&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9695&amp;amp;nbsp;-&amp;amp;nbsp;Provide consistency in the password strength checking during the order process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9696&amp;amp;nbsp;-&amp;amp;nbsp;Convert mixed case capitalization when &amp;amp;#039;Use My Own Domain&amp;amp;#039; is selected to lower case&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9697&amp;amp;nbsp;-&amp;amp;nbsp;Fix one time affiliate payout option to allow consistent enabling and disabling of option&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9703&amp;amp;nbsp;-&amp;amp;nbsp;Ensure quotes obey client&amp;amp;#039;s tax exempt status&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9710&amp;amp;nbsp;-&amp;amp;nbsp;Ensure referral status is properly styled for all languages in client area affiliate page&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-10052&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9778&amp;amp;nbsp;-&amp;amp;nbsp;Ensure OpenID &amp;amp;#039;cancel&amp;amp;#039; and &amp;amp;#039;return to cPanel&amp;amp;#039; links function properly&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9810&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Addon Name is available in Addon Welcome email&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9815&amp;amp;nbsp;-&amp;amp;nbsp;Improve formatting of SSL order date in SSL Configuration Process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9845&amp;amp;nbsp;-&amp;amp;nbsp;Disable &amp;amp;quot;Renew Now&amp;amp;quot; homepage button if renewal is disabled on Domains Expiring Soon home panel&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9859&amp;amp;nbsp;-&amp;amp;nbsp;Ensure the ticket priority and status opened by guests are displayed in the default language&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9897&amp;amp;nbsp;-&amp;amp;nbsp;Improve performance of domain checker with 900+ TLD prices&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9915&amp;amp;nbsp;-&amp;amp;nbsp;Improve success messaging upon saving Easy Translation fields&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9963&amp;amp;nbsp;-&amp;amp;nbsp;Preserve input values of Invoice Add Payment tab upon validation failure&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9983&amp;amp;nbsp;-&amp;amp;nbsp;Improve admin email reply processing for piped emails containing certain characters&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9989&amp;amp;nbsp;-&amp;amp;nbsp;Improve Mass Pay process to remove unnecessary Credit Applied/Removed transaction history&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9992&amp;amp;nbsp;-&amp;amp;nbsp;Update .me whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9995&amp;amp;nbsp;-&amp;amp;nbsp;Increase size of group for Subscription ID on Client Hosting/Domain Pages&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9997&amp;amp;nbsp;-&amp;amp;nbsp;Explicity define the response type for markdown preview requests&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10000&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Hidden Configurable Options are not shown on Order Confirmation Email&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10003&amp;amp;nbsp;-&amp;amp;nbsp;Update to .ao whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10007&amp;amp;nbsp;-&amp;amp;nbsp;Update to .pro whois server&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: MODULE-6405&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10008&amp;amp;nbsp;-&amp;amp;nbsp;Adding any status to admin ticket filter should show all tickets&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10009&amp;amp;nbsp;-&amp;amp;nbsp;Improve the display of plain text emails&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10012&amp;amp;nbsp;-&amp;amp;nbsp;Ensure users imported with cPanel/WHM Utility can log in&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10014&amp;amp;nbsp;-&amp;amp;nbsp;Generate more user friendly passwords with reset password &amp;amp;amp; send option in client details page&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10019&amp;amp;nbsp;-&amp;amp;nbsp;Add ability to enable ticket feedback request on close on a per department basis&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10023&amp;amp;nbsp;-&amp;amp;nbsp;Update .club whois match string&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10025&amp;amp;nbsp;-&amp;amp;nbsp;Extend CC expiration date support in order process&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10054&amp;amp;nbsp;-&amp;amp;nbsp;Update to .pro whois server&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10058&amp;amp;nbsp;-&amp;amp;nbsp;Resolve PHP notices generated by pop cron run&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10061&amp;amp;nbsp;-&amp;amp;nbsp;Improve domain status filtering in client area with certain languages&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10068&amp;amp;nbsp;-&amp;amp;nbsp;Improve selected currency display on mobile platforms and lower resolutions&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10069&amp;amp;nbsp;-&amp;amp;nbsp;Ensure jQuery calls won&amp;amp;#039;t conflict with other JS libraries for Two-Factor Auth Activation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10086&amp;amp;nbsp;-&amp;amp;nbsp;Improve handling of Knowledge Base links that contain apostrophes&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10111&amp;amp;nbsp;-&amp;amp;nbsp;Remove client dropdown format setting&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10112&amp;amp;nbsp;-&amp;amp;nbsp;Improve UX of Client Selectize Dropdown&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10117&amp;amp;nbsp;-&amp;amp;nbsp;Remove browser utility from Utilities menu&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10123&amp;amp;nbsp;-&amp;amp;nbsp;Create module class autoloader&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10144&amp;amp;nbsp;-&amp;amp;nbsp;Do not invoke hooks or language files in Chatstack instantiation&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10147&amp;amp;nbsp;-&amp;amp;nbsp;Ensure Fraud Check error messages appear in all scenarios&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10182&amp;amp;nbsp;-&amp;amp;nbsp;Do not show secure notice in shopping cart when SSL is not available&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10190&amp;amp;nbsp;-&amp;amp;nbsp;Add further protection for HTTPoxy&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10192&amp;amp;nbsp;-&amp;amp;nbsp;Add notice about free disk space required to perform an update&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Modules ===&lt;br /&gt;
MODULE-6373&amp;amp;nbsp;-&amp;amp;nbsp;[Plesk] Improve handling of connection errors on clientsservices.php&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6397&amp;amp;nbsp;-&amp;amp;nbsp;[ResellerClub] Update DNS Manager to limit DNS results to 50 per page&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6402&amp;amp;nbsp;-&amp;amp;nbsp;[EnomSSL] Only run DeleteFromCart when cart is empty&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6417&amp;amp;nbsp;-&amp;amp;nbsp;[eNom] Provide in-product guidance on creating API Tokens&amp;lt;br /&amp;gt;&lt;br /&gt;
MODULE-6421&amp;amp;nbsp;-&amp;amp;nbsp;[PayPal] Ensure a3 value on subscription value does not exceed 2dp&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9700&amp;amp;nbsp;-&amp;amp;nbsp;Pass serviceID value when cancelling PayPal Subscriptions on upgrade orders&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== API ===&lt;br /&gt;
CORE-8502&amp;amp;nbsp;-&amp;amp;nbsp;Improve AdminAreaPage hook functionality in populating variables&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-8549&amp;amp;nbsp;-&amp;amp;nbsp;Improve API stability by allowing customization of deserialization length&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: MODULE-6261&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9639&amp;amp;nbsp;-&amp;amp;nbsp;Update Client API doesn&amp;amp;#039;t call ClientEdit Hook&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9982&amp;amp;nbsp;-&amp;amp;nbsp;Ensure API:getclientsproducts returns name value&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: CORE-9986&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10042&amp;amp;nbsp;-&amp;amp;nbsp;Improve UpdateContact API support of &amp;amp;#039;password2&amp;amp;#039; parameter&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10050&amp;amp;nbsp;-&amp;amp;nbsp;Improve ClientAreaPageLogin hook &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10066&amp;amp;nbsp;-&amp;amp;nbsp;Hook ContactEdit should provide previous contact data as part of its input params&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10075&amp;amp;nbsp;-&amp;amp;nbsp;Ensure GetTickets API call does not return merged tickets&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Languages ===&lt;br /&gt;
CORE-9889&amp;amp;nbsp;-&amp;amp;nbsp;Fix German Domain Register menu item translation string&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9958&amp;amp;nbsp;-&amp;amp;nbsp;French client area translation additions and improvements&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9962&amp;amp;nbsp;-&amp;amp;nbsp;Portuguese translation additions and improvements &amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-9967&amp;amp;nbsp;-&amp;amp;nbsp;English language translation additions and improvements&amp;lt;br /&amp;gt;&lt;br /&gt;
CORE-10221&amp;amp;nbsp;-&amp;amp;nbsp;Spanish Language translation additions and improvement&amp;lt;br /&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;Also known as: ADDON-5987&amp;lt;br /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cole</name></author>	</entry>

	</feed>