Jump to content

WHMCS John

WHMCS Support Manager
  • Content Count

    10013
  • Joined

  • Last visited

  • Days Won

    58

WHMCS John last won the day on January 12

WHMCS John had the most liked content!

Community Reputation

206 Excellent

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 @LightningHost, The function that's being declared twice getadminpermsarray is not part of the stock WHMCS code. In the past we've received reports of it being caused by an after-market module called BrixlyResellerElite. Please check your /modules directories for this module. Removing this module directory and any associated files should work around the error. If you need to continue using the module, please contact the vendor to see if there is an update available which resolves it.
  2. Version 1.0.0

    6 downloads

    An issue has been identified in the 8.4.0 release - published on 18th January 2022, that can result in an Ooops! Error at the end of the Daily Automation Cron fir users of the Stripe payment gateway in a certain condition. The error is encountered if the settlement currency of the Stripe account does not match a currency configured in WHMCS. The full error details are below: TypeError: Argument 1 passed to _stripe_isNoDecimalCurrency() must be of the type string, null given, called in /whmcs/modules/gateways/stripe.php Stack Trace: #1 /path/to/whmcs/vendor/whmcs/whmcs-foundation/lib/Updater/Version/Version840alpha1.php(0): _stripe_formatAmountFromStripe(xxxx, NULL) #2 /path/to/whmcs/vendor/whmcs/whmcs-foundation/lib/Scheduling/Jobs/Queue.php(0):WHMCS\Updater\Version\Version840alpha1::resolveIncorrectStripeTransactions() #3 /path/to/whmcs/vendor/whmcs/whmcs-foundation/lib/Cron/Task/RunJobsQueue.php(0):WHMCS\Scheduling\Jobs\Queue->executeJob()
  3. Hi @WebHostingPeople, This help guide contains steps to identify the php.ini being loaded by the cron job: https://help.whmcs.com/m/automation/l/969680-identifying-the-php-ini-used-for-in-command-line-cron-engine
  4. Hi all, This error indicates that one or more of the database schema changes was not applied during the update for some reason. Possibly a server timeout killed the update process prematurely. The query to create the field (plus the others) is located in the /resources/sql/upgrade830alpha1.sql file. Creating the missing field will resolve the error: ALTER TABLE `tblaffiliateshistory` ADD `invoice_id` int(10) unsigned NOT NULL DEFAULT 0 AFTER `affaccid`; As always, before making changes to the database, please backup.
  5. Hi all, Thanks for sharing your feedback on the OX App Suite offering, particularly with regards to the email service. We've been sharing this with the OX team, and we hear your comments loud and clear. We've worked with customers and OX directly on the problem, and in December 2021, OX upgraded to the latest and greatest version of its AVAS software. Since then we’re happy to say the results have been extremely promising; as spam issues have subsided significantly. Our apologies for the inconvenience you may have experienced in the past, but the feedback we're getting since the upgrade is much more positive. We'd love for you to try OX App Suite again, and we're currently running a 100% Rebate offer on all orders placed before the end of March: https://marketplace.whmcs.com/promotions
  6. Version 1.0.0

    9 downloads

    An issue has been identified in the 8.4.0 release - published on 18th January 2022, that can result in an Ooops! Error in the client area on systems running older versions of Ioncube Loaders. The full error details are below: Whoops\Exception\ErrorException: Declaration of WHMCS\View\Menu\Item::setLabel($label): Knp\Menu\ItemInterface must be compatible with Knp\Menu\MenuItem::setLabel(?string $label): Knp\Menu\ItemInterface in /home/541340.cloudwaysapps.com/gfggjvawbn/public_html/vendor/whmcs/whmcs-foundation/lib/View/Menu/Item.php:0 Stack trace: #0 /path/to/whmcs/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\Utility\Error\Run->handleError(64, 'Declaration of ...', '/home/541340.cl...', 0) #1 [internal function]: WHMCS\Utility\Error\Run->handleShutdown() #2 {main} Details of solutions which do not require the hotfix are available at Troubleshooting a Declaration of WHMCS\View\Menu\Item::setLabel($label) Error
  7. Hi @markc, You might be able to observe more error details returned from PayPal by examining the Response section in your browser's Network Analyser tool. We have information on using this here: https://help.whmcs.com/m/troubleshooting/l/1312423-an-error-occurred-while-communicating-with-the-server-please-try-again How were the clients imported into WHMCS please? If no password was set upon importing, it's possible that there's nothing for the Login as Owner operation to authenticate against. Is there an Owner listed for the affected Client Accounts under their "Users" tab?
  8. @WebHostingPeople, That is correct. The Pay To Text is not client details, so won't be fixed by the Client Data Snapshot feature. If you need to display different Pay To Text based upon invoice date, consider editing the viewinvoice.tpl and invpocepdf.tpl templates and adding the old text conditionally: https://developers.whmcs.com/themes/conditionals/
  9. The details of and solutions to common errors which may be encountered when applying the 8.4 update have been published in our dedicated 8.4 updates section: 8.4 Update Troubleshooting Please review these guides before posting or opening a support ticket, as your question may already be answered.  Further self-help for update issues is located at: https://help.whmcs.com/m/updating General troubleshooting guides are located at https://help.whmcs.com/m/troubleshooting
  10. Hi all, I can confirm that CORE-14055 was resolved in 8.4.0 Beta 1. We'll get the release notes updated shortly, My apologies for the confusion.
  11. Hi @ocastaned, We've not currently aware of any issues preventing the Bulk Pricing Updater from updating domain pricing. Can you provide some details on how it's not working? What criteria are you entering, and what is the record not being updated which you expect? Do bear in mind that the only the domains which exactly match the conditions you specify will be updated.
  12. What's new in WHMCS 8.4: Faster WordPress Hosting Checkout - A quicker checkout experience for customers purchasing WordPress Hosting - Learn More Open-Xchange Mailbox Aliases - Create and Manage Email Aliases from the WHMCS Client Area - Learn More Digicert Site Seals - SSL Certificate Site Seal Code now available in the WHMCS Client Area - Learn More Optimized Merchandising for SSL Products - Enabling you to promote your best performing SSL products Automatic Updater Improvements - Additional pre-flight checks to help ensure a successful update - Learn More For more information about the new features in WHMCS 8.4, visit the What's New in WHMCS 8.4 Microsite
  13. Hi @WebHostingPeople I'm pleased to see that our support team were able to help explain the Billing Logic operation, and how deleting invoices was blocking further invoices from being generated. In the broad context; WHMCS will never generate duplicate invoices for the same service on the same Next Due Date. If a service renewal invoice is deleted, but you wish to generate a new invoice for a similar period, edit the client's Products/Service to move the Next Due Date forward by 1 day, then Save Changes. This will allow a new invoice to be generated for almost the same period. Additionally it was my personal pleasure to explain the operation of the Store Client Data Snapshot feature in the follow-up questions in your ticket. If you have any further questions, please don't hesitate to get back in touch.
  14. Hi @daniel va, If the issue occurrs at 00:00 every day, then most likely the daily automation tasks at midnight are consuming all the available resources on your hosting account. I recommend working with your server admin/hosting provider to increase available virtual CPU and memory resources. Additionally, what options are configured under Configuration > System Settings > Database Backups? To hazard a guess, the backup process might be using up PHP resources. Consider disabling Email and FTP Backup, and switching to the cPanel Backup option instead: https://docs.whmcs.com/Backups#cPanel_Backup
  15. Hi @Joelj, How have things been going with the backup disabled? If it's been working since, then it would indicate the backup generation was using up all the available resources on your hosting account. To confirm, you can re-enable it and run the daily automation tasks from the command line , this should show a resource exhausted error on-screen: https://help.whmcs.com/m/automation/l/683269-advanced-cron-troubleshooting If you don't have WHMCS installed on a cPanel server, then I can suggest exploring other external backup options which don't require PHP to operate as an alternative (such as Jetbackup).
×
×
  • 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