Results 1 to 9 of 9

Thread: Warning messages on Models

    Success! Looks like we've fixed this one. According to our records the fix was applied for DSGNR-1307 in a recent build.
  1. #1
    Ext JS Premium Member Artistan's Avatar
    Join Date
    Apr 2007
    Location
    MN
    Posts
    144
    Vote Rating
    0
      0  

    Default Warning messages on Models

    http://visits.benint.net/visits/touch-model/index.html

    fields is deprecated as a property directly on the Model prototype. Please put it inside the config object.

    proxy is deprecated as a property directly on the Model prototype. Please put it inside the config object.

    Url above is an example of it.
    Currently I have stores without proxy using models.
    These models are fairly simple with RestProxy and JsonReader and a few fields defines.

    After the warning messages (notices?)
    Then I get a fatal Uncaught TypeError!





  2. #2
    Sencha User
    Join Date
    Oct 2010
    Location
    Knoxville, TN
    Posts
    133
    Vote Rating
    1
      0  

    Default

    Same thing here. Anyone have any clue whats going on with this?

  3. #3
    Sencha User aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,487
    Vote Rating
    146
      0  

    Default

    The warnings are just grabbing those properties off of the prototype and putting them in the configuration. That should not be causing the getId failure.

    Could you create a test case that illustrates the problem so that we can resolve it?

    As a side note, the config issue will be resolved in a build in the near future.
    Aaron Conran
    @aconran

  4. #4
    Ext JS Premium Member Artistan's Avatar
    Join Date
    Apr 2007
    Location
    MN
    Posts
    144
    Vote Rating
    0
      0  

    Default

    http://visits.benint.net/visits/touc.../designer.html

    I will work on a more simple example if/when I can.

  5. #5
    Ext JS Premium Member Artistan's Avatar
    Join Date
    Apr 2007
    Location
    MN
    Posts
    144
    Vote Rating
    0
      0  

    Default

    Quote Originally Posted by aconran View Post
    The warnings are just grabbing those properties off of the prototype and putting them in the configuration. That should not be causing the getId failure.

    Could you create a test case that illustrates the problem so that we can resolve it?

    As a side note, the config issue will be resolved in a build in the near future.
    Here is a MUCH simpler example...

    http://visits.benint.net/visits/stor.../designer.html

  6. #6
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Vote Rating
    65
      0  

    Default

    This is the same issue we are seeing that crashes designer when you click load data. Looking into this on both levels. It is a framework exception just not sure why yet
    Phil Strong
    @philstrong

  7. #7
    Sencha Premium Member svenna's Avatar
    Join Date
    Jun 2007
    Location
    Oslo,Norway
    Posts
    652
    Vote Rating
    40
      0  

    Default

    The trace an exception looks very much alike a bug in the ST2 PR4 framework, fixed in Beta 1.

    http://www.sencha.com/forum/showthre...d-of-undefined

    http://www.sencha.com/forum/showthre...)-PR4&p=721809
    Sven Tore Iversen

  8. #8
    Sencha User
    Join Date
    Jun 2011
    Posts
    350
    Vote Rating
    1
      0  

    Default

    Thanks Sven for reporting this.

    Artistan, this will be fixed soon when we upgrade Touch to Beta1.

  9. #9
    Sencha User aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,487
    Vote Rating
    146
      0  

    Default

    This should be fixed as of build 276.
    Aaron Conran
    @aconran

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •