Difference between revisions of "Version 8.4 Release Notes"
(→Changelog) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 53: | Line 53: | ||
===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...] | [https://marketplace.whmcs.com/help/connect/kb/ox_app_suite/getting_started/what_is_an_email_alias Learn more...] | ||
| Line 66: | Line 66: | ||
[[Other_Tab#Event_Handling|Learn more...]] | [[Other_Tab#Event_Handling|Learn more...]] | ||
| + | |||
| + | == Deprecation and Removal Notices == | ||
===SagePay Module Deprecation and Updates=== | ===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. | + | 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. | + | # 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. | + | # 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. | In order to continue using '''SagePay Tokens''' as a payment gateway, you must migrate to this new module. | ||
| Line 81: | Line 83: | ||
# Opayo has discontinued the card vault feature. | # 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 == | == Templates == | ||
| Line 91: | Line 91: | ||
===Twenty-One Theme=== | ===Twenty-One Theme=== | ||
| − | The following link provides a comparison of changes between 8.3.2 and 8.4. | + | 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. | + | 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. | + | 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. | + | 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. | + | 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. | + | https://github.com/WHMCS/orderforms-standard_cart/compare/v8.3.2-release.1...v8.4.1-release.1 |
== Changelog == | == Changelog == | ||
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
Contents
Version History
| 8.4.0 | Beta 1 | 1st December 2021 |
| 8.4.0 | Release Candidate 1 | 17th December 2021 |
| 8.4.0 | General Availability 1 | 18th January 2022 |
| 8.4.1 | Maintenance | 21st 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.
Once you are running WHMCS 8, you can upgrade to PHP 7.4.
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.
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.
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.
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.
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.
- 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.
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