Home>Support>Not getting email inquiry

Not getting email inquiry

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].

We are currently using SiteOrigin for some of our online contact pages.

https://www.1st-line.com/parts-inquiry/

https://www.1st-line.com/contact-us/

Everything seems to work ok when we test it. However we are getting calls from people who say they sent an inquiry and never got a response. When we search through our emails, we can’t find them. Every time I hear a call I test it on my computer and of course it works ok.

I tried using the “”contact us”” form on my cell phone and the page refreshed and I didn’t get the email inquiry. I noticed the URL changed. It added “#contact-form-5555” to the end of the URL.

https://www.1st-line.com/contact-us/#contact-form-5555

When I try to fill our the form again, then I get the “success” message. I do receive the email and the URL adds “,contact-form-5555” to the end.

https://www.1st-line.com/contact-us/#contact-form-5555,contact-form-5555.

The end part seems to change every time I use it.

Any idea what what the issue could be?

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

  1. 6 years, 9 months ago Andrew Misplon
    Hi, I Work Here

    Hi Gregg

    Email delivery issues are common across all contact form plugins. The problem isn’t the plugin in question but most often has to do with deliverability from your server. The best way to resolve this is to use an SMTP plugin like https://wordpress.org/plugins/wp-mail-smtp/.

    Here is a guide: https://www.wpbeginner.com/plugins/how-to-set-up-wp-mail-smtp-with-any-host-ultimate-guide/

    Hope that helps.

  2. 6 years, 9 months ago Gregg

    Hi Andrew,

    Thanks for the reply. I contacted my web host. They looked into it and were able to fix the issue. It had to do with the page being cached (or not being cached).

  3. 6 years, 9 months ago Andrew Misplon
    Hi, I Work Here

    Super, really glad to hear you were able to resolve the problem. Thanks for letting us know.

    All the best :)

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