Viewing 8 replies - 1 through 8 (of 8 total)
  • had the same problem. The urls for the scripts this plugin uses are being output like

    https://domain.comwp-content/plugins/etc....

    the / is missing after the domain name and before wp-content.

    As a temporary fix I changed line 154 of /classes/core.php from

    trim( $this->url, '/' ),

    to

    $this->url,

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Hi there,

    We just pushed an update out to the plugin, and updated our Docs. Google now requires the Maps API Key to be enabled in order to use the Lookup widget. Please do the following:

    1) Review this doc and make sure you have both the “Google Places API Web Service” and “Google Maps Javascript API” enabled on your API Key
    2) Update to the latest version (version 1.4.2)

    Let me know how it goes. Thanks!

    Did this also fix the error in the script urls? the missing / between the site’s domain name and wp-content. I don’t think that has anything to do with google.

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Hi John,

    We weren’t able to duplicate that issue anywhere. If that were an issue we’d have TONS of support requests since the plugin would fail for everyone.

    Something like that might happen if you have some custom rules in your htaccess, or wp-config.php file. Or maybe a plugin is creating a conflict somehow.

    Can you give me some details about your environment? Have you tried disabling all other plugins to see if that resolves the issue? If it does, re-activate each one, one at a time and when you find the issue again let me know which plugin caused the issue and I can look into duplicating that problem.

    Thanks!

    I have this installed on a testing site. This is the only plugin activated on the site. It is running a bare 2015 theme. This is the code that is output in the footer for this plugin on the admin page for this site.

    <script type='text/javascript' src='https://ssird5.com.php53-8.dfw1-2.websitetestlink.comwp-content/plugins/google-places-reviews/assets/js/form.js?ver=1.4.2'></script>
    <script type='text/javascript' src='https://ssird5.com.php53-8.dfw1-2.websitetestlink.comwp-content/plugins/google-places-reviews/assets/js/jquery.fitvids.js?ver=1.4.2'></script>
    <script type='text/javascript' src='https://ssird5.com.php53-8.dfw1-2.websitetestlink.comwp-content/plugins/google-places-reviews/assets/js/core.js?ver=1.4.2'></script>

    as you can see, there in no / between the domain name and wp-content

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    I see that. But I can’t duplicate that issue. For example, on our demo site:
    https://googleplacesreviews.wordimpress.com/

    Those scripts are output in the Admin correctly like you see in this screenshot:
    https://www.dropbox.com/s/rd56zvdf53xanrb/2016-07-12%2014_45_28-Developer%20Tools%20-%20http___googleplacesreviews.wordimpress.com_wp-admin_options-ge.png?dl=0

    So I’m not sure exactly why that is happening on your site. Nevertheless, I’m going to create a ticket to dig into that line you pointed out.

    Thanks!

    I tracked this down to a setting in the wp-config.php file on the site.

    define('WP_CONTENT_URL', '/wp-content');

    This is a setting put there by the hosting provider. This isn’t really something that I can change.

    This plugin should be somehow be detecting if the url returned form plugins_url() includes the domain name and it should not be stripping off the beginning/ from the value it returns. This is the first plugin that I’ve found that has a problem with this.

    Unfortunately, I can’t even add a filter to put the ‘/’ back on because this plugin strips it off after the filters for plugin_url() are run and there in no filter in this plugin that would allow me to put it back on.

    Basically, while this may not effect a lot of people, my position is that this plugin should not be stripping the initial ‘/’ from the url returned by plugins_url().

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Ya, I think you’re right about that. Now that I know exactly how that happened to you, I can test it and update our code to account for it directly.

    Thanks!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Not working – blank box’ is closed to new replies.