Home>Support>Google Maps Widget: There were no results for the place you entered.

Google Maps Widget: There were no results for the place you entered.

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’ve been trying to implement the Google Maps widget on our site. The SiteOrigin Widgets Bundle came included with my theme (Create by Themetrust), but the map doesn’t seem to be working. In the widget preview, everything renders correctly, but on the actual site I get a message reading “There were no results for the place you entered. Please try another.”

I haven’t at all been able to isolate the cause of the problem, there don’t appear to be any plugin conflicts, and every other SiteOrigin widget I’ve used seems to function with no issue. Please advise.

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, 3 months ago Andrew Misplon
    Hi, I Work Here

    Hi Weecare

    Very sorry about the late reply. We work through a prioritized forum queue, and unfortunately it’s taken us some time to get to your thread.

    https://siteorigin.com/about/forum-thread-prioritization/

    Because it’s been a while since you posted this, would you mind letting us know if you still need help? If so, we’ll jump right in.

  2. 9 years, 3 months ago weecare

    Yes, we definitely still need this sorted out.

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

    Hi Weecare

    Would it be possible for you to create a temporary admin account for us so we can log in and take a look? You can create the account with the following email address:

    [email protected]

    Just navigate to UsersAdd New in your WordPress admin. Enter siteorigin for the username and [email protected] for the email address. Make sure you’ve selected Administrator for the role and enabled the Send Password field so we receive the details.

    Once we’re finished taking a look, you can delete this account. We’ll let you know when to do that.

  4. 9 years, 3 months ago Private Message - WordPress

    This is a private message.

  5. 9 years, 3 months ago Private Message - WordPress

    This is a private message.

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

    Thanks :) Please, change our user role to Administrator and we’ll take a look ASAP. We’re based in Cape Town, South Africa, our timezone is GMT+2. I’ll take a look as soon as we’re on again in the morning.

  7. 9 years, 3 months ago weecare

    Apologies, I made you a user on our Network, not the actual site. Just a moment, I'll correct.

  8. 9 years, 3 months ago Private Message - WordPress

    This is a private message.

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

    Thanks. After testing on your site and locally it appears that this might be a plugin conflict. Please, try working through the steps outlined below:

    //

    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.

  10. 9 years, 3 months ago weecare

    Hi Andrew,

    Thanks for your help. Turns out it was a conflict with the W3 Total Cache plugin. Everything looks good to go again!

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

    Nice find! If you wanted to dive into the settings of W3 Total Cache you might be able to locate the particular issue. Perhaps it was JS minification? If you wanted to dig deeper we could perhaps assist in locating the file to exclude from minification. OR, say it was that setting you could use W3 Total Cache without JS minification turned on.

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