nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sample scripts no longer work since upgrade to v3.0 of the API

StephenLead

It looks like a batch process has been run over all of the sample scripts, eg the Hover sample, to upgrade them to use version 3.0 of the JS API.

<link rel="stylesheet" type="text/css" href="http://serverapi.arcgisonline.com/jsapi/arcgis/3.0/js/dojo/dijit/themes/claro/claro.css"> <script type="text/javascript" src="http://serverapi.arcgisonline.com/jsapi/arcgis/?v=3.0"></script>

This means that the samples no longer work when copy/pasting directly from the Esri site into a local file.

[ATTACH=CONFIG]15775[/ATTACH]

If I revert those lines to use 2.8 the sample works fine.

Thanks,
Steve

Screen Shot 2012-07-05 at 1.51.19 PM.png

Icon_9.png

Find more posts tagged with

Accepted answers

derekswingley1

I'm having a similar problem. Also I am running this from my local file system [ATTACH=CONFIG]15793[/ATTACH]

Please use a local web server. It's not realistic to run web apps from your local file system. There are plenty of free options and most OSes come with a web server built-in.

All comments

FengZhang2

Seems that you may have a "Access-Control-Allow-Origin" issue for your local html file. You can try to publish the html to the web server and access it using

http://hostmame/.../query_hover.html

Or, the following help links may be helpful to you.

Making cross domain JavaScript requests using XMLHttpRequest or XDomainRequest
http://www.leggetter.co.uk/2010/03/12/making-cross-domain-javascript-requests-using-xmlhttprequest-or-xdomainrequest.html

SCRIPT5: Access is denied in IE9 on xmlhttprequest
http://stackoverflow.com/questions/5793831/script5-access-is-denied-in-ie9-on-xmlhttprequest

derekswingley1

Steve�?? are you running the sample from your file system or from a local web server?

NigelAlford

I'm having a similar problem. Also I am running this from my local file system [ATTACH=CONFIG]15793[/ATTACH]

JScripterror.jpg

derekswingley1

I'm having a similar problem. Also I am running this from my local file system [ATTACH=CONFIG]15793[/ATTACH]

Please use a local web server. It's not realistic to run web apps from your local file system. There are plenty of free options and most OSes come with a web server built-in.

JeffPace1

Hey derek,
I know this was a change that had to be made, but up till 2.8 everything ran fine as a local file. It was MUCH more convenient. This seems like a major step backwards.

NigelAlford

I launched this from Visual Studio 2010 Ultimate and everything finally worked. Thats an interesting update with 3.0

StephenLead

Please use a local web server. It's not realistic to run web apps from your local file system. There are plenty of free options and most OSes come with a web server built-in.

Hi Derek,

Thanks for the clarification. However, I agree with Jeff that this represents a new hurdle for developers (especially those just starting out with the JS API).

While it's not realistic to run web apps from a local file system, it IS common to fire up a quick sample to check how one specific thing works, which is surely the point of the samples? This is how we test out new functionality before compiling it into a robust web app for deployment (not just in the ArcGIS Server JS API but in other web mapping APIs, or indeed other JavaScript/HTML libraries).

I haven't looked into v3.0 yet so I don't fully understand the change, and why it was necessary. As a developer, all I can see is that the copy/paste/test approach used to work, and now doesn't. Perhaps there could be a blog post/tutorial explaining the changes, and giving some simple instructions for the new requirements of a web server - this could be linked on each sample page.

Cheers,
Steve

MarkHoover

Hi Derek,

Thanks for the clarification. However, I agree with Jeff that this represents a new hurdle for developers (especially those just starting out with the JS API).

While it's not realistic to run web apps from a local file system, it IS common to fire up a quick sample to check how one specific thing works, which is surely the point of the samples? This is how we test out new functionality before compiling it into a robust web app for deployment (not just in the ArcGIS Server JS API but in other web mapping APIs, or indeed other JavaScript/HTML libraries).

I haven't looked into v3.0 yet so I don't fully understand the change, and why it was necessary. As a developer, all I can see is that the copy/paste/test approach used to work, and now doesn't. Perhaps there could be a blog post/tutorial explaining the changes, and giving some simple instructions for the new requirements of a web server - this could be linked on each sample page.

Cheers,
Steve

Spot on; everything addressed here is a valid concern and well said.

ReneRubalcava

