iank Posted October 5, 2017 Share Posted October 5, 2017 Hi, Didn't know where to post this, so have gone for this subforum. I have a few PW sites with a UK host, on a Reseller account. They are all using a combination of Formbuilder and WireMailSMTP to send the results of enquiry forms. I have WireMailSMTP set up with my Mandrill account settings, and everything worked fine. Nothing too unusual here. I have similar setups on another host, everythings OK. A couple of days ago the first hosting company (and my preferred one) upgraded the cPanel to include EasyApache and the ability to easily switch PHP versions. I think they're going to provide LetsEncrypt shortly too, but that's unrelated. Suddenly, the system has stopped using SMTP and appears to be sending via the default WireMail settings/PHP mail. The mails are getting sent (as far as I can see), but not going through the Mandrill authenticated route, so some are getting into junk mail folders. I try the same site/codebase on my internal development system and it still sends via WireMailSMTP's Mandrill settings, but not on the live host. PHP versions are slightly different, but both 5.4 variants. What's even weirder is that during troubleshooting I set up a hook to WireMail::send to see if I could log which class it's using (and other params). This works fine on the local dev system and shows all the expected settings. On the live system, the hook doesn't even fire, so I can't confirm it's using WireMail's send() even. The hosting company have been quite helpful and we've spent all day trying to resolve this, but they've run out of ideas and I'm getting to the same point. Can anyone throw any possible light/offer any suggestions? Much appreciated, Ian. Link to comment Share on other sites More sharing options...
iank Posted October 6, 2017 Author Share Posted October 6, 2017 (edited) Still haven't resolved this. Some further information which may be of help: PW Version 3.0.62 Formbuilder Version: 0.3.0 WireMailSMTP Version 0.2.5 (was 0.2.2 but upgrading made no difference). PHP Version was 5.4.28 on dev, 5.6.31 on live. Tried switching to 5.4.45 on live, no improvement. Still not sending via SMTP, and still not able to hook WireMail::send on live. Have attached Tracy Debugger but no obvious errors detected. Update: I'm getting a bit closer to the root of the issue. When FormBuilder comes to send, it does a check to see if the wireMail function exists: if(function_exists('wireMail')) { ... $result = wireMail(...) } else { ... $result = @mail(....) } So I put some breakpoints in and it transpires that function_exists('wireMail') is returning false on my newly upgraded cPanel hosted sites. The reason that I can't hook is that it then goes on to use the mail() method directly, bypassing WireMail completely. ... so why would the function_exists() return false all of a sudden? What could change in PHP that would create this issue? I may cross-post this last updated info in the FormBuilder forum; hopefully Ryan can pick it up and provide some insight. Edited October 6, 2017 by iank Update 1 Link to comment Share on other sites More sharing options...
iank Posted October 9, 2017 Author Share Posted October 9, 2017 Update: It seems that function_exists() is broken in some way on PHP 5 versions in this particular hosting environment. It returns false when passed a namespaced function name (as per the FileCompiler compiled module files). It should return true, as the function is certainly present and callable. I've done some tests and it's not Processwire related; the same issue is present in vanilla PHP scripts. If I switch to PHP 7 function_exists() once again behaves as expected. 3 Link to comment Share on other sites More sharing options...
cstevensjr Posted October 9, 2017 Share Posted October 9, 2017 You should be commended on sticking with the troubleshooting. I'm glad you finally got to the root of the problem. 2 Link to comment Share on other sites More sharing options...
iank Posted October 9, 2017 Author Share Posted October 9, 2017 6 hours ago, cstevensjr said: You should be commended on sticking with the troubleshooting. I'm glad you finally got to the root of the problem. Ha, thanks! I'm not a 'proper' programmer but I don't like it when I can't establish a logical explanation. It's been raised as a fault to the hosting team and they're looking into it.. 2 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now