Jump to content

Piping.php PHP Deprecated: preg_replace():


mwaraitch

Recommended Posts

WHMCS 6.1.1

System check indicates server configuration matches all needs of whmcs.

Email piping issues:-

Email piping set using email forwarding in Cpanel, is working ok.

Tickets are generated / replied back, However, for tickets generated through email, the user gets 2 response, 1 is usual auto responder (set at whmcs) and second is a bounced back emails indicating error message as showing blow for advice, if some one can advice.

-----

 

The following text was generated during the delivery attempt:

 

------ pipe to |/home/user/public_html/crons/pipe.php

generated by sales@dmain ------

 

 

PHP Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/user/public_html/crons/pipe.php on line 0

 

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/user/public_html/crons/pipe.php on line 0

 

PHP Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/user/public_html/crons/pipe.php on line 0

 

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/user/public_html/crons/pipe.php on line 0

Edited by mwaraitch
Link to comment
Share on other sites

Sorry for late reply, due to some reason the forum here would not allow me post after login. The reply area for quick reply and reply to thread would just remain grey and sort of locked.

 

Its was php5.5 and resolved on setting php 5.4. However, that did not resolve the issue in totality. User still continue to get 2 messages, one is the responder set in whmcs (meaning mail is getting through) and other is mail delivery failure notice given below. I had whmcs staff check it and they think its due to issues are server (cagefs not exiting properly) while my server admin says its due to php script as they moved the out out of cage and the issue continued. I am not sure of next step at the moment, may be the alternate mean of piping through cron can work (though that is not recommended by whmcs for cpanel, single domain) Or may be I can now move to Cpanel people as they are one of the party left in this. Tried advice of "Resetting permissions of /usr and /usr/bin to 755, Deleting all old autoresponders - - example : /home/USER/.autoresponder.useremail@userdomain.com.data at https://forums.cpanel.net/threads/cagefs-and-autoresponders.502021/

 

 

The email send to whmcs are still bouncing though with following message:

 

This message was created automatically by mail delivery software.

 

A message that you sent could not be delivered to one or more of its

recipients. This is a permanent error. The following address(es) failed:

 

pipe to |/home/username/public_html/crons/pipe.php

generated by sales@domain

 

The following text was generated during the delivery attempt:

 

------ pipe to |/home/username/public_html/crons/pipe.php

generated by sales@domain ------

Edited by mwaraitch
Link to comment
Share on other sites

  • 3 months later...

Move whmcs to another server, worked ok for a while, however, appeared again.

 

How to reduce the error_reporting level in your PHP configuration to not output depreciated warnings?

WHM >> Service Configuration » PHP Configuration Editor >> Advance mode >> error_reporting has following entry:

E_ALL & ~E_NOTICE & ~E_DEPRECATED

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • 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