Jump to content

WHMCS John

WHMCS Support Manager
  • Content count

    9,289
  • Joined

  • Last visited

  • Days Won

    33

Everything posted by WHMCS John

  1. Version 1.0.0

    21 downloads

    An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that prevents payments being processed via payment gateways using transaction references: MODULE-7154 - Sagepay Repeats MODULE-7146 - PayPal Pro Reference Payments MODULE -7140 - PayPal Payments Pro with Reference Transactions option enabled CORE-13810 - Prevent Client Area access to Add Payment Method page with only Reference Gateways We have also identified issues with the eWay Rapid module in this version: MODULE-7134 - Correctly report the status of declined payments in eWay Rapid MODULE-7132 - Correctly report the status of refunds in eWay Rapid MODULE-7131 - Error "Call to a member function getKey() on null" when adding a pay method via the admin area using eWay Rapid We have also identified an issue with Authorize.net CIM: MODULE-7143 - Ensure credit cards can be added/updated when Validation Mode is set to "Live" This hotfix applies only to 7.8.3
  2. Hi there, In the same way as v7.7, once a client makes their first payment via eWay, a token is stored in WHMCS which can then be remotely charged and updated. You can see the token ID when viewing an invoice assigned to eWay in the admin area. The workflow for updating a stored card at eWay via WHMCS in 7.8 is as follows: Edit the Pay Method for the existing card (eg. a Mastercard) The iframe appears with the the email address and phone number pre-filled The client enters their new credit card number, expiry date and CVV (eg. an Amex) Click "Pay Now" The card details under the Token Payment Customer at eWay are updated with the new card - no charge is made The iframe closes and the Pay Method in WHMCS is updated to reflect the new Amex card number. The process is the same for admins and clients, with the only difference being the starting point at step 1. I've tested this process today in the eWay Sandbox environment using 7.8.3 with the hotfix applied, and can confirm that the process is working as expected: I placed an order as a new client and used a Mastercard to successfully make payment (Order total 2.49 AUD). I then updated the Pay Method from a Mastercard to Amex via WHMCS. Then I created an invoice for 1.00 AUD, assigned to eWay Rapid payment gateway, published it and clicked "Attempt Capture". The invoice was marked paid in WHMCS. The transaction on the eWay control panel shows the invoice charges were made against the appropriate cards as I would expect: Please help us in understanding which part of the process is presenting the obstacle to you?
  3. Hi @sibuk, This error can occur if columns are missing from ticket-related tables tblticketnotes tblticketreplies tbltickets The 7.8.2 update creates an attachments_removed column in those tables, so creating them manually should resolve the error: alter table `tbltickets` add `attachments_removed` tinyint(1) NOT NULL DEFAULT '0' AFTER `attachment` alter table `tblticketreplies` add `attachments_removed` tinyint(1) NOT NULL DEFAULT '0' AFTER `attachment` alter table `tblticketnotes` add `attachments_removed` tinyint(1) NOT NULL DEFAULT '0' AFTER `attachments` I'd also recommend checking the other database updates have been applied., these are located at /resources/sql
  4. WHMCS John

    Invalid positive integer

    Hi there, We've been able to reproduce this when paying for orders with a total of 0.00 with an existing Pay Method. Case MODULE-7155 is open internally with our development team to have this resolved in a future update. Once we resolve cases and push features they are available at our change log, here: https://changelog.whmcs.com/ I apologize for the inconvenience, and appreciate your patience as we work to resolve this.
  5. Hi there, We've been able to reproduce this error and have opened case CORE-13801 internally to have this resolved in our next feature release. This error occurs when a client logs in for the first time after updating to 7.8.x and ticking the "Remember Me" checkbox Logging out and back in again with the "Remember Me" option UNticked for the first time will resolve this error. It should then be possible to use the "Remember Me" option as usual.
  6. Hi @J-B, Thanks for providing that information. This error is being returned directly by Stripe, and indicates that the address validation failed based upon the client's postcode/zip code: https://stripe.com/docs/radar/rules#traditional-bank-checks Please have the client update their address details associated with the card (via the Pay Methods page) and try again.
  7. WHMCS John

    Maxmind Now working anymore?

    Hi @kingbrend, I performed a test on my stock 7.8.3 install, placing an order as a new client and failing the fraud check. I confirmed that an uncaptured transaction is logged in Stripe (see attached). Please ensure you've applied the 7.8.3 maintenance release, and any custom templates are up-to-date. We recommend using the Standard Cart order form template or its children with Stripe: Standard Cart Premium Comparison Pure Comparison Supreme Comparison Universal Slider Cloud Slider https://docs.whmcs.com/Version_7.8.0_Release_Notes#Template_Changes
  8. WHMCS John

    Maxmind Now working anymore?

    Hi @kingbrend, This is currently the designed behaviour in version 7.8 when used with Stripe Payment Intents; the card will be pre-authorised upon placing the order. A charge is only made when the fraud check completes successfully. This pre-auth hold will be released by the bank if no charge is made after a period of time. We are looking to further finesse this behaviour in v7.9 to cancel the hold if the fraud check is subsequently failed.
  9. Hi @hkhost, I've been bale to reproduce this on my 7.8.3 installation, so have opened case MODULE-7161 internally with our development team to have this investigated for a future update. Once we resolve cases and push features they are available at our change log, here: https://changelog.whmcs.com/ I apologize for the inconvenience, and appreciate your patience as we work to resolve this.
  10. Version 1.0.0

    8 downloads

    An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that can result in non-card tokens (such as GoCardless Mandates) being migrated to a remote credit card Pay Method type instead of the expected bank account type. This occurs when running v7.7 there is both credit card information and a Mandate token stored for a client, and GoCardless is the only active payment gateway module. Upon applying the 7.8 update and performing the Pay Method migration for an impacted client, a remote credit card Pay Method may be created. This hotfix applies only to 7.8.3
  11. It should not be necessary to use this "Login" link to update the card details stored remotely at eWay and the token in WHMCS. Please just update the card number, expiry date and CVV number and click the "Pay Now" button. With regards to removing the Login link, this implementation method does not offer a way for us to control the iframe's appearance: https://www.eway.com.au/developers/api/iframe/ However I do know it is possible to customise the logo and card scheme icons from eWay's side, so they may also have the ability to enable/disable this feature if you speak to their support team. If you have a preferred alternative implementation method, please feel free to submit a new Feature Request over at https://requests.whmcs.com for potential consideration in future.
  12. Hi @hkhost, Please ensure you've applied the 7.8.3 update. Is this with a custom template or the stock Six templates and Standard Cart order form? If using a custom template, please ensure it's been updated: https://docs.whmcs.com/Version_7.8.0_Release_Notes#Template_Changes
  13. Version 1.0.0

    23 downloads

    An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that when opening a ticket as a support contact via email causes the first CC'd email address to be combined with the submitter's email. This could result in ticket notifications not being sent to all the expected recipients. This hotfix applies only to 7.8.3
  14. Version 1.0.0

    297 downloads

    An issue has been identified in the 7.8.2 release - published on 6th September 2019, that can result in an error when visiting the pwreset.php file directly: Call to undefined function WHMCS\CALinkUpdateCC This is caused by the introduction of new Friendly URLs for the password reset path /password/reset/begin Attempting to access the old location at pwreset.php results in this error. This hotfix applies only to 7.8.2
  15. WHMCS John

    Service ID Not Found

    This sounds like a service has been assigned to a product which no-longer exists. This can be corrected with: UPDATE tblhosting SET packageid='x' WHERE id='y'; Replace x with the correct product ID (from Setup > Products/Services > Products/Services > Edit) Replace y with the service ID (from your browsers' URL bar) Could you please share the entries you have in Utilities > Logs > Activity Log at the time of performing the sync? Take care to remove any sensitive data before posting it here publicly.
  16. Hi @vinc1402, Based on the information provided here, everything look to be in order so I would expect the Stripe token to be attempted for capture automatically. We'll need to take a closer look to identify why this isn't happening in this situation, so please do open a support ticket with access credentials so we can investigate further.
  17. WHMCS John

    Card number is required'

    Hi @Burti, Which payment gateway are you using please? From that output "ziraat_BurtiNET" looks like a custom gateway name. The error suggests that the credit card number is not being passed in the module's capture function in the expected way. In which case, please ensure the module is coded in accordance with our develop documentation and samples at https://developers.whmcs.com/payment-gateways/
  18. Hi @Remitur, I've been bale to reproduce this on my end too, as such I've opened case CORE-13799 with our development team. Once we resolve cases and push features they are available at our change log, here: https://changelog.whmcs.com/ I apologize for the inconvenience, and appreciate your patience as we work to resolve this.
  19. Hi @Perce, This is likely caused by a server-side security measures, such as mod_security. Please work with your server admin/hosting provider to check the server logs to identify the specific cause of the permission error and adjust any security rules as necessary.
  20. Hi all, As a separate topic has been started to discuss this latest case (and already linked), I'm going to close this topic to further discussion. Please continue over at:
  21. Hi there, We have opened case MODULE-7151 regarding the statement descriptor for initial signups being displayed as "Shopping Cart". This is because there is no invoice on order when the payment with Stripe is being made, so an invoice number cannot be sent.
  22. Hi @benduick, I'm sorry to hear you encountered an overage invoicing problem. I'd expect this to be possible only on installations currently running 7.8.0 - 7.8.2, created in version 5.0 or earlier, where soft limits are set to 0 for products which have not been saved since version 5.1. Does this sound like your case? Which version of WHMCS were you running at the time of invoice generation please? Can you please share your support Ticket ID so I can review the situation in more detail?
  23. The template system used by WHMCS makes it easy to add extra variables wherever extra information should be displayed. In this example I'll demonstrate how to add the Client ID to the invoice page. This same process can be used to display any bit of available client data to almost any client area page. 1. Locate the template relating to the page you wish to modify. In this example I'm using viewinvoice.tpl. Template files are located in the /templates/*your active template*/ directory. I recommend making customisations to a custom template to ensure they are maintained following an update. More details are located here: https://developers.whmcs.com/themes/getting-started/ 2. At the top of the file, add the following code: {debug} Save the file and upload it to the server. 3. Visit the page in your browser, and you'll see a popup appear. This contains all the template variables and language strings available on this page. Identify the variable you want to use, in this case it's the $clientsdetails array I need because it contains the userid: 4. If the variable to use is a simple key-value pair, then it can be output simply by adding the merge field like this to the template file: {$filename} However in this example the client userid is contained within an array. So the format to add to viewinvoice.tpl is: {$clientsdetails.userid} Add the merge field into the template wherever you'd like to display the extra variables. I've added it beneath the client's name: 5. Once you're happy, remove the {debug} tag, save and upload the template file. Et Voila! The Client ID is now displayed on the invoice page: ProTip: This also works for email templates too! Sent the email to a client, then view the message via Utilities > Logs > Email Log. For further reading, please refer to https://developers.whmcs.com/themes/variables/ Feel free to modify it to suit your needs and I hope it helps! 
  24. WHMCS John

    Service ID Not Found

    Hi @hkhost, The Sync Tool will present a list of all proposed actions before you execute them. Do you still see the service listed in on the clients Summary tab, or is it gone entirely?
  25. Hi @vivithemage, Are you finding that Pay Methods created after updating to 7.8.3 are still experiencing the problem? We made some changes to handle situations with invalid data reported by some users. Pay Methods are created for existing clients when attempting capture on an invoice, visiting their Summary tab in the admin or when the client logs into the client area.
×

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated