Jump to content

WHMCS Alex

WHMCS Technical Analyst II
  • Content Count

    167
  • Joined

  • Last visited

  • Days Won

    5

WHMCS Alex last won the day on May 13

WHMCS Alex had the most liked content!

Community Reputation

25 Excellent

2 Followers

About WHMCS Alex

  • Rank
    WHMCS Technical Analyst II

Recent Profile Visitors

3625 profile views
  1. Hello @aknight, This guide will help you get that resolved: https://help.whmcs.com/m/v82/l/1420755-resolving-a-down-for-maintenance-error The tblupdatelog table in the database should provide you with more information on why the update failed. I hope this helps.
  2. Hi @jeebee123, Do you have the Sync Next Due Date option enabled? A synchronisation of the Expiry Date but not Next Due Date suggests you have the Domain Sync Enabled option enabled, but the Sync Next Due Date option. If you do have that enabled, please review the Domain Synchronisation report that is emailed out to all administrators who have the System Emails option enabled in their role for further information. I hope this helps.
  3. Hi @Hosting New, This guide will help you get that resolved: https://help.whmcs.com/m/v82/l/1420755-resolving-a-down-for-maintenance-error
  4. Hi, Thanks for your post! The error references an addon module by the name of "tpl_override": Call to a member function clientarea() on null in /home/elanmy/public_html/whmcs/modules/addons/tpl_override/hooks.php:26 WHMCS does not develop or distribute a module by that name, so I would advise reaching out to the developer(s) of it with this error so they can review the error and the function being called to determine the problem for you.
  5. Hi, This issue has been resolved in version 8.3 of WHMCS: https://docs.whmcs.com/Changelog:WHMCS_V8.3.0_Beta_1 Once version 8.3 reaches stable release tier, updating to it will resolve this.
  6. Hi @persis Thanks for your post! The issue you report has been resolved in version 8.3 of WHMCS: https://docs.whmcs.com/Changelog:WHMCS_V8.3.0_Beta_1 Once version 8.3 reaches stable release tier, updating to it will resolve this.
  7. Hi @tkalfaoglu, You will want to execute this SQL query (after you have taken a backup of the database): UPDATE tblhosting SET server = 'NEW_SERVER_ID' WHERE server = 'OLD_SERVER_ID'; Where "NEW_SERVER_ID" is the ID of the server you want all clients to be associated with and "OLD_SERVER_ID" is the ID of the server you intend to remove. You can easily find the ID's by looking at the tblhosting.id value of the database. Once that query executes and all clients are associated with the one server, you can remove the duplicate server from inside WHMCS. I hope this helps.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
×
×
  • 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