Page 1 of 1

WHMCS v6

Posted: 07 Jul 2015, 09:59
by innovot
With v6 on the horizon, now RC3, will SoluteDNS be available soon after ?

Re: WHMCS v6

Posted: 07 Jul 2015, 12:33
by Daniel
Thank you for your interest in SoluteDNS for WHMCS 6.

As we have decided to push WHMCS 6 compatibility to the 0.2.x branch of SoluteDNS development time was raised as well. We try our utmost to make our 0.2.x branch available as soon as possible. However I cannot give you an exact ETA, but we try to make the release within a maximum time of 2 months.

Re: WHMCS v6

Posted: 18 Aug 2015, 13:35
by innovot
How is it coming along please ?

Re: WHMCS v6

Posted: 18 Aug 2015, 14:15
by Daniel
Please see: http://forum.solutedns.com/viewtopic.php?f=3&t=73

If you still have any further questions please do not hesitate to contact us!

Re: WHMCS v6

Posted: 01 Sep 2015, 11:36
by delsio
Hi

I have just downloaded the latest version.

I get this error:

Fatal error: The file /var/www/vhosts/**********/httpdocs/modules/addons/solutedns/solutedns.php cannot be decoded by this version of the ionCube Loader. If you are the administrator of this site then please install the latest version of the ionCube Loader. in Unknown on line 0

Running:
[root@designer ~]# php -v
PHP 5.4.44 (cli) (built: Aug 10 2015 15:58:07)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
with the ionCube PHP Loader v4.7.1, Copyright (c) 2002-2014, by ionCube Ltd.

Re: WHMCS v6

Posted: 01 Sep 2015, 13:44
by Daniel
Thank you for your post! It seems the current released version requires ionCube v5 loaders. We recommend you to update your ionCube loaders. If this causes big issues for you please contact support in order to find a suiting solution.

Re: WHMCS v6

Posted: 01 Sep 2015, 17:15
by delsio
Dear,

I still get the error after updating to ioncube 5.x:

<b>Fatal error</b>: Class 'localdb' not found in <b>/var/www/vhosts/domains.co.mz/httpdocs/modules/addons/solutedns/solutedns.php</b> on line <b>618</b><br />

Re: WHMCS v6

Posted: 01 Sep 2015, 21:22
by Daniel
Was solved with ticket support. The exact cause is still unknown it might be related to an issue with the database tables. A other possibility is the ioncube24 Service but this is only a guess at this time as no errors where reported related to the ionCube24 Service

It has our attention.