Designer 1.2.2-48 export with the new ExtJS 4.0.7 does not load in the browser

**boboka** · 21 Oct 2011 1:05 PM

I updated to ExtJS 4.0.7 today, re-exported my project from Designer without any change (other than changing the path in the project settings from "/ext-4.0.2a/" to "/ext-4.0.7-gpl/") and when I try to load the page I receive

ext-all-debug.js:13795
Uncaught TypeError: Cannot call method 'on' of null

No customization or adding of code whatsoever. Just screen interface design and export.

**boboka** · 24 Oct 2011 9:07 PM

solved it. There were still problems with some characters in the "id" field for the buttons. (Extjs 4.1-pr1 also gave errors) . Designer should really check for some of the fields for valid characters.

**aconran** · 27 Oct 2011 9:42 AM

boboka -

Agreed, could you please give us more details about what the issue is so that we can improve the validation?

**boboka** · 27 Oct 2011 11:29 AM

I think the best if the check will use the standard:

html5:
http://www.w3.org/TR/html5/elements....e-id-attribute

in html4 it was even more strict:
http://www.w3.org/TR/html401/types.html#type-name

More info on this, with some examples:
http://mathiasbynens.be/notes/html5-id-class

**Phil.Strong** · 31 Oct 2011 5:29 AM

Less bug and more feature. Thanks for the links on id restrictions

**allan.ditzel** · 2 Nov 2011 10:44 AM

What characters were you using in the id field of the buttons? I'm seeing similar behavior (i.e. getting an error when exporting the project with designer 1.2.2-48 but I can preview in designer), but I'm not using any special characters in my button id's.

**allan.ditzel** · 2 Nov 2011 11:26 AM

In my case I'm finding that the method addManagedListener in ext-all-debug.js is failing on binding the load event for a second ajax store I have added to the project. It doesn't matter whether the autoLoad property is true or false, this error still occurs:

ext-all-debug.js: 13324 Uncaught TypeError: cannot call method 'on' of undefined

**allan.ditzel** · 2 Nov 2011 6:46 PM

FYI

I found a work-around for the particular issue I was facing. Basically, in the store I was setting the userClassName and storeId properties, but to different values, and this is what was causing the issue. Once I set both of these properties to the same value the exported project loaded in the browser.

So this sounds more like an Ext 4 issue than a Designer issue?

**Phil.Strong** · 3 Nov 2011 8:29 AM

Yes this is a known issue that's been reported and we're working on it

**Phil.Strong** · 3 Nov 2011 8:42 AM

A bug with MVC and not Designer specifically.

Designer 1.2.2-48 export with the new ExtJS 4.0.7 does not load in the browser

Thread Tools

Search Thread

Display

Designer 1.2.2-48 export with the new ExtJS 4.0.7 does not load in the browser

Designer 1.2.2-48 export with the new ExtJS 4.0.7 does not load in the browser