SoluteDNS - Community Forums

Hello,

I upgraded WHMCS 5.3.10 and SoluteDNS 0.1.7 (15001) to latest WHMCS (7.1.0) and latest SoluteDNS (0.2.7). But now, when enter to addon section in logs error message appears:

[Sun Dec 18 20:52:12.028527 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: PHP Warning: Invalid argument supplied for foreach() in /home/dev7/public_html/crm/admin/configaddonmods.php on line 0
[Sun Dec 18 20:52:12.028619 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: PHP Fatal error: Uncaught Error: Class 'localdb' not found in /home/dev7/public_html/crm/modules/addons/solutedns/solutedns.php:717
[Sun Dec 18 20:52:12.028625 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: Stack trace:
[Sun Dec 18 20:52:12.028628 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: #0 [internal function]: solutedns_upgrade(Array)
[Sun Dec 18 20:52:12.028632 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: #1 /home/dev7/public_html/crm/admin/configaddonmods.php(0): call_user_func('solutedns_upgra...', Array)
[Sun Dec 18 20:52:12.028635 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: #2 {main}
[Sun Dec 18 20:52:12.028638 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: Next Error: Class 'localdb' not found in /home/dev7/public_html/crm/vendor/whmcs/whmcs-foundation/lib/Terminus.php:0
[Sun Dec 18 20:52:12.028641 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: Stack trace:
[Sun Dec 18 20:52:12.028644 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: #0 [internal function]: WHMCS\\Terminus::whmcsExceptionHandler(Object(Error))
[Sun Dec 18 20:52:12.028647 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: #1 {main}
[Sun Dec 18 20:52:12.028650 2016] [fcgid:warn] [pid 31811:tid 140350618064640] [client xxxx:63351] mod_fcgid: stderr: thrown in /home/dev7/public_html/crm/vendor/whmcs/whmcs-foundation/lib/Terminus.php on line 0

Thank you for your post and reporting this issue.

Unfortunately the upgrade process from the 0.1.x branch to the 0.2.x branch isn't that straight forward. I would recommend you to deactivate SoluteDNS and make sure all database tables are removed. Afterwards you can activate the 0.2.7 version and do a fresh install.

If this doesn't solve the issue please do not hesitate to report back!

Hello Daniel,

I removed all mod_solutedns tables from database, but when I go to Setup -> Addon Modules section I anyway got this errors and can't deactivate SoluteDNS module. How to do it from command line?

Right now I do all this changes on DEV installation, but how to upgrade from 0.1 to 0.2 module in production? Or 0.1 and 0.2 are completely different products? Maybe there are some sort "migration" possibilities from old to new version?

Please remove the solutedns folder entirely from the modules/addons directory. Next go to the WHMCS admin area addon page and review SoluteDNS is no longer being displayed. Afterwards you can reupload a fresh copy of the latest branch and activate it again.

If you have a paid license we can offer you extended (paid) support for upgrading your setup. In this case we would convert your database from the 0.1.x to the 0.2.7 branch after which you can reimport this database. Otherwise I recommend you to disable and remove SoluteDNS entirely before upgrading and start fresh with the new branch in WHMCS v7.

If you wish to use our extended support service please contact our sales. Contact information can be found at: http://www.solutedns.com/support/

Hello,

I did what you suggested, removed solutedns folder, verified that MySQL tables removed. Addon section works and there aren't any solutedns options. Installed fresh solutedns from latest 0.2.7 archive and same error.

Thank you for your feedback. I will ask our development to review this issue and find a workaround when possible. I will reply to this post as soon as possible when more information is available.

Please replace attached files and review if this solves the issue you experience. The attached files have a different upgrade approach where this error should not occur.

Thanks, It worked.