WHMCS v6 Supported Modules

Version 1.6 and above of our WHMCS modules now fully support WHMCS v6. This includes our Domains Module, SSL Certificate Module and Hosting Services Module. The latest copy of our WHMCS Module can be found within the Synergy Wholesale system. We encourage users to ensure they are running the latest module and not the default one included with WHMCS.

Changes to the Domains Module (v1.6):

• Full WHMCS v6 compatibility: The new Domains Module is now fully compatible with WHMCS v6 and onwards.
• Simpler API whitelisting: There is a new API Connectivity checkbox that can be enabled when performing initial configuration that will help troubleshoot connectivity issues.*
  
• New name: The module finally reflects our new branding (of Synergy Wholesale).
• Better error handling: The module now supports better handling of errors or unexpected input and provides further information to the user as to where the error may lay.
• Client Area DNS Change: When a user is utilising FreeDNS from the client area, the previous message to advise them that any change to their name servers has had to be removed due to WHMCS v6 interpreting this displayed message as a consist error and preventing name server updates.

* Note: Please ensure the new API Connectivity option is unticked and disabled once you have finished configuring the Domains Module because you could be blocked from the Synergy Wholesale API for excessive utilisation.

Changes to the Hosting Module:

• Full WHMCS v6 compatibility: Whilst this module was already fully compliant with WHMCS v6, we are now throwing on the official sticker!
• Updated error handling: The module now supports better handling of errors and should assist in troubleshooting.
• New name: The module finally reflects our new branding (of Synergy Wholesale).

Changes to the SSL Module:

• Full WHMCS v6 compatibility: The new SSL Module is now fully compatible with WHMCS v6 and onwards.
• The name has not been updated from VentraIP Wholesale at this stage because a migration path needs to be executed upon name change to ensure continued service to existing records. We will be providing more information on this in the coming weeks.

Updated: Monday, 26 October 2015.