Jump to content

WHMCS Alex

WHMCS Technical Analyst II
  • Content Count

    160
  • Joined

  • Last visited

  • Days Won

    5

WHMCS Alex last won the day on May 13

WHMCS Alex had the most liked content!

Community Reputation

24 Excellent

2 Followers

About WHMCS Alex

  • Rank
    WHMCS Technical Analyst II

Recent Profile Visitors

3447 profile views
  1. Hi, If you are using Cloudflare and the issue is that the authoritative IP address for requests is not being correctly recorded, you likely need to configure your Trusted Proxies setting inside WHMCS, adding in Cloudflare’s IP ranges.
  2. Hi, There is presently not a way you can modify the Domain Syncronisation feature to sync more than 50 domains at one time, however, you can force the execution of the task via cron.php to execute more frequently. Example command: php -q /path/to/crons/cron.php do --DomainStatusSync Executing that every 5 minutes (either manually or as a cron job) would result in 600 domain names being synchronised every hour (12 x 50). I hope this helps.
  3. Hi @AznHypeBreaker, WHMCS does not have a bulk disable option for the Auto CC Processing option, however, it can be achieved via this SQL query: UPDATE `tblclients` SET `disableautocc` = "1"; Please be sure to fully backup your WHMCS database before executing said query.
  4. Hi @leopard16, I have witnessed such an error before and it was caused by using an unsupported version of PHP in WHMCS 8.x (such as 7.1). WHMCS 8.x supports PHP 7.2, 7.3 and 7.4. How are you confirming the PHP version being used? Under the “Utilities” menu admin side, you will find a PHP Info page, which you can view to confirm the PHP version being used. This page just uses the phpinfo() function to output such information.
  5. Hi @Gor, You can customise the admin directory as documented here: https://docs.whmcs.com/Customising_the_Admin_Directory#Renaming_Your_Admin_Directory You may also wish to review this documentation regarding further security you can implement to restrict access to the admin dashboard: https://docs.whmcs.com/Further_Security_Steps#Restrict_Access_by_IP I hope this helps.
  6. Hi @brian!, We have an internal case open with the development team to explore this is in more detail, but our present understanding is that this relates to that driver and the way it handles integers, thereby not being a deficiency in the WHMCS software. Whilst I cannot speak for the intentions of the development team, I would anticipate the resolution I provided to become documented, with the potential of a check being implemented within WHMCS to alert users to it, though that is only my anticipated outcome of the aforementioned internal case and not a confirmation that will become the result of it. I hope that helps.
  7. Hi, Do you use CloudLinux at all? If so, please try switching from pdo_mysql to nd_pdo_mysql (native driver) within the Cloudlinux PHP configuration and check again. The CloudLinux pdo_mysql build appears to have some quirks about the way it handles integers (or at least we have observed unexpected behavior), but the native driver does not.
  8. Hi, This issue may occur when an order form template contains a theme.yaml file referencing itself as the parent theme. To resolve it, ensure that any custom order form templates in place don't reference themselves as the parent theme inside the theme.yaml file. This has also been reported to our development team as CORE-16051 so it's better handled by the core product in future. I hope this helps.
  9. Hi, As a further update here, we have been able to determine that this issue may occur when an order form template contains a theme.yaml file referencing itself as the parent theme. To resolve it, ensure that any custom order form templates in place don't reference themselves as the parent theme inside the theme.yaml file. This has also been reported to our development team in CORE-16051 so it's better handled by the core product in future. Thanks!
  10. Hello @massa, I can confirm it’s not something we can reproduce locally, however, I’d like to ensure we understand why yourself and others are experiencing this issue. Would you please PM me your ticket ID so I can take a look further myself? Thanks!
  11. Hello @Liam, A client ID and Secret are used by the PayPal Checkout module, which utilises webhooks for payment notifications, not the IPN (which the PayPal Basic module uses). To that end, you will want to check the webhook events history inside PayPal to determine why no notification of payment was sent: https://developer.paypal.com/developer/dashboard/webhooks/live WHMCS configures the relevant webhook listener and events for payment/subscriptions upon connecting to PayPal, from WHMCS. You will also want to check your Gateway Log inside WHMCS for any errors if payment notifications/webhooks are being received but the payment is failing to record, with common issue explained here: https://docs.whmcs.com/PayPal_Checkout#Common_Problems
  12. Hi @Cert, You can migrate to Stripe as documented here: https://docs.whmcs.com/Stripe#Migrating_to_Stripe Whether you can utilise that migration path, will depend on the exact SagePay module you are using. If you’re using tokens or repeats, they are token based gateways, as such card data is not stored in WHMCS preventing the migration path documented above from working. If that’s the case, @brian! is correct in respect of the process for moving, customers would need to manually store their card through WHMCS (using Stripe) or pay their next invoice.
  13. Hello @cyben76, I would only expect the ticket to visible by visiting the unique ticket number/URL only, where the ticket was submitted by an unregistered user. You can easily check if that was the case by reviewing whether the ticket was automatically linked to a client account. What can happen is registered users open a ticket via the contact form, or via email (where it’s then piped in) but using a different email address to that which is registered on the account, meaning that whilst you recognise them as being an existing client, WHMCS has not linked the ticket to said clients account, making the ticket accessible as if it were an unregistered user. If you are finding tickets correctly linked to clients accounts are visible without logging in, I’d suggest submitting a ticket to us so we can investigate further.
  14. Hello, Thanks for reaching out to WHMCS. In version 8.0, WHMCS will ensure sensitive gateway related data is encrypted before it's inserted into the tblpaymentgateways table. The following gateway settings, which don't contain sensitive data won't be encrypted: name type visible convertto This change should not affect gateway modules developed as per our SDK as the gateway module will be retrieving said configuration values from within the $params array (which will pass the decrypted values of settings within the _config function of the module) which is passed to all functions within the gateway module. The change itself represents a positive step forward to protecting sensitive gateway related configuration values within WHMCS. That being said, we would be interested to know of the need for being able to decrypt those values directly, via the API or another method and how that relates to the integration you have developed?
  15. Hello @snake, WHMCS itself does not email out instructions pertaining to how to transfer specific TLDs, such as changing the tag for a .uk domain name. I would suggest creating a knowledgebase article that covers this and then update the Domain Transfer Initiated email template to reference that article.
×
×
  • Create New...

Important Information

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