We are pleased to announce the release of WHMCS 5.3.12.
This update contains maintenance updates for the 5.3 series of WHMCS as well as new functionality in Domain Renewal Notices. More information on these can be found in our recent Feature Spotlight blog post: Domain Renewal Notices.
As usual, we are making available both an incremental upgrade version containing just the changed files for those upgrading from the latest previous version V5.3.11 and a full release which can be used to perform a new installation or upgrade an existing installation regardless of previous version.
Both of these are available to download from the downloads page below.
Please refer to the release notes for specific information regarding this release and details of any template changes that are required.
Posted by Matt on Wednesday, February 25th, 2015
The Internet Corporation for Assigned Names and Numbers (or ICANN for short), recently introduced some new requirements relating to how domain renewals should be handled by domain registrars. Some domain registrars have implemented changes in response to these ICANN requirements. For example eNom announced that in an effort to ensure their sub-resellers meet the new requirements, they would start sending out domain renewal notices on behalf of their resellers.
However, as you might expect, many companies wish to continue sending their own custom branded and personalised domain expiry notices, and eNom will allow you to do that, providing you can prove you can meet the requirements set out by ICANN.
As of today, any web hosting provider using WHMCS with eNom can do just that as WHMCS 5.3.12 includes the necessary tools and functionality to ensure you comply. eNom is the first registrar integrated with WHMCS to benefit from this new functionality in our product. We look forward to working with other registrars who offer similar functionality in the near future.
WHMCS has always allowed you to send domain expiry warning notices, however only prior to the expiry date. One of the new requirements from ICANN is that if a domain expires, the registrar must send at least one post expiry notice within 5 days of the expiry date. In 5.3.12, it is now possible to configure any of the reminders to be sent either before or after expiry as shown below.
Another new ICANN requirement was that it is no longer sufficient to just send the expiry notice to a domain's registered account holder, but rather it must go to the email address listed under the registrant contact of the whois record. WHMCS will now also perform this for eNom domains, sending it to both the account holder and the registrant contact (if they differ).
Lastly, ICANN now requires sufficient logging of the domain renewal notices so that an audit trail can be provided for regulatory compliance. With that being said, in WHMCS 5.3.12 we've introduced a new dedicated logging system for domain renewal notices which will keep a log of all renewal notices that are sent, along with the date and recipients, and provide an easy way to view and export that information upon request via a new report.
To get this new functionality, simply upgrade to WHMCS 5.3.12 today
More information on configuring and using this new feature can be found in the Domain Renewal Notices Documentation
For more information on the changes eNom is making and the opt-out process once you have upgraded to 5.3.12, please visit http://www.enom.com/news/867/domain-renewal-changes-starting-february-1-2015.html
Even if you don't wish to opt-out and configure your WHMCS installation to send the renewal notices to your customers, do make sure to set the "Renewal URL" inside your eNom Reseller Renewal Account Settings or eNom won't be able to direct users to your WHMCS install for the renewal in the notices that they send on your behalf.
For more specific details on the ICANN requirements, please visit https://www.icann.org/resources/pages/errp-2013-02-28-en
Posted by Matt on Wednesday, February 25th, 2015
When development on Version 6.0 of WHMCS began, we set ourselves some very ambitious goals.
The most visible change is of course the new client area look, however it is so much more than just a new look. The aim was to create not only a great looking user experience, but also the most user friendly, cross browser and platform compatible, developer accessible client area offered by any web host billing platform.
And we're confident you'll love the results.
The real benefit of the new frontend will be seen through the power of how modules (and hooks) can shape the user experience, and once the beta period opens, we'll be opening up communication channels for developers to get in contact with us and discuss the best ways in which they can take advantage of that new functionality. We also have a few surprises up our sleeves so stay tuned for those. :)
But Version 6.0 is about much more than just a new frontend. This is a huge deal for us.
It marks the culmination of a year of hard work, with considerable behind the scenes investment in new technologies and new code, setting the stage for us to ramp up and continue delivering an ever improving quality of product to our users at an even more rapid pace. I will touch on just a few of these here.
Composer is just one of a number of really good advancements to come along for PHP development community in recent years. Created by Nils Adermann and Jordi Boggiano, Composer allows us to utilise components and libraries from other projects and frameworks, which allows us to significantly reduce development time, whilst ensuring we're using quality tried and tested code, as well as giving developers, who work with WHMCS, code and API's that they will likely be familiar with. So far we're using components from Symfony, Laravel and a number of other specific packages used throughout the PHP community for their stability and power.
Next on the list was future planning for the deprecation of PHP's original MySQL functions, and with that in mind, we made the decision to commit to using Models driven by an ORM. After much testing and debate internally, we settled on using the Laravel Eloquent ORM aka Illuminate Database. This makes interacting with the database much easier, and will hugely simplify working with the WHMCS backend database in add-ons, custom reports, and many other ways.
PHP Version requirements is another big issue. PHP is a modern enterprise language that has been consistently providing more advanced features, stability, and security to its developers, and we intend to take full advantage of it. For 6.0, we announced mid-way through last year that PHP 5.3 would be the minimum requirement to run WHMCS 6.0. We really wanted to make this 5.4, but we appreciate that a significant percentage of our users are still running on PHP 5.3 (and even 5.2 in some cases), and that sometimes there are factors that make upgrading PHP difficult. Moving forward however, our PHP support will be much more aligned to that of the official PHP project, so just a little heads up on that.
Last but not least, we've also made a lot of internal changes in the WHMCS labs and offices, both to our backend systems, internal organisation and workflow, our testing infrastructure, and more, including a significant increase in the coverage and permutations of our automated UI, API, and unit tests.
We've also committed heavily to investing further in the product, and with that in mind we're hiring - so if you're a super talented PHP developer, we want to hear from you
As I started out by saying, Version 6.0 is not far away now. In the coming weeks, we'll be posting a series of blog articles that go into more detail about what to expect in Version 6.0 and with more in depth details about some of "under the hood" changes and technical aspects to come. Be sure to keep an eye on our blog and social media accounts. And if you aren't on our mailing list, subscribe here
to be among the first to hear about it.
Posted by Matt on Wednesday, February 18th, 2015
We are pleased to announce the public release of aWHMCS 2.0, which is now available for immediate download on Google Play.
aWHMCS 2.0 introduces a brand new user interface, improved support for tablet devices and lots of new functionality to bring our Android App in-line with our iOS offering.
You can download aWHMCS free of charge via the Google Play
store and give it a try with our online demo.
To get aWHMCS for your installation, it's just $2.99/month or $29.99/year (2 months free). And remember, once you activate it for your installation, all of your staff can take advantage of it.
To find out more, visit www.awhmcs.com
Already have aWHMCS? For existing license holders this update is available at no additional cost. Simply visit the Google Play
store to get it today.
Posted by Sean on Friday, January 23rd, 2015
On February 1st, 2015, VeriSign, the Registry Operator for the .net domain, is increasing the annual registration price by $0.61 USD.
As a result of this registry increase, the cost of registering and/or renewing a .net domain will be increasing for all domain registrars, and in turn will affect prices for our eNom and ResellerClub users.
For our ResellerClub users, the current base price of $9.45/year will be increasing to $9.85/year and for our eNom users, the current base price of $9.75/year will be increasing to $10.15/year. Despite the $0.61 price increase, you'll notice our sub-reseller prices are only increasing by 40 cents. This is due to both the domain registrars and ourselves absorbing some of the cost increase to offer our clients the best possible rates.
eNom users will also be receiving an email notice today from eNom regarding this price increase.
You may be asking, what does this mean for me?
On February 1st, you will want to review your domain pricing in WHMCS for the .net TLD and adjust it as necessary to maintain the profit margin you desire. To adjust the domain pricing go to Setup > Products/Services > Domain Pricing inside your WHMCS admin area and click on Open Pricing next to the .net TLD.
Before that date however, you might also like to consider renewing any .net domains you own to avoid the upcoming price increase.
In the meantime, if you have any questions or concerns regarding this update, please do not hesitate to contact our support team.
Posted by Sean on Tuesday, January 13th, 2015