1. #11
    Sencha User aflx's Avatar
    Join Date
    Jun 2011
    Location
    Berlin, Germany
    Posts
    64
    Vote Rating
    0
    aflx is on a distinguished road

      0  

    Default


    @samlinux: yesterday I had the same issue after updateing sencha and I think you are right. Nothing changed in PR3

  2. #12
    Sencha User
    Join Date
    Dec 2011
    Posts
    1
    Vote Rating
    0
    jvaartjes is on a distinguished road

      0  

    Default


    Yes, i had the same issue in PR3. The fix works great though!
    Thanks!

  3. #13
    Sencha User mblomdahl's Avatar
    Join Date
    Nov 2011
    Location
    Stockholm, Sweden
    Posts
    4
    Vote Rating
    0
    mblomdahl is on a distinguished road

      0  

    Default


    Quote Originally Posted by aflx View Post
    I had the same error. This is because the proxy-property in the Ext.data.Batch is never set. As a workaround you can add this to the constructor:

    Code:
    if (config.hasOwnProperty) {
      this.proxy = config.proxy;
    }
    People like you are what makes the Internet a great place to live.

    Regards,
    //mblomdahl

  4. #14
    Sencha User
    Join Date
    Nov 2010
    Posts
    118
    Vote Rating
    9
    Bunchofstring will become famous soon enough

      0  

    Default


    I enjoy working with ST2, but I am just concerned about using data package workarounds like (1) the patch to enable non-integer idProperty for models, or (2) using store.each(function(record){store.add(record).save()},this); instead of store.add(records);store.sync();

    Can someone help me understand why a PR release would have problems with store.sync()? IMO, the localstorage proxy is a key feature for Sencha Touch, so I'm surprised that this patch is still required. Maybe this isn't as critical to other devs as I think, but it'd be great to have some insightful comment on circumstances where store.sync() works OOTB vs. where it doesn't.