I'm getting a similar error in Firefox 3: failed loading undefined./parser.js with error: TypeError: this._getText is not a function

However, if I do a shift-reload, it works. Plus it works fine locally, it's only on the remote server where it fails. This suggests a timing problem, which would explain why only some people would see it.

Gary

[edited to clarify that it's not the identical error]

It is hard to tell -- does not sound like a known issue. If you use Firebug's Net tab, does that indicate any network loading errors? Do the paths for the loaded files look right?

Actually, the .Net tab doesn't show any of the .js files even when it 's working, but the Console does. On the other hand, when it doesn't work, there are no GETs logged in the console.

The file path does look suspicious: undefined./parser.js . Both the 'undefined' and the period between the 'undefined' and / seem questionable.

I've tried debugging using console.log statements in dojo.js.uncompressed.js, and it appears that it's trying to execute the dojo.require before dojo.js has finished executing, and in particular, before the function that adds _getText to the dojo object has finished.

Specifically, I added log messages here, starting at line 1254 (version 1.1.1):

if(typeof window != 'undefined'){
	dojo.isBrowser = true;
	dojo._name = "browser";
	console.log("window is defined");

	// attempt to figure out the path to dojo if it isn't set in the config
	(function(){
		var d = dojo;
		// this is a scope protection closure. We set browser versions and grab
		// the URL we were loaded from here.
		console.log("in defined window anonymous function");
		if(document && document.getElementsByTagName){
		.....
		}
		d.baseUrl = d.config.baseUrl;
		console.log("computed base url = " + d.baseUrl);
		// fill in the rendering support information in dojo.render.*

and the console log shows:

window is defined
in defined window anonymous function
failed loading undefined./parser.js with error: TypeError: this._getText is not a function				2 (line 34)
computed base url = /js/dojo/dojo/
...

I don't know whether the order of messages is reliable, but they're certainly consistent with the conjecture that the dojo.require is being executed too soon.

"application/xhtml+xml" is known to, well, suck. What mimetype are you serving the page with?

--
Project Lead, The Dojo Toolkit 
President, The Dojo Foundation

My main page is text/html , while the javascript pages are application/x-javascript, I think.

I am also getting the parser/getText() error described by GaryFX periodically with firefox.

I am using a local deployment of dojo 1.1.1 and have received it on both Firefox 2 and 3.

Like the other comments, refreshing the page will resolve the error...

I know the only way to avoid such error.
Load dojo libs throw o.aolcdn.com server, not locally.

<_script type="text/javascript" src="http://o.aolcdn.com/dojo/1.1.1/dojo/dojo.xd.js"
djConfig="parseOnLoad: true">
and so on...

I share this problem with you guys - is this worth a word to the developers ?
For me it looks like a common problem, so it should be solved for all.

I believe I have just encountered this issue with 1.1.1...

I have been using dojo for some time and the error just recently started occurring. Has anyone had this problem with an earlier version of dojo?

It is very annoying, as sometimes I will have to refresh the page two or three times before the error goes away. I think it has caused problems during users' testing too (hard to tell...since it's intermittent and they're not net-savvy enough to check a firebug console...)

It would be good to get a complete test case: actually, a complete HTML page that runs with a built version of dojo. Feel free to attach the HTML test case to a ticket you can open at http://bugs.dojotoolkit.org.

It seems like there may be a problem involved, but it is hard to pinpoint without an HTML test case I can run. Note that the HTML test case should be standalone-it should not depend on any type of server to generate the HTML. I should be able to run the static HTML and see the problem.

Are you all using tiny_mce.js? I wonder if moving that after Dojo makes a difference, or if it is interfering somehow with Dojo's initialization code.