pKris Posted November 23, 2022 Share Posted November 23, 2022 Hey all! We recently upgraded to WHMCS 8.6, and all is well except for a few issues. Occasionally a ticket will throw an error when opening it, this ticket could be brand-new or days old with many replies in it: TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in /var/www/html/ponyboy/supporttickets.php:0 Stack trace: #0 /var/www/html/ponyboy/supporttickets.php(0): in_array() #1 {main}\] I can still access the ticket via the WHMCS mobile app, it's just the browser that complains. 0 Quote Link to comment Share on other sites More sharing options...
sonuyos Posted December 2, 2022 Share Posted December 2, 2022 Same, facing this issue too. 0 Quote Link to comment Share on other sites More sharing options...
DennisHermannsen Posted December 2, 2022 Share Posted December 2, 2022 Are you able to reproduce the error by doing specific steps? Giving all information possible will most likely result in a quick fix from WHMCS. 0 Quote Link to comment Share on other sites More sharing options...
pKris Posted December 2, 2022 Author Share Posted December 2, 2022 1 minute ago, DennisHermannsen said: Are you able to reproduce the error by doing specific steps? Giving all information possible will most likely result in a quick fix from WHMCS. Sadly no, it is an issue that may happen once in a blue moon - we could have a ticket open with a customer and be communicating back and forth on it for days when all of the sudden this pops up. 0 Quote Link to comment Share on other sites More sharing options...
DennisHermannsen Posted December 2, 2022 Share Posted December 2, 2022 (edited) That specific error just seem like it would happen in a very specific case. Does the client attach anything? Are they trying to add a CC? Also, does it happen on 8.6.1 as well? Edited December 2, 2022 by DennisHermannsen 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted December 14, 2022 WHMCS Support Manager Share Posted December 14, 2022 Hi all, I can confirm this issue was resolved in v8.6.1: Quote CORE-18286 - Prevent error in PHP 8.1 on ticket observer requests https://docs.whmcs.com/Changelog:WHMCS_V8.6.1 0 Quote Link to comment Share on other sites More sharing options...
sol2010 Posted March 26, 2023 Share Posted March 26, 2023 Hello I am running 8.6.1 and also just got this error: A message that you sent could not be delivered to one or more of itsrecipients. This is a permanent error. The following address(es) failed: pipe to |/home/user/WHMCS/crons/pipe.php generated by email@addressexample.co local delivery failedThe following text was generated during the delivery attempt:------ pipe to |/home/user/WHMCS/crons/pipe.php generated by email@addressexample.co ------TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in /home/user/public_html/whmcs/includes/ticketfunctions.php:0#0 /home/user/public_html/whmcs/includes/ticketfunctions.php(0): in_array('Closed', NULL)#1 /home/user/WHMCS/crons/pipe.php(0): processPipedTicket('email@addressexam...., 'email user name .', 'Re: [Ticket ID:...', 'Hi there\n\nWednes...', '733731_SM-Logo....', Object(WHMCS\Mail\AutoSubmittedHeader), Array)#2 {main} 0 Quote Link to comment Share on other sites More sharing options...
Weeb Fluffy Posted July 6, 2023 Share Posted July 6, 2023 Hello there Sorry for reviving this post This happened to me recently with WHMCS 8.7.3 and PHP 8.1 It happened when a user opened a ticket through an email and between the round trip emails they added 2 people from the organization to the ticket and that is when the error appeared. Whenever the recipient of the email is more than one person and does not have permissions in the ticket, whmcs throws me the error. To solve it, we proceeded to register the 2 people of the organization as part of support and with permissions in the ticket office. After that I stop throwing errors and I manage to import the emails correctly. Another problem that this generated is that every time the email piping cron was executed, it imported again the same emails that were throwing an error. Hope this can help someone experiencing the same thing Email Import Log: 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.