Jump to content

WHMCS John

WHMCS Support Manager
  • Content count

    8,820
  • Joined

  • Last visited

  • Days Won

    18

WHMCS John last won the day on June 30

WHMCS John had the most liked content!

Community Reputation

176 Excellent

5 Followers

About WHMCS John

  • Rank
    Head of Support

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi testers! In WHMCS 7.6 Beta 1 we have updated the 2Checkout module to add support for the inline checkout style. During the pre-release testing we want to hear about your experiences with this feature. Some potential starting points for discussion are: What was your experience enabling the 2Checkout Inline style? How was the client-side experience placing an order and paying with Inline? How was the client-side experience paying an invoice via the client area with Inline? When paying an invoice containing multiple services with different billing cycles, were recurring payments configured appropriately? In addition to resolving any errors which might occur, understanding any pain points is of particular interest to us. Your input will help us tweak messaging in the product or documentation and publish support articles. Thanks for your help in the pre-release testing!
  2. Hi all, We've heard back from eWay who have confirmed there was an update to the Rapid API which affected some merchants processing Token Payments on Thursday the 5th of July. The issue was quickly identified by the eWAY IT team, and a fix was deployed the following day (6th of July). eWay have not recommended any changes to our code at this time.
  3. Hi testers! One of the key new features in WHMCS 7.6 Beta 1 is Domain Verification Support. During the pre-release testing we want to hear about your experiences with this feature. Some potential starting points for discussion are: Did you see the verification notices in the appropriate places in the client area and admin area? Is the wording of the verification notices easy for your staff and clients to understand? Were the verification messages hidden when the verification was completed or lock periods elapsed? Which domain registrar are you testing with? In addition to resolving any errors which might occur, understanding any pain points is of particular interest to us. Your input will help us tweak messaging in the product or documentation and publish support articles. Thanks for your help in the pre-release testing!
  4. WHMCS John

    MaxMind v2 - Share Your Experience

    Hi @Openhost, The default Fraud Risk Score value is 0, and the lowest score Maxmind will assign in 0.01. So in effect your current settings are configured to block every order. Therefore it sounds like WHMCS is behaving in accordance with your configuration, which is reassuring. I've updated the documentation to provide more information on configuring the Fraud Risk Score setting: https://docs.whmcs.com/MaxMind#MaxMind_Fraud_Risk_Score I hope that's helpful, thanks for your feedback!
  5. WHMCS John

    MaxMind v2 - Share Your Experience

    Hi @Openhost, Thanks for sharing your feedback regarding the mindfraud v2 service. Can you let me know what your Setup > Fraud Protection > Maxmind > MaxMind Fraud Risk Score was set as? Was the fraud score assigned to the orders by Maxmind above or below aforementioned the Risk Score value?
  6. Hi testers! In WHMCS 7.6 Beta 1 we have updated the Maxmind module to use the minfraud v2 API. During the pre-release testing we want to hear about your experiences with this feature. Some potential starting points for discussion are: What was your experience with checks on orders immediately after updating? Was the process of configuring the module straight-forward? Does the information displayed on the new style reports meet your needs? Are there any situations where Maxmind checks did not result in the expected action? In addition to resolving any errors which might occur, understanding any pain points is of particular interest to us. Your input will help us tweak messaging in the product or documentation and publish support articles. Thanks for your help in the pre-release testing!
  7. WHMCS John

    ''AuxBilling contact Details are not vaild"

    Hi @Daskew78, WHMCS does not currently update the AuxBilling contact when changing domain whois details, as this contact is optional. The module has operated in this way since version 3. If eNom do intend to change the behaviour of this field, then we are in touch with the relevant people to advise us of this.
  8. WHMCS John

    Nominet module now requires TLS 1.2

    Hi @Lowreg, Our development team also received today's communication from Nominet and have reached out to Nominet to get clarification on if there will need to be any changes made to the product for the upcoming change. If there are, those changes will be made available well ahead of the September date.
  9. WHMCS John

    ''AuxBilling contact Details are not vaild"

    Hi all, I've received confirmation from eNom support they are indeed having issues regarding Aux billing contacts not properly saving, and have asked me to pass on their apologies for the inconvenience. The eNom engineering team is aware of this impact on customers and have been working towards a resolution. At this time there have been reports of a workaround: Manage the domain contact details directly via the eNom website; Set aux billing, admin contact, and registrant to all to "custom" and set each to the same information. I trust that is useful information. If you have any further questions, please contact eNom support. You can assist eNom support in your reports by using the Module Debug Log to capture the API communication between WHMCS and eNom: https://docs.whmcs.com/Troubleshooting_Module_Problems
  10. WHMCS John

    ''AuxBilling contact Details are not vaild"

    Hi there, We have received a few reports of this error in the past week. Nothing has changed in our code at that time, and I'm not aware of planned changes to eNom's API which could cause this. I suspect this might be related to some of the changes eNom have been making to their system, so I have reached out to our contact for clarification.
  11. WHMCS John

    WHMCS/cPanel Intergration Issues

    Hi @solidblueliquid, This indicates that the user through which WHMCS is accessing the cPanel API does not have permissions to login as the reseller. The reseller must be owned by the user which is entered on the Setup > Products/Services > Servers > Edit page. For resellers, this may necessitate you use the root user.
  12. WHMCS John

    search function 500 error in admin

    Hi @vasil_uhmk, 500 Internal Server Errors would typically be logged to your WebServer log. Please try enabling the display _errors option in your configuration.php file: http://help.whmcs.com/m/troubleshooting/l/678796-troubleshooting-warning-messages#disabling_display_errors_in_configuration_php This may yield further error details on-screen or in your browser's network analyser tool (in the Response section).
  13. WHMCS John

    Cloudflare WHMCS Module

    Hi @cluster, Unfortunately it seems that Cloudflare have discontinued their module: https://support.cloudflare.com/hc/en-us/articles/115002343151-Cloudflare-WHMCS-module-is-not-compatible-with-WHMCS-7-x Perhaps you could use the contact link on the above page to persuade them to reinstate it?
  14. Hi @bluesteam, You can learn more about our order form templates (and which are deprecated) in the following documentation: https://docs.whmcs.com/Standard_Order_Form_Templates
  15. Hi @snowliondev, WHMCS sets the "MC_callback" value within the module code (one for the Worldpay module one for the Futurepay module). The URL is constructed from your WHMCS System URL setting from Setup > General Settings > General tab. To this, the path the to appropriate callback file is apopended: /modules/gateways/callback/worldpay.php or /modules/gateways/callback/worldpayfuturepay.php. So theoretically, if you switched your entire installation to http only, by changing the WHMCS System URL to begin http://, then the Worldpay callbacks would also go to an http:// URL. However this is not something I would personally recommend, and I'd suggest instead investigate changes your SSL certificate setup.
×

Important Information

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