Jump to content


Level 2 Member
  • Content count

  • Joined

  • Last visited

Community Reputation

10 Good

About aquiss

  • Rank
    Level 2 Member
  1. Domain Categories

    Talking of categories, has anyone got a list that places the extensions in correct categories? We are often finding many are not listed in any category other than getting bunched into the popular one (when they are clearly not popular).
  2. why was goCardless support removed

    Let me give some clarity on this. The original Gocardless module was written in partnership with us, as a tester, by a guy called Tim who worked there. We worked with him to get the original module up and running as we were one of GoCardless's launch partners. Tim then left GoCardless to return back to University full time (was part time whilst working at GC). He made the original code available in the public domain, but as no one official was updating it, our understanding was WHMCS then dropped it. GoCardless even did a blog entry on us, them and WHMCS https://gocardless.com/blog/merchant-of-the-month-aquiss/ For ages, literally 2-3 years, the only way to make things work was via patchy GitHub solutions, they worked, but were not amazing. We patched ours for internal needs for a while, but when version 7 of WHMCS, we had find an different solution. Personally, support for GoCardless now would make more sense than it did back then, so many businesses are using them, but with commercial modules, at decent money, available, it might not make sense for WHMCS. However, with them supporting other forms of Direct Debit and now including DD based elements into WHMCS core, surely this is worth a look again?
  3. PHP Version Warning

    Alex would it not be worth removing this warning from within WHMCS software until such time as upgrades can be made? I fear you are going to get a large increase in support tickets from customers who are not in the know (like myself) unless this warning is suppressed in some way.
  4. We are using WHMCS 7.4.1 and PHP 7.0.26 Today a warning has appeared that our PHP version is end of life Ok, upgrading PHP is not an issue, but I thought WHMCS did not support PHP 7.1.* yet ? If i'm correct, this warning from within WHMCS is a chicken or egg situation.
  5. Thanks for the confirmation of how it works, bit confusing, but at least I know.
  6. Can anyone else confirm that the new "international phone number automatic formatting" introduced into 7.4.0, even when disabled from within the new option, is still changing client profile contact numbers to start with the international format (in our case +44.)?
  7. I've put full details in ticket (id given above), however, it appears to be linked to a weird problem with our SSL (we moved to a multi domain SSL 2 months ago), so linked to point 1.
  8. Just and update, this was our end, but has taken some real debugging to get things sorted. Thanks Nate and other whmcs staff today for highlighting an issue area. Ticket replies were very fast, detailed and exactly the professionalism that we needed. Top notch guys! WHMCS Staff, this is linked to your ticket #BPI-325537
  9. Cheers Nate, I know we have raised a ticket with your support desk and they have highlighted points 1 and 2 already. We are just double checking everything our end before looking at point 3.
  10. Never had issues previously with automatic upgrades, always been spot on, however, this morning we have gone to upgrade and get the following errors Error (Help Documentation) Error: failed to open stream: operation failed Failed to enable crypto error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed The "https://releases.whmcs.com/pkgs/whmcs-7.4.1-release.1.zip" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages: [Composer\Downloader\TransportException] Downloading - Installing whmcs/whmcs (7.4.1) Updating dependencies https://releases.whmcs.com could not be fully loaded, package information was loaded from the local cache and may be out of date failed to open stream: operation failed Failed to enable crypto error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed The "https://releases.whmcs.com/packages.json" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages: Loading composer repositories with package information
  11. From Admin, find client. Then under Summary Tab select option Credit Card Option within the Clients Information box. Then from within their, you can clear the current information. Hopefully that's what your are asking for.
  12. This has been resolved. I think I must have been cached, because without doing anything, this morning the option has appeared. It was indeed the tick box as Brian highlighted. Not sure you are correct Chris, as the option appears for all our customers, regardless if they have a card on file or not. Now if this is intended to be like that, that's another thing entirely.
  13. Hi Brian, Yup, I found swiftdone's post earlier today and had the same thought, but unchecking that does not seem to make "Manage Credit Card" reappear in client side billing drop down. Thus I presumed something else was wrong/changed (I can't recall messing with templates in this regard). Thanks for the second link, I had no seen that, but it answers my second part perfectly. Thank you.
  14. Well this one has got me stumped....over 8 hours and I can't for the life of me solve it. hmmm
  15. Some months back I removed the option in the client side to add/manage credit cards (located within the Billing menu dropdown). We have now added Stripe as Payment Gateway, so adding this option back I believe will be useful/needed. I maybe wrong that Stripe makes use of this, but i'm asking anyway. However, I can't for the life of me remember how I disabled/removed this option Is there an admin side option to switch on/off this feature that I can't find again? I fear I just took it out within the template, but flipping back to my unedited original does not seem to bring the option back either, hence I think its an admin side thing.

Important Information

By using this site, you agree to our Terms of Use & Guidelines