eForm not sending email after Evolution 1.0.8 upgrade??

I recently upgraded one of our client's sites from Evolution 1.0.7 to Evolution 1.0.8 and all of the forms using the eForm snippet have stopped sending email. Thankfully, the onValidate function we're using to populate a database table with the entries is still working, but it would still be nice if the emails went through as well.

Any suggestions/help would be greatly appreciated.

The 1.0.8 update only changed the Forgot Manager Plugin so unless you had a corrupt upload of something in the eForm folder or overwrote some customisation in the eForm snippet it's difficult to see how the upgrade would have been the culprit.

I know I lost more than one email feature when upgrading and overwriting an eForm that had been customized to use SMTP mailing instead of the PHP mail() function that eForm comes with.

Quote from: bunk58 at Feb 20, 2013, 04:30 PM

The 1.0.8 update only changed the Forgot Manager Plugin so unless you had a corrupt upload of something in the eForm folder or overwrote some customisation in the eForm snippet it's difficult to see how the upgrade would have been the culprit.

Thanks for the response. I've initiated a support ticket with the hosting provider, but I do find it a bit odd that the last successful message I received from the site was on the same day that I did the portal upgrade. I have also tried re-uploading the eForm folder, but it hasn't made a difference.

Quote from: sottwell at Feb 20, 2013, 04:51 PM

I know I lost more than one email feature when upgrading and overwriting an eForm that had been customized to use SMTP mailing instead of the PHP mail() function that eForm comes with.

Thanks for responding. The site forms are using the PHP mail() function that comes with eForm and I haven't done any customization other than to capture form information to a database table (which is still working)

the same day that I did the portal upgrade

That sounds like more than upgrading MODx, unless I'm not understanding correctly.

Quote from: bunk58 at Feb 21, 2013, 03:35 PM

the same day that I did the portal upgrade

That sounds like more than upgrading MODx, unless I'm not understanding correctly.

Sorry, substitute portal with MODx upgrade.

Hi Jeffb01 and Susan
I appear to be experiencing the same set of problems. After upgrading Evo to 1.0.8 from 1.0.5 the email confirmation that is sent via SwiftMailer 4.0.6 stopped sending (all other functions of the site work fine). To confuse matters, I also migrated the site to a new host around the same time and have also opened a ticket with them regarding this problem and potential php-mail server setting conflicts. As far as I can tell it appears that the script stops processing at the mail section and does not complete the rest of the functions after it. I have reinstalled the Swiftmailer library which did not rectify the problem.
I have exhausted my limited MODx/php abilities and was hoping you had further insights into this.
I can provide the affected snippet if it will assist.

Quote from: jeffb01 at Feb 21, 2013, 01:35 PM

Quote from: sottwell at Feb 20, 2013, 04:51 PM

I know I lost more than one email feature when upgrading and overwriting an eForm that had been customized to use SMTP mailing instead of the PHP mail() function that eForm comes with.

Thanks for responding. The site forms are using the PHP mail() function that comes with eForm and I haven't done any customization other than to capture form information to a database table (which is still working)

If you upgraded the eForm snippet, it overwrote your modified version that used swiftmailer. Normally eForm uses the phpmailer class from /manager/includes/controls. If you had eForm modified to use SMTP, that also was overwritten to use the default php mail() function.

When doing modifications to a standard installed snippet, it's best to actually clone it by copying the whole assets/snippets/eform directory as well as the snippet in the Manager, then rename your cloned version eg. smtpForm, directory and snippet, then use that snippet instead of eForm. That way when you upgrade, you don't have to worry about overwriting your modifications.

Hi Susan
Thank you for your reply.
I checked the new versions of the eForm and swiftmailer snippets against the original versions and did not find any code modifications that would have impacted on their respective functions. I have since reverted to installing PEAR onto the new host server and use SMTP auth to process the confirmation emails, which now works (save for a couple of minor oddities that I will post separately).
While still being a relative novice with all this, I suspect it was more of an issue with the new host servers configuration and PHP settings than with the eForm snippet. I do note and appreciate your advise regarding the practice of cloning any snippets for modification purposes and thank you for your help with this.