Success! Looks like we've fixed this one. According to our records the fix was applied for a bug in our system in a recent build.
  1. #1
    Sencha User
    Join Date
    Jun 2011
    Posts
    20
    Vote Rating
    0
    boboka is on a distinguished road

      0  

    Default 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


    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.

  2. #2
    Sencha User
    Join Date
    Jun 2011
    Posts
    20
    Vote Rating
    0
    boboka is on a distinguished road

      0  

    Default


    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.

  3. #3
    Sencha - Architect Dev Team aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,445
    Vote Rating
    129
    aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold

      0  

    Default


    boboka -

    Agreed, could you please give us more details about what the issue is so that we can improve the validation?
    Aaron Conran
    @aconran
    Sencha Architect Development Team

  4. #4
    Sencha User
    Join Date
    Jun 2011
    Posts
    20
    Vote Rating
    0
    boboka is on a distinguished road

      0  

    Default


    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

  5. #5
    Sencha - Architect Dev Team Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Vote Rating
    65
    Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice

      0  

    Default


    Less bug and more feature. Thanks for the links on id restrictions
    Phil Strong
    @philstrong
    #SenchaArchitect
    Sencha Architect Development Team

  6. #6
    Touch Premium Member
    Join Date
    Nov 2011
    Location
    Bay Area
    Posts
    68
    Vote Rating
    0
    allan.ditzel is on a distinguished road

      0  

    Default


    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.

  7. #7
    Touch Premium Member
    Join Date
    Nov 2011
    Location
    Bay Area
    Posts
    68
    Vote Rating
    0
    allan.ditzel is on a distinguished road

      0  

    Default


    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

  8. #8
    Touch Premium Member
    Join Date
    Nov 2011
    Location
    Bay Area
    Posts
    68
    Vote Rating
    0
    allan.ditzel is on a distinguished road

      0  

    Default


    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?

  9. #9
    Sencha - Architect Dev Team Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Vote Rating
    65
    Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice

      0  

    Default


    Yes this is a known issue that's been reported and we're working on it
    Phil Strong
    @philstrong
    #SenchaArchitect
    Sencha Architect Development Team

  10. #10
    Sencha - Architect Dev Team Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Vote Rating
    65
    Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice Phil.Strong is just really nice

      0  

    Default


    A bug with MVC and not Designer specifically.
    Phil Strong
    @philstrong
    #SenchaArchitect
    Sencha Architect Development Team