Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About WHMCS Peter

  • Rank

Recent Profile Visitors

1,045 profile views
  1. WHMCS Peter

    I am Ayush Khanna

    Welcome to the WHMCS.Community, @ayushkhanna! It's good to have you here!
  2. WHMCS Peter

    Where to Add Code in Example Module?

    Hi @WisTex, For addon pages available within the Admin Area, you would need to add this to ~/lib/Admin/Controller.php - https://github.com/WHMCS/sample-addon-module/blob/master/modules/addons/addonmodule/lib/Admin/Controller.php In the WHMCS Admin Area, the url would look like ~/admin/addonmodules.php?module=addonmodulename&action=page - the action variable calls the function in Controller.php. For example, if you added the following function to Controller.php: public function mynewpage($vars) { $message = "Hello World!"; echo $message; return; } This would allow you to view "Hello World" from ~/admin/addonmodules.php?module=addonmodulename&action=mynewpage Naturally, addonmodulename would be the name of your module. I hope this helps!
  3. Hi there, If you are receiving a blank page in the Admin area after upgrade, this does indeed indicate that the template is no longer compatible. You can update the template for all of your admins quickly by running the following SQL query. Bare in mind that we recommend taking a database backup before performing any manual database query, regardless of how basic it may be. UPDATE tbladmins SET `template` = 'blend'; This will update all admins in tbladmins to the blend theme with immediate effect. If you are still receiving a white page after this, it may be that a stray admin dashboard widget was left on your system. Check ~/modules/widgets/ for a file called "system_overview.php". If this is there, go ahead and remove it. If this does not resolve it, also ensure you have no files in /lang or /admin/lang with "update" in the filename. This can also cause this. I hope this helps!
  4. WHMCS Peter

    UpdateTransaction API, do nothing?

    Hi there! Thanks for posting. Due to the sensitive nature of some information we'd require to troubleshoot this with you, could you open a Support Ticket with us? We'd like to take a closer look in to what is occurring here. When submitting the ticket, could you please provide all parameters that you have sent and their values, access to your WHMCS installation and FTP/Web Hosting Control Panel access if possible. This will allow us to assist you in the most effective way. Thanks! Peter Technical Analyst
  5. WHMCS Peter

    Email Verification/ File Attachment issue

    Hi @Ambarella, I think it's best that you open up a Support Ticket so that we can look in to this in detail for you if you believe your directory paths are correct. When opening the ticket, please make sure you provide WHMCS and FTP details to ensure a speedy resolution! We're here to help and we'll surely get everything sorted for you. 🙂 Best Regards, Peter
  6. WHMCS Peter

    Cron job failure email notification

    Hi @thisismatt, Indeed, this indicates that the issue is resolved for now. This issue can sometimes occur when your MySQL server has "Gone Away" before the transaction could be completed. This happens when a cron takes a lot longer to process for example. You could always check your MySQL servers `wait_time` and `interactive_timeout` values, just to make sure they are not too low. If you do run in to this issue again, do open a Support Ticket while it is occurring. We'll be able to take a closer look in to your environment and hopefully pinpoint the cause for you.
  7. Question: How can I set up Office365 to effectively work with WHMCS' Email Piping feature? Office365 (herein referred to as "O365") offers an external email service provided by Microsoft that isn't hosted on the same server as WHMCS. This means the standard method for importing emails received to an O365 mailbox into the WHMCS support ticket system is to use the POP3 importing method. You may like to use the Email Piping option instead. This guide shows how this can be achieved using O365 and a cPanel server. As O365 is an external service that isn't hosted on the same server as WHMCS, to achieve the best results, this will require a second domain name. This can be anything you like. Nobody ever needs to see or know about it. For this example, whmcs.COM is my main domain (connected to O365) and whmcs.NET is my secondary domain (Emails hosted in cPanel with WHMCS - Notice the different TLDs). Today, we will be setting up whmcs.net to pipe emails from whmcs.com email addresses to WHMCS. The steps are fairly straightforward: Create a forwarder for your "Pipe" email in cPanel It's important to immediately note that cPanel does not require an email address to be set up in order to use Email Forwarding therefore, we won't be running through these steps. You only need one "Pipe" email address. WHMCS will be able to determine which email address a message was originally sent to before your "Pipe" email. The first thing we need to do is log in to cPanel. This is fairly straightforward and the easiest way is via one of two ways: - Via a redirect: Navigate to https://yourdomain.com/cpanel - Via a dedicated subdomain: Navigate to https://cpanel.yourdomain.com Once you have logged in to cPanel, you will need to navigate to the Email category and click "Forwarders". From inside the "Forwarders" page, click "Add Forwarder" Add a new Forwarder - In "Address to Forward", choose a name for your pipe email - We used "tickets" (This email can be absolutely anything you like however) which will create a forwarder for "tickets@whmcs.net" - Click "Advnaced Options" to show further forwarding options - Select "Pipe to a Program" and in put the path to your "pipe.php" file. (Pro Tip: You can get this from Setup >> Support >> Support Departments at the top of the page!) You will receive a success message similar to: "All email sent to ”tickets@whmcs.net” will now be copied to “|/home/whmcs/public_html/whmcs/crons/pipe.php”." That's it! You've finished configuring your "pipe" email. Create a shared mailbox on O365 with your publicly visible support email address. To perform the following tasks, you must be an Organisation Administrator on Office365. If you are not, please ask your System Administrator to perform these steps: In the O365 Admin Area, click "Groups" on the sidebar and select "Shared Mailboxes". You can find the Admin Area for O365 by navigating to https://portal.office365.com and clicking the "Admin" tile. Click "Add a Mailbox" - A new sidebar will open. - In here, set up your new Shared Mailbox. For example: - Name: WHMCS Support (Or any other name you are using for your Support Department, e.g. Sales) - Email: support@whmcs.com - We used "support" because the department we're setting up will be "Technical Support". - Make sure to click "Add" once you're ready to create this mailbox. Once created, this is the email address you must use in your Support Department configuration. Pro Tip: Occasionally, it may take up to 15-20 minutes for O365 to provision your new Shared Mailbox. You may need to wait until this has been completed before you can move on to the next step. On the "Shared Mailboxes" page, click on your newly created Shared Mailbox to edit it's settings. In here, you'll need to find "Email Forwarding" and click "Edit" Configure your Email Forwarder to forward to your "Pipe" email hosted on your cPanel server with WHMCS. - Enable the "Forward all email sent to this inbox" setting - Input your "Pipe" email into "Forwarding Address" - Disable "Keep a copy of forwarded email in this inbox" (Unless you want to keep the originals for any reason - Records perhaps?) - Save the changes. That's it. You're done! So how exactly does this work? When O355 forwards the email to your cPanel server, it retains the original "To" address. WHMCS reads the original email headers and so will be interpreted as being sent to support@whmcs.com, even though you are piping it in via tickets@whmcs.net. As long as the email address that the message was originally sent to is configured in a Support Department (in this case support@whmcs.com), WHMCS will import the email in to this department. Emails sent from WHMCS will show the "From" address of the Support Department (e.g. support@whmcs.com) and so nobody will ever see or know about your tickets@whmcs.net email address. Step-by-step the processing work like this: For example: Your client sends an email to support@whmcs.com Office365 receives this email, acknowledges that you have a forwarder active and passes the message over to tickets@whmcs.net Your cPanel mailserver which houses tickets@whmcs.net receives the email and delivers it. The email still shows that it was to support@whmcs.com. As your cPanel server delivers the email, it is piped by your forwarder in to WHMCS. As the email still looks like it was sent to support@whmcs.com, WHMCS knows exactly which department to open a ticket in. Success! Your email is received and processed by WHMCS.
  8. WHMCS Peter

    HOW to Change Admin Password???

    Hi Johnny, This indicates that the email address set up in your Admin account is also set up for a Support Department in Setup >> Support >> Support Departments. Having this email associated with an account or vice-versa can cause undesirable effects to WHMCS operations and as such, is disallowed. We do not recommend any manual interaction with the database to override this feature. Instead, use a different email address for either your admin account or Support Department. I hope this helps.
  9. WHMCS Peter


    Hello, Unfortunately, the functionality you're looking for here is not something that is currently offered by the WHMCS API. However I can see how an API call to retrieve client notes could be useful. Therefore I would encourage you to please submit a request to our feature requests tracker where other users can contribute to and vote on your idea. Ideas with the most votes and activity do get reviewed by our team. http://requests.whmcs.com In the meantime, you could use a query such as: SELECT * FROM `tblnotes` WHERE `userd` = 'WHMCSCLIENTID'; Naturally, you'll need to replace "WHMCSCLIENTID" with the ID of a client (tblclients.id)
  10. WHMCS Peter

    Error after update to 7.6 on admin login

    Hi @arobo, Thanks for posting in the WHMCS.community! I can confirm that when you are presented with an error like this, the first PHP error is usually the most helpful. In this case: Error: Call to undefined method WHMCS\\Admin::getRoleID() in /xxxxx/widgets/system_overview.php:156 This shows that there is an undefined method in a specific file. As this file is located in /modules, this indicates that it is likely one of two things, an outdated file or a problematic third-party addon. In this case, this file is outdated and no longer shipped with WHMCS. EDIT: This is a very old Admin Dashboard widget was shipped with WHMCS v6.x - This has been replaced by the overview.php file. You should create a new directory called ".disabled" in the same directory that the file lies and then move the file specified in to .disabled - Moving this file from /xxxxx/widgets/system_overview.php to /xxxxx/widgets/.disabled/system_overview.php disables the file but does not remove it, just in case you need it later. I'm happy to confirm that it is safe for you to permanently delete this file. (/xxxxx/widgets/system_overview.php) I hope this helps.
  11. WHMCS Peter

    Many of the new fa fonts broken

    Hi @tap0le, I'd recommend checking out our latest GitHub commits, linked in our Release Notes under "Template Changes". This shows all of the updates required to templates to ensure they work correctly with WHMCS at the latest version. You can find the v7.6 Release Notes here: https://docs.whmcs.com/Version_7.6.0_Release_Notes Each time we release a new version, we list in our Release Notes if we have made any changes to our stock templates which will affect WHMCS functionality so that custom templates may be updated too.
  12. WHMCS Peter

    Update from v7.5.2 to v7.6 don't work

    Hi @redit, We're glad that you've got this resolved. We find that sometimes users upload the files as root and then forget to change the ownership (chown) to the user in which the webserver runs under. Because the files are uploaded as root, they are owned by root until such time those permissions are updated. Again, we're glad you got it resolved and thanks for the update!
  13. Hi all, As per @WHMCS John's message above, please enable the slow query log in MySQL and share the results. If you're not happy sharing the results here, please feel free to submit a ticket. The slow query log allows us to effectively troubleshoot if MySQL interaction is causing the slowdown of WHMCS on your servers. @yggdrasil - Please feel free to share your ticket ID and I'll be happy to take a look at it. If you'd be happy to, it would be great if you could also provide the output of a MySQL slow query log to ensure we effectively troubleshoot the issue.
  14. Hi Jan38, Thanks for posting in our v7.6 forum. It sounds like your server isn't able to process "Full Friendly URLs" correctly. Please review the following troubleshooting guides for assistance resolving this: http://help.whmcs.com/m/80786/l/949908-troubleshooting-problems-accepting-eula-after-update http://help.whmcs.com/m/73533/l/814258-troubleshooting-a-404-error-after-updating
  15. WHMCS Peter

    DecryptPassword API broken

    Hi Nathanael, Client passwords are (and have been since around version 6) hashed and encrypted in an irreversible manner. This was done to protect the security of said passwords. The DecryptPassword API call is designed for decrypting service passwords. There is no longer any way to decrypt Client passwords as the reversible encryption functionality was removed from WHMCS entirely. In short, I can confirm that this is by design. I hope this helps.

Important Information

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