Opened 3 years ago

Closed 3 years ago

#18869 closed defect (invalid)

dojo 1.10.4 error: Must pre-load all supporting widgets before instantiation

Reported by: jonavuka Owned by:
Priority: undecided Milestone: tbd
Component: General Version: 1.10.4
Keywords: Cc:
Blocked By: Blocking:

Description

Hi,

I'm doing a project that involves upgrading our dojo toolkit from 1.9.1 to 1.10.4 and I am experiencing an issue with the template. I am using the _Template.js module from the dijit package and I get the following errors:

dojo/parser::parse() error TypeError?: Cannot read property 'toString' of undefined(…) init.js:623 dojo/parser::parse() error Error: custom.MapContainer?: parser returned unfilled promise (probably waiting for module auto-load), unsupported by _WidgetsInTemplateMixin. Must pre-load all supporting widgets before instantiation

In our MapContainer?.js module we use an html as a template as such:

templatePath : dojo.moduleUrl("custom.templates", "MapContainer?.html")

The MapContainer?.js module is the first thing that's called in our application, it goes through the constructor and then goes into a file called init.js. This project uses arcgis javascript api which in turn uses the dojo toolkit. So this init.js is part of the arcgis application and it ends up spitting the error I mentioned above.

The behaviour of the application is different from browser to browser. For instance, in chrome and Firefox the error is always displayed. However, for IE if the cache is cleared the error happens but when the page is reloaded it doesn't happen and the application behaves as expected.

Any idea what this could be? Where can I look to find the underlying issue?

Change History (2)

comment:1 Changed 3 years ago by dylan

Status: newpending

We reserve the issue tracking system for verified bugs, but this sounds more like a support question, which we encourage use of the mailing list, IRC, or commercial support options listed at https://dojotoolkit.org/community/

Without a complete example, it's difficult to tell, but it's pretty clearly a timing issue.

It looks like you are using pre-AMD syntax, which has the potential to cause further issues as it has been deprecated in favor of AMD and more modern APIs.

I'm going to return this to @jonavuka, but I encourage providing a more complete example through one of the other support forums first.

comment:2 Changed 3 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.