Release Notes
← Older revision
Revision as of 22:59, 16 November 2016
(2 intermediate revisions by the same user not shown)
Line 16:
Line 16:
==Download==
==Download==
−
Download the latest version of WHMCS from http://download.whmcs.com/
+
Download the latest version of WHMCS from http://download.whmcs.com/
#prerelease
==Upgrade Process==
==Upgrade Process==
Line 31:
Line 31:
==Release Notes==
==Release Notes==
+
+
* '''New Daily Cron Notification Format''' - The WHMCS Daily Cron Notification email format has been changed. The email is now intended to provide a high level overview of the daily cron activities and the new [[Automation Status]] feature within the admin interface will allow for reviewing more in depth information for any recent cron run.
+
+
* '''Admin Dashboard Widgets''' - As part of the Admin Dashboard changes, a new format for dashboard widgets has been introduced. Widgets designed for previous versions of the product are still compatible. New style widgets adhere to the admin role permissions and do not require configuring separately like previous widgets.
+
+
* '''Module Queue''' - The module queue is a new feature designed to make it easier to track and resolve failed module API commands. Any failed module calls such as new account provisioning attempts, domain registration and renewals, suspensions, terminations and more will be recorded here along with the reason for failure providing you with an interface to review failures and resolve them. For more information, see [[Module Queue]].
+
+
* '''Premium Domains''' - WHMCS 7.1 introduces support for selling Premium Domains. The selling of Premium Domains requires use of a domain registrar that supports checking the availility of and returning pricing information for Premium Domains. V7.1 introduces this ability to the Enom and ResellerClub domain registrar modules. For more information, please see [[Premium Domains]]
+
+
* '''Namespinning with ResellerClub''' - Domain suggestions are now supported by the ResellerClub and associated domain registrar modules. This can be enabled and configured in ''Setup > Products & Services > Domain Pricing''
+
+
* '''Domain Lookup Provider''' - The location of the domain lookup provider settings has been moved from General Settings to ''Setup > Products & Services > Domain Pricing''
+
+
* '''Cron Logging Changes''' - The format and quantity of activity log entries relating to the cron have changed.
===Asset/Template Changes===
===Asset/Template Changes===
−
We've introduced
compression of all asset files
. This reduces the number of external requests, giving improved performance throughout the product. Delivering faster load times for admins and clients
.
+
WHMCS 7.1 introduces consolidation and
compression of all asset files.
−
====
Which Templates have this?
====
+
'''
Which Templates have this?
'''
−
For
the Client Area, the templates Six and Standard Cart
use minified files
. For the Admin Area, both v4 and Blend templates
use minified files
.
+
All templates have been updated for this - for
the Client Area, the templates Six and Standard Cart. For the Admin Area, both
the
v4 and Blend templates.
−
====
Why change this?
====
+
'''
Why change this?
'''
−
Speed
. On average, WHMCS 7.1 performs '''50'''% fewer requests and pages load up to '''25'''% faster.
+
This change reduces the number of external requests on page loads leading to improved performance throughout the product
. On average, WHMCS 7.1 performs '''50'''% fewer requests and pages load up to '''25'''% faster.
−
====
Can I still add custom css?
====
+
'''
Can I still add custom css?
'''
Yes, definitely. By using the existing [[Customising_the_Six_Theme#Applying_Custom_CSS_Styling|custom.css]] functionality for the six template. The custom.css file for the Six template can apply overrides to the Six and any Order Form Template.
Yes, definitely. By using the existing [[Customising_the_Six_Theme#Applying_Custom_CSS_Styling|custom.css]] functionality for the six template. The custom.css file for the Six template can apply overrides to the Six and any Order Form Template.
−
===Stripe===
===Stripe===
−
WHMCS 7.1
introduced
an
official WHMCS
Stripe module.
Find
the
WHMCS module can in modules/gateways/. Full
documentation
for Stripe is here
.
+
WHMCS 7.1
introduces
an
Official
Stripe module.
For more information, please see
the
[[Stripe]]
documentation.
−
====
What if I have an existing Stripe Module?
====
+
'''
What if I have an existing Stripe Module?
'''
−
WHMCS has attempted
to make the module a drop in replacement for other third party modules. After upgrading, configure the module in Setup > Payments > Payment Gateways. Once configured, disable the third party module, choosing Stripe as the replacement.
+
We have tried
to make the module a drop in replacement for other third party modules. After upgrading, configure the module in
''
Setup > Payments > Payment Gateways
''
. Once configured, disable the third party module, choosing Stripe as the replacement.
−
====
What if my module has the filename "
stripe
"?
====
+
'''
What if my module has the filename "
Stripe
"?
'''
On upgrade, replacement of the third party module will be automatic. Configuration of the module is still required in Setup > Payments > Payment Gateways.
On upgrade, replacement of the third party module will be automatic. Configuration of the module is still required in Setup > Payments > Payment Gateways.
−
====
What if the third party module had template changes?
====
+
'''
What if the third party module
I used before
had template changes?
'''
−
With the official WHMCS module, there are no template changes.
Remove
any
changes completed
to
your custom template to avoid any conflict issues
.
+
With the official WHMCS module, there are no template changes
required
.
Any changes yuou performed when installing
any
third party modules will need
to
be reverted
.
−
====
Can I
use
Stripe
with stored Credit Card details
?
====
+
'''
Can I
convert locally stored credit cards to
Stripe?
'''
−
The
Stripe
module
converts
stored details
to
a
token on automatic capture. It
is
not possible to store or view credit card details in full when using
Stripe
in WHMCS
.
+
Yes.
The module
supports automatically converting locally
stored
credit card
details
into tokens the first time
a
payment
is
captured via
Stripe.
−
==New Documentation
Articles
==
+
==New Documentation==
* [[Automation Status]]
* [[Automation Status]]
* [[Module Queue]]
* [[Module Queue]]
* [[Premium Domains]]
* [[Premium Domains]]
−
* [[Hooks:PremiumPriceOverride|Premium Price Override Hook]]
−
* [[Hooks:PremiumPriceRecalculationOverride|Premium Price Recalculation Override Hook]]
* [[Stripe]]
* [[Stripe]]
+
* [http://docs.whmcs.com/classes/7.1/index.html New Class Documentation]
==Template Changes==
==Template Changes==