Fixing WordPress plug-in Pirate Form

I’ve been using a theme on another site that uses the WordPress plug-ion Pirate Forms for its contact form. The problem was that although it would say that the email was sent, the email never arrived. It took me a while, but I finally figured out the problem with Pirate Forms. When it creates the header string to send with the email, it is using the email from the form as the “from” email.

So what’s wrong with that? It’s what the sender is inputting into the form as his email. Well, apparently some servers want the email coming from a known and valid email and won’t accept what was input into the form. Fortunately, the solution is quite simple, just change the variable from $send_from to $site_email. See below:

Original line: $headers = “From: $send_from_name <$send_from>\r\nReply-To: $send_from_name <$send_from>”;

Edited line: $headers = “From: $send_from_name <$site_email>\r\nReply-To: $send_from_name <$send_from>”;

Make sure you enter a valid/known email in the Contact notification sender email field on the Pirate Forms settings Option tab.

Comments

Chris Popovic
Reply

I’m having trouble with attachments coming through. I can make the form prompt for an attachment but the attachment doesn’t come attached in the received email.

fypster
Reply

It’s still not working for me, any other suggestions? Where did you change this settings?

spice3d
Reply

I posted this ages ago. They have fixed this particular bug since then.

Jad Chahine
Reply

Hi, it didn’t work for me either. Out of all the form plugins, why did the theme have to pick pirate forms? I’ve never had a problem with forms..

Any other suggestions? I am not using smtp.

Thank you,

Jad

spice3d
Reply

Yeah, people seem to have a lot of issues with it. That said, it’s working for me and I’m not using SMTP either. Sorry I can’t help you more. The original purpose of this post was a problem they had a while ago which has since been fixed.

Laura
Reply

I tried this solution, but it still no working…

spice3d
Reply

You should update your plug-in. They have fixed this issue. If it’s still not working then it must be in your settings. The plug-in works fine for me.

Leave a Reply