topic Re: ParkFinder App - Browser Issue in ArcGIS JavaScript Maps SDK Questions

ParkFinder App - Browser Issue

BrianLord1 — Thu, 29 Nov 2012 18:47:14 GMT

I am new to Javascript and have been working on configuring the ParkFinder Template from the Local Government App Gallery (http://www.arcgis.com/home/item.html?id=734512384d3b4b849aba2db0e33a80f2). So far I just swapped out all the ESRi layer/field names for mine. I got the app to work on Chrome and FIrefox, but run into an issue when testing it in IE7.

The app loads and everything is fine until I try to search for parks. The map says "Loading" and never actually loads anything. As you can see in the attached image, the search Results portion is populated. However the Park info and Directions boxes do not even show up. I am guessing it is something with the routing functionality, but am not sure where to start.

Any help would be greatly appreciated.

Thanks,
Mark

Also, I just noticed that the infowindow does not work when I click on the park either.

Re: ParkFinder App - Browser Issue

JeffPace — Thu, 29 Nov 2012 18:52:41 GMT

I am new to Javascript and have been working on configuring the ParkFinder Template from the Local Government App Gallery (http://www.arcgis.com/home/item.html?id=734512384d3b4b849aba2db0e33a80f2). So far I just swapped out all the ESRi layer/field names for mine. I got the app to work on Chrome and FIrefox, but run into an issue when testing it in IE7.

The app loads and everything is fine until I try to search for parks. The map says "Loading" and never actually loads anything. As you can see in the attached image, the search Results portion is populated. However the Park info and Directions boxes do not even show up. I am guessing it is something with the routing functionality, but am not sure where to start.

Any help would be greatly appreciated.

Thanks,
Mark

Also, I just noticed that the infowindow does not work when I click on the park either.

IE7 is not a CORS compliant browser, which means you have cross domain issues, which means you need a proxy setup.

Re: ParkFinder App - Browser Issue

BrianLord1 — Thu, 29 Nov 2012 19:00:06 GMT

Thanks for the reply.

Is that just an issue with Javascript, because I have a Silverlight app that I created and it runs fine on IE7?

Re: ParkFinder App - Browser Issue

JeffPace — Thu, 29 Nov 2012 19:02:31 GMT

Thanks for the reply.

Is that just an issue with Javascript, because I have a Silverlight app that I created and it runs fine on IE7?

not sure. still better than needed an abandoned plugin though 😉

Re: ParkFinder App - Browser Issue

BrianLord1 — Thu, 29 Nov 2012 19:07:45 GMT

Yeah, I agree. It is a completely different app and I will eventually be re-making it in Javascript.

If it was a cross-domain issue, wouldnt I have issues loading any of the data or running the query that populates the park list? The map services load fine, its just when i try to search for parks. Unless it is caused by the app trying to use the routing service from arcgis online.

Re: ParkFinder App - Browser Issue

JeffPace — Thu, 29 Nov 2012 19:09:24 GMT

GET requests (less than 2000 characters) don't need a proxy. POST does (>2000 characters). my guess is the size of the request is switching the request type to POST.

Re: ParkFinder App - Browser Issue

TracySchloss — Thu, 29 Nov 2012 19:37:44 GMT

I worked through the Park finder example myself. It didn't work for me until I had my proxy set up correctly.

Re: ParkFinder App - Browser Issue

BrianLord1 — Sat, 11 Dec 2021 21:23:21 GMT

So I checked the folder I download for the app and a proxy is set up and saved in the same location as my application.

I also have the following code in my html document.

            esri.config.defaults.io.proxyUrl = "proxy.ashx";        //Setting to use proxy file
            esriConfig.defaults.io.alwaysUseProxy = false;
            esriConfig.defaults.io.timeout = 180000;    //ersi request timeout value

If I understood the documentation I read, this set up will automatically use the proxy page if the request exceeds 2000 characters.

Also, the documentation for this app says that it is optimized for IE 7/8/9, Chrome, FireFox so it must be somethign I changed. The only things I changed were field names and map service names/url's.

Re: ParkFinder App - Browser Issue

JeffPace — Sat, 11 Dec 2021 21:23:24 GMT

So I checked the folder I download for the app and a proxy is set up and saved in the same location as my application.

I also have the following code in my html document.
            esri.config.defaults.io.proxyUrl = "proxy.ashx";        //Setting to use proxy file
            esriConfig.defaults.io.alwaysUseProxy = false;
            esriConfig.defaults.io.timeout = 180000;    //ersi request timeout value
If I understood the documentation I read, this set up will automatically use the proxy page if the request exceeds 2000 characters.

Also, the documentation for this app says that it is optimized for IE 7/8/9, Chrome, FireFox so it must be somethign I changed. The only things I changed were field names and map service names/url's.

That looks fine, did you add your servers to the .config file?

Re: ParkFinder App - Browser Issue

BrianLord1 — Sat, 11 Dec 2021 21:23:27 GMT

Yep, code is shown below.

<ProxyConfig mustMatch="true">
  <serverUrls>
    <serverUrl url="http://xxxxxxx/ArcGIS/rest/services/"
               matchAll="true"></serverUrl>   

  </serverUrls>

</ProxyConfig>

Do I have to change anything in the proxy.ashx file?

Re: ParkFinder App - Browser Issue

BrianLord1 — Fri, 30 Nov 2012 13:51:50 GMT

So after using fiddler to watch the request/responses from my app, I am pretty sure the issue is with the route.solve task that gets sent to ArcGIS online.

When I use Firefox and Chrome I can see that this is sent as a GET request and returns in less than 1 second. However, when using IE7 this never even shows up in Fiddler and the map gets stuck. The previous request (a spatial query to find the parks within a 1 mile buffer) is sent via POST to my server but I can see the response so I believe it returned fine.

Any ideas on what could cause an issue with the route.solve task in just IE7?

Re: ParkFinder App - Browser Issue

JeffPace — Fri, 30 Nov 2012 17:04:38 GMT

since you are running on your own server, you need to add ESRI's servers to the proxy.

Re: ParkFinder App - Browser Issue

BrianLord1 — Sat, 11 Dec 2021 21:23:29 GMT

I did double check to make sure I have ESRIs server listed on the proxy, and I do.

I was running my webmap using debugging in Visual Studio and I kept getting an error on the following line.

if (infoPopupFieldsCollection[key].DisplayText) {
            td1.innerHTML = infoPopupFieldsCollection[key].DisplayText + ':';
        }

I have attached a screenshot of the error I get.

Any ideas as to what may cause this and wether or not this might be the cause of the IE issues?