Difference between revisions of "Version 8.4 Release Notes"

From WHMCS Documentation

(Created page with "<div class="docs-alert-info" style="max-width:370px;"> <span class="title">Release Information</span> <br /> Version: 8.4<br /> Release Type: Beta<br /> Latest Update: 1st Dec...")
 
 
(12 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<br />
 
<br />
 
Version: 8.4<br />
 
Version: 8.4<br />
Release Type: Beta<br />
+
Release Type: Maintenance<br />
Latest Update: 1st December 2021<br />
+
Latest Update: 21st February 2022<br />
 
Distribution Types: Full and Via Automatic Updater
 
Distribution Types: Full and Via Automatic Updater
 
</div>
 
</div>
Line 11: Line 11:
 
   <onlyinclude>
 
   <onlyinclude>
 
<table class="table table-striped">
 
<table class="table table-striped">
<tr><td>8.3.0</td><td>Beta 1</td><td>1st December 2021</td></tr>
+
<tr><td>8.4.0</td><td>Beta 1</td><td>1st December 2021</td></tr>
 +
<tr><td>8.4.0</td><td>Release Candidate 1</td><td>17th December 2021</td></tr>
 +
<tr><td>8.4.0</td><td>General Availability 1</td><td>18th January 2022</td></tr>
 +
<tr><td>8.4.1</td><td>Maintenance</td><td>21st February 2022</td></tr>
 
</table>
 
</table>
 
</onlyinclude>
 
</onlyinclude>
Line 45: Line 48:
  
 
Clients can now easily copy-and-paste their site seal code from directly within the WHMCS Client Area. They can then add that code to their HTML pages to display their site seal anywhere on their website.
 
Clients can now easily copy-and-paste their site seal code from directly within the WHMCS Client Area. They can then add that code to their HTML pages to display their site seal anywhere on their website.
 +
 +
[https://marketplace.whmcs.com/help/connect/kb/digicert_ssl_certificates/managing_orders/how_do_i_get_my_site_seal Learn more...]
  
 
===Optimized Merchandising for SSL Products===
 
===Optimized Merchandising for SSL Products===
  
You can now add recommendation labels to designate featured MarketConnect SSL products to make sure that your clients find your highest-margin SSL products first.
+
You can now add recommendation labels to designate featured [[MarketConnect]] SSL products to make sure that your clients find your highest-margin SSL products first.
  
 
===OX App Suite Email Aliases===
 
===OX App Suite Email Aliases===
  
Clients can now create and manage email aliases for OX App Suite via MarketConnect in the WHMCS Client Area.
+
Clients can now create and manage email aliases for OX App Suite via [[MarketConnect]] in the WHMCS Client Area.
 +
 
 +
[https://marketplace.whmcs.com/help/connect/kb/ox_app_suite/getting_started/what_is_an_email_alias Learn more...]
  
 
===Faster WordPress® Checkout===
 
===Faster WordPress® Checkout===
Line 58: Line 65:
 
The new '''Event Handling''' setting lets you control how WHMCS handles events like installing and provisioning WordPress, allowing for faster checkout speeds for WordPress purchases.
 
The new '''Event Handling''' setting lets you control how WHMCS handles events like installing and provisioning WordPress, allowing for faster checkout speeds for WordPress purchases.
  
[[Other_Tab|Learn more...]]
+
[[Other_Tab#Event_Handling|Learn more...]]
  
 
== Deprecation and Removal Notices ==
 
== Deprecation and Removal Notices ==
 
''None''
 
  
== Template ==
+
===SagePay Module Deprecation and Updates===
 +
 
 +
Due to anticipated changes from Opayo (formerly Sage Pay) to their SCA and 3DSv2 API implementations, we have updated the related [[Payment Gateways|payment gateway]] modules.
 +
 
 +
# If you use the '''[[SagePay]]''' or '''[[SagePay Repeats]]''' modules, you can continue using them with no further action. These modules are fully compatible with both the old and new API implementations.
 +
# The existing '''SagePay Tokens''' module will not function with the new API implementation. To address this issue, WHMCS 8.4.1 includes a new '''[[SagePay Tokens v2]]''' module.
 +
 
 +
In order to continue using '''SagePay Tokens''' as a payment gateway, you must migrate to this new module.
 +
 
 +
These changes alter the tokenization services that Opayo (and therefore the '''SagePay Tokens v2''' module) offer:
 +
 
 +
# The gateway can only tokenize and store credit cards when the client is making a payment.
 +
# Opayo has discontinued the card vault feature.
 +
 
 +
[https://help.whmcs.com/m/payments/l/1528851-sagepay-tokens-deprecation-and-sagepay-tokens-v2 Learn more...]
 +
 
 +
== Templates ==
  
 
For a list of changed files and a graphical view of the exact changes, please refer to the GitHub repositories below.
 
For a list of changed files and a graphical view of the exact changes, please refer to the GitHub repositories below.
Line 70: Line 91:
 
===Twenty-One Theme===
 
===Twenty-One Theme===
  
The following link provides a comparison of changes between 8.3.2 and 8.4.0 (Beta 1):
+
The following link provides a comparison of changes between 8.3.2 and 8.4.1 (Maintenance):
  
https://github.com/WHMCS/templates-twenty-one/compare/v8.3.2-release.1...v8.4.0-beta.1
+
https://github.com/WHMCS/templates-twenty-one/compare/v8.3.2-release.1...v8.4.1-release.1
  
 
=== Six Theme ===
 
=== Six Theme ===
 
          
 
          
The following link provides a comparison of changes between 8.3.2 and 8.4.0 (Beta 1):
+
The following link provides a comparison of changes between 8.3.2 and 8.4.1 (Maintenance):
  
https://github.com/WHMCS/templates-six/compare/v8.3.2-release.1...v8.4.0-beta.1
+
https://github.com/WHMCS/templates-six/compare/v8.3.2-release.1...v8.4.1-release.1
  
 
=== Standard Cart Order Form ===
 
=== Standard Cart Order Form ===
 
          
 
          
The following link provides a comparison of changes between 8.3.2 and 8.4.0 (Beta 1):
+
The following link provides a comparison of changes between 8.3.2 and 8.4.1 (Maintenance):
  
https://github.com/WHMCS/orderforms-standard_cart/compare/v8.3.2-release.1...v8.4.0-beta.1
+
https://github.com/WHMCS/orderforms-standard_cart/compare/v8.3.2-release.1...v8.4.1-release.1
  
 
== Changelog ==
 
== Changelog ==
 
* [[Changelog:WHMCS_V8.4.0_Beta_1|Version 8.4.0 Beta 1]]
 
* [[Changelog:WHMCS_V8.4.0_Beta_1|Version 8.4.0 Beta 1]]
 +
* [[Changelog:WHMCS_V8.4.0_RC_1|Version 8.4.0 RC 1]]
 +
* [[Changelog:WHMCS_V8.4.0_GA|Version 8.4.0 GA]]
 +
* [[Changelog:WHMCS_V8.4.1|Version 8.4.1 Maintenance]]

Latest revision as of 20:30, 11 May 2022

Release Information
Version: 8.4
Release Type: Maintenance
Latest Update: 21st February 2022
Distribution Types: Full and Via Automatic Updater

Version History

8.4.0Beta 11st December 2021
8.4.0Release Candidate 117th December 2021
8.4.0General Availability 118th January 2022
8.4.1Maintenance21st February 2022


Download

Download the latest version of WHMCS from https://download.whmcs.com/

Upgrade Process

WHMCS 8.0 and above requires PHP 7.2 or later. WHMCS 8.0 introduces support for PHP 7.4. Earlier versions of WHMCS do not support PHP 7.4.

You will only see the WHMCS 8 updates within the Automatic Updater if you are running on PHP 7.2 or later. If you are running PHP 7.1 or earlier, to update to WHMCS 8 via the Automatic Updater, you will first need to upgrade to PHP 7.2 or PHP 7.3, and then check for updates and perform the update.

Once you are running WHMCS 8, you can upgrade to PHP 7.4.

View Standard Upgrade Steps

Automatic Updating

If you are running WHMCS 7.0 or later, you can use the built-in Automatic Update utility.

Go to Utilities > Update WHMCS to begin the process.

If the update was released recently, you may need to click Check for Updates before the update will be available.

For more information about updating, refer to the Automatic Updater documentation.

Release Notes

Download Site Seals

Clients can now easily copy-and-paste their site seal code from directly within the WHMCS Client Area. They can then add that code to their HTML pages to display their site seal anywhere on their website.

Learn more...

Optimized Merchandising for SSL Products

You can now add recommendation labels to designate featured MarketConnect SSL products to make sure that your clients find your highest-margin SSL products first.

OX App Suite Email Aliases

Clients can now create and manage email aliases for OX App Suite via MarketConnect in the WHMCS Client Area.

Learn more...

Faster WordPress® Checkout

The new Event Handling setting lets you control how WHMCS handles events like installing and provisioning WordPress, allowing for faster checkout speeds for WordPress purchases.

Learn more...

Deprecation and Removal Notices

SagePay Module Deprecation and Updates

Due to anticipated changes from Opayo (formerly Sage Pay) to their SCA and 3DSv2 API implementations, we have updated the related payment gateway modules.

  1. If you use the SagePay or SagePay Repeats modules, you can continue using them with no further action. These modules are fully compatible with both the old and new API implementations.
  2. The existing SagePay Tokens module will not function with the new API implementation. To address this issue, WHMCS 8.4.1 includes a new SagePay Tokens v2 module.

In order to continue using SagePay Tokens as a payment gateway, you must migrate to this new module.

These changes alter the tokenization services that Opayo (and therefore the SagePay Tokens v2 module) offer:

  1. The gateway can only tokenize and store credit cards when the client is making a payment.
  2. Opayo has discontinued the card vault feature.

Learn more...

Templates

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

Twenty-One Theme

The following link provides a comparison of changes between 8.3.2 and 8.4.1 (Maintenance):

https://github.com/WHMCS/templates-twenty-one/compare/v8.3.2-release.1...v8.4.1-release.1

Six Theme

The following link provides a comparison of changes between 8.3.2 and 8.4.1 (Maintenance):

https://github.com/WHMCS/templates-six/compare/v8.3.2-release.1...v8.4.1-release.1

Standard Cart Order Form

The following link provides a comparison of changes between 8.3.2 and 8.4.1 (Maintenance):

https://github.com/WHMCS/orderforms-standard_cart/compare/v8.3.2-release.1...v8.4.1-release.1

Changelog