Home>Support>Testing the Contact Form widget locally

Testing the Contact Form widget locally

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

I have a few questions about the SiteOrigin Contact Form widget as I would really like to use it for the site I’m working on.

I came from here https://siteorigin.com/thread/contact-form-test-shows-success-but-no-email-arrives/

I’ve have used Contact Form 7 before for other builds, but I’d like try this out to see how it holds up. Since I am not too familiar with setting up local environments, I’m using WAMP.

I’m currently having an issue with sending emails from my local dev. I get “Error sending email, please try again later.” when I fill out the form and send.

Can you point me in the right direction? Would you recommend WP Mail SMTP for this like in the thread mentioned above?

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 9 years, 4 months ago Alex S
    Hi, I Work Here

    Hi Alexramsee,

    I’m not very familiar with the WP mail SMTP plugin. I would suggest instead using a simple SMTP mail server app instead. Such as Papercut which I personally can recommend.

    Just to confirm, you’re seeing “Error sending email, please try again later” via the form itself correct?

  2. 9 years, 4 months ago alexramsee

    Yes, the message only came up after I submitted the form.

    I’ll go check out papercut. Thanks.

  3. 9 years, 4 months ago Alex S
    Hi, I Work Here

    Hi Alexramsee

    This sounds like it could be a plugin conflict issue. Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.

    If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.

    Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.

    If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More