I believe the reason for this a Dojo 1.7 issue and not an ESRI API issue.
If run locally, Dojo will try to load the files locally, which is why you get these errors.
Let's look at the dojo/text tool. It will load a file as plain text to use in your application, mostly used for templating. This a XHR request, which cannot be done locally and will only work in a server environment.

It can be a little annoying if you are not used to keeping a server up locally.

If you want a ridiculously easy local server to use, try xampp.
http://www.apachefriends.org/en/xampp.html

It's a simple, one-click install of apache/mysql/tomcat and more. You can just use it to run apache which will work for running the samples. There's even a version to run it off a usb drive. I've been using it for quite a while at work so I don't need to work off a test server.

StephenLead

Hi all,

I guess the main problem is that this new requirement (to use a web server) isn't documented anywhere. Eg, the Samples homepage still links to a video showing how to download a sample and run it from your local disk. None of the individual samples have been updated to list the requirement for a web server.

As of last week, we were all used to working a certain way, and now we need to change. That's not a problem, but there needs to be a clearer set of instructions on what's required. This affects both experienced developers (who are used to working the old way and new developers (who need to know how to get started).

This could be remedied with a new "how to use these samples" video tutorial (and complementary text version) on the Samples homepage, showing how to set up a local web server. This should also be linked from each sample page.

At the moment, developers would need to read this thread in order to figure out (a) what's wrong and (b) how to fix it.

Cheers,
Steve

derekswingley1

Hi all,

I guess the main problem is that this new requirement (to use a web server) isn't documented anywhere. Eg, the Samples homepage still links to a video showing how to download a sample and run it from your local disk. None of the individual samples have been updated to list the requirement for a web server.

The video shows using a local instance of IIS to run the sample. Notice that the html file is placed in the wwwroot directory (default location to serve files using IIS) and when it's loaded in the browser, the sample is accessed using http://, not file://.

J_C_Geers

edit:
my bad

StephenLead

The video shows using a local instance of IIS to run the sample. Notice that the html file is placed in the wwwroot directory (default location to serve files using IIS) and when it's loaded in the browser, the sample is accessed using http://, not file://.

OK maybe the video wasn't a good example as I got frustrated by the slow clicking and stopped watching it before the end (or perhaps this makes it a good example after all, since most developers have short attention spans...)

I won't labour the point, but my feedback is that it's possible many users will be confused by the new requirements, and it would help if there was some mention of this, somewhere.

Cheers,
Steve

KeithSandell

If I'm running an app from the IIS root folder and I am still getting the following console error:

XMLHttpRequest cannot load http://server.arcgisonline.com/ArcGIS/rest/info?f=json. Origin http://<servername> is not allowed by Access-Control-Allow-Origin.

Should I be concerned? What could be causing this?

This is the World Street Map example straight copy and paste.

derekswingley1

If I'm running an app from the IIS root folder and I am still getting the following console error:

XMLHttpRequest cannot load http://server.arcgisonline.com/ArcGIS/rest/info?f=json. Origin http://<servername> is not allowed by Access-Control-Allow-Origin.

Should I be concerned? What could be causing this?

You can safely ignore that error. More info: http://forums.arcgis.com/threads/60386-Access-Control-Allow-Origin-and-3.0?p=208466&viewfull=1#post208466

StephenLead

I promised not to labour the point, but anyway..... I just noticed that another user has run into the same issue:

Please help me. The live samples are working when i view it in the browser, but when i copy the code into notepad and run it as a local copy in the browser. The code is not working, nothing is being displayed.

I tried to link to a reference showing the need to use a web server - and I still can't find one, aside from this thread.

The Getting Started section of the help shows how to create your first application, but doesn't mention setting up a web server. Perhaps you could you add something here with simple instructions on how to set up a web server in Windows, OS and Linux?

Cheers,
Steve

KristianLucido

Hi,
I have the same problem.
I dont have the ARCGIS API in local but in a webserver and do the correct configuration in "init.js" and "dojo.js".
What's the problem? I don't understand!

[ATTACH=CONFIG]17873[/ATTACH]

This is the image of the error in Firebug. "192.168.13.56" is my address IP in my network. The url of the file is not good!

Please help me!

Thanks in advance!

esri.JPG

derekswingley1

It would be better if you started a new thread instead of piggy-backing on this one since it's already been answered. Can you start a new thread, and in that thread, post the code for the page that is generating that error.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.