Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Sorry for the delay over the holidays. We’re working on this issue currently, specifically to avoid the “mystery man” icon all together when possible. Hope to get that new release out relatively soon.

    Thanks!

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    HI there,

    Actually, we already rolled out the issue that I believed would resolve this. And on more careful review of your issue I think this isn’t about our plugin code, but perhaps how you implemented HTTPS on your site.

    Can you double-check your Site and Blog URLs in your Settings? Are those both using HTTPS? Go to “Settings > General” and provide a screenshot if you can. If they are NOT using HTTPS then the plugin can’t call it correctly. Let me know what you find.

    Thanks!

    Ward Graham

    (@eagrayhamgmailcom)

    Hi,
    I have this same issue. I recently moved my site using dev.domain.com then changed the name under general settings, DNS etc. now the mistry link sources the image from dev.domain.com rather than www. Seems like the plugin is caching. I cannot find dev.domain.com anywhere in the DB when I search via phpmyadmin. I removed and reinstalled the plugin restarted apache, cleared php cache, removed any caching/minifying plugin, tried a new API key. Even used wget to pull site locally to eliminate any client/CDN caching. in short the plugin seems to be using a FQDN from some source instead of using local links. Hope this helps. TY!

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Can you provide a link to your site so I can see the problem live? As well as screenshots of your General Settings just for confirmation?

    The widget does have built-in caching for the reviews, but not for the mystery man source. It’s possible that your migration didn’t update that setting somehow too.

    Ward Graham

    (@eagrayhamgmailcom)

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    I think it must be set in your database somehow. WE have a section of this tutorial dedicated to resolving insecure elements with a plugin called “Better Search Replace” Here’s that doc:
    https://givewp.com/documentation/resources/how-to-use-ssl-and-https-for-your-wordpress-website/

    You could use that (specifically with the “Dry Run” option) and instead search for all instances of https://dev.brighthoney.com … of course, make sure you have a backup of your database first and that you know how to restore it quickly if there’s any problems.

    Let me know how that goes. Thanks!

    Ward Graham

    (@eagrayhamgmailcom)

    Where is the plugin loading this variable from: GPR_PLUGIN_URL ? I can then use phpmyadmin to look at the specific DB entry. doing a blind search and replace is not a comfortable option as you may understand.

    $avatar_img = GPR_PLUGIN_URL . ‘/assets/images/mystery-man.png’;

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    That’s defined in the root file of the plugin and you can see that it is just using the WordPress default function for the plugin directory:

    
    $plugins_url = plugins_url();
    
    define( 'GPR_PLUGIN_URL', $plugins_url . '/' . basename( plugin_dir_path( __FILE__ ) ) );

    https://github.com/WordImpress/google-places-reviews-free/blob/master/google-places-reviews.php#L72

    So, it should be dynamic according to your core WordPress settings, but since you mentioned the migration it seems that perhaps something was cached and migrated with the old value. Bottom line is I don’t believe this is a problem with the plugin specifically but something in how things were migrated.

    Ward Graham

    (@eagrayhamgmailcom)

    found it. cleared the PHP opcode cache. Sorry I did not think of that earlier.

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Thanks for the confirmation Ward, glad you got it worked out.

    Thread Starter websitesontwerpen

    (@websitesontwerpen)

    Thanks, your tips and installing the plugin ‘Really Simple SLL‘ made everything work as hoped.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘SSL / HTTP for plugin images’ is closed to new replies.