Address locator: No results in IE 11

Brian Oevermann

August 11, 2016 17:49

I recently upgraded our Html5 viewers to GE 4.5.1 and Html5 Viewer 2.6.1. Everything has gone smoothly.

 

Today, however, I had a user call and inquire why no results were showing up when she typed in an address in the Global input textbox. This was news to me because address matching was working for me in the browsers I regularly use--Firefox and Chrome.

 

It turns out she was using IE 11. When I used IE 11 I got the same result--no address match results. Same Viewer and Site, just a different browser. It appears to run the address match but simply reports no results found.

 

Is anyone else seeing this behavior? It appears to be a browser-specific issue and not something GE-specific but I don't know that for certain.

 

 

0

• 

  Permanently deleted user

  August 23, 2016 18:27

  Hi Brian,

   

  This is a known issue, and will be fixed in Essentials 4.6 with Core 3.0.  The tracking number is CORE-1143.

   

  I'll add you as a stakeholder!

   

  Thanks,

   

  Danny

  0
• 

  Brian Oevermann

  August 23, 2016 18:53

  Thanks, Danny. Did I just miss that entry in the known issues list? Either way I'm glad it's on track for being fixed.

  0
• 

  Permanently deleted user

  August 23, 2016 19:35

  Hi Brian,

   

  No you didn't miss it, but I'm afraid we did.  I'll get it added :)

   

  Thanks!

   

  Danny

  0
• 

  Brian Oevermann

  July 10, 2017 22:21

  Daniel,

   

  On Friday I finally updated our system to GE 4.7.1 and HV 2.8.2, expecting that CORE-1143 would be fixed. It still does not appear to be fixed and the release notes do not mention it.

   

  Can you give me a status regarding this bug? I have a couple of departments that, for various reasons, use IE as their 'standard' rather than Firefox or Chrome so this has been a critical shortcoming for them.

   

  Thanks for the update!

   

   

  0
• 

  Permanently deleted user

  July 14, 2017 16:06

  Hi Brian,

   

  That bug is still marked as fixed, but if you're still experiencing it, please open a support case so we can help you investigate, and verify if it was a regression or not!

   

  Thanks,

   

  Danny

  0
• 

  Brian Oevermann

  July 14, 2017 16:37

  Daniel,

   

  Thanks for following up again. I just did a bit of exploring. We have two instances of GE running--Internal and External. Internal is our original installation and all of the viewers inherit from a 'main' viewer configuration but separate HTML5 Viewer configs. External is more recent and while built in the same way as our internal viewers, the 'main' viewer config was built from scratch and not copied from internal.

   

  Interestingly, our [not quite "live" to the public] External viewer address location works as expected in IE 11. They are both hitting the same geocoding service on our map server, so something is wonky with my internal configuration.

   

  I'll set aside some time to build a quick site from scratch on the internal instance and see what my results are. If they are the same as present then I will open a support case.

   

  Thanks, again!

   

  Brian

   

   

  0
• 

  Brian Oevermann

  July 14, 2017 17:30

  It appears I wrote too soon. My External viewer is again exhibiting the behavior. A colleague is able to get results on one of the internal viewers but not on the external viewer. Wacky.

   

  Definitely need to do some research and testing to try to determine the extent of this before I can open an effective support ticket.

   

  Brian

  0

Please sign in to leave a comment.