Mark

Dave,

My apologies for the late response. I have followed your instructions and it does appear there’s an issue on the Console and Network. How do you want me to show the results? I tried to c/p but the results looks ugly See below.

load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-widget,jquery-ui-position,jquery-ui-core,jquery-ui-menu&ver=5.2.3:4

Mark

Pardon my use of the <p> tag. I forgot to turn off my HTML brain.

Excellent, that fixed the issue. I appreciate it. Keep up the genesis work.

I am having the same issue. It would be great to see this in the next release as I like your plugin but it distracts on the blog page.

Wrong plugin. Closing the thread as resolved in error.

My apologies.

koheiueno

You need to review the which has all the instructions to help you find the files you need to edit the code with.

Chris, glad you figured it out. The instructions needs to be updated a little bit but that was the same issue I figured out. Hopefully it will help the others.

Aye, I agree. It is important to be accessible to everyone. I love how this plugin makes links more accessible than the standard links.

I figured it out. Well, I got it working but I am not sure which one did the trick but it works now.

First thing, the instructions states to replace key=<your API Key> but google does not states you need the < > so I took that out.

Second thing, I added my domain to the approved domain list.

Third thing, I enabled the following…

Google Maps Direction API
Google Maps Distance Matrix API
Google Maps Elevation API
Google Maps Geocoding API
Google Maps Javascript API
Google Places API Web Service

Hope this helps.

Same problem here.

It’s a great plugin. So much more simpler and a LOT easier to use than the others out there.

The error message I am getting in the javascript console states,

210Google Maps API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required

I don’t know if that helps?

Yes, the Smash balloon plugin. I’m going to test the first issue later today and will reach out to you so you can see the issue.

Glad to give you a heads up.

I upgraded and the fatal call error seems to be resolved. While testing it, for some reason, the widget conflicted with my theme’s css. I need to investigate this further to see if it is an issue on my end.

It also appears to interfere with Instagram Feed plugin as it prevented the plugin from pulling the feed by staying in a loading mode. When I moved your widget out, the Instagram feed resumed as normal. I tested it again, and same results as well.

In any case, the oAuth appears to be working.

Yes, I am using all the latest versions, blah blah blah.

WP 4.5
Broken Link 1.1.4

What I did notice was when I deactivated your plugin, the inline editor did “turn off” without having to save the page. But when your plugin is activated, the inline editor does not turn off, forcing me to save the draft every time (which automatically refreshes the page) in order to clear the in-line editor.

No other plugins are interfering with this.

It does work now. I took a long hard look at the custom CSS and realized what was causing the issue. Somehow there was a duplicated .site-header in the jetpack with the 36px that was being called up first. I looked at the entire CSS and I have no idea how but there were a lot of duplicated CSS in there.

It’s all good now. I need a better way to work smarter by finding duplicate CSS. Thanks again.