Results 1 to 7 of 7

Thread: Bug in Ext.data.BufferedStore when using a grouped stateful table

    You found a bug! We've classified it as EXTJS-16754 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #1
    Sencha Premium User
    Join Date
    Dec 2007
    Location
    Stuttgart, DE
    Posts
    51

    Default Bug in Ext.data.BufferedStore when using a grouped stateful table

    Ext version tested:
    • Ext 5.1.1.264


    Browser versions tested against:
    • Chrome 40, but: doesn't matter


    DOCTYPE tested against:
    • <!DOCTYPE HTML>


    Description:
    When using a grouped stateful grid on a Ext.data.BufferedStore the method applyState() is called as expected. The method itself calls setGrouper() with is a setter on the grouper config property. This calls applyGrouper() in Ext.data.AbstractStore which in turn tries to call this.getData().getGrouper(). This does not work on buffered stores however.

    Steps to reproduce the problem:
    Just run the following fiddle twice. On the first run the grid renders as expected (no state in the cookie), but it fails on the second run when it tries to apply the grouper state as described above.



    The result that was expected:
    • grid is displayed


    The result that occurs instead:
    • grid is not displayed
    • Code:
      Uncaught TypeError: undefined is not a function ext-all-debug.js:47159 
      Ext.define.applyGrouper ext-all-debug.js:6260 
      setter ext-all-debug.js:46996 
      Ext.define.applyState ext-all-debug.js:91511 
      Ext.define.applyState ext-all-debug.js:37757 
      Ext.define.initState ext-all-debug.js:37645 
      Ext.define.constructor ext-all-debug.js:38796 
      Ext.define.constructor ext-all-debug.js:7379 
      Ext.Base.Base.addMembers.callParent ext-all-debug.js:91079 
      Ext.define.constructor ext-all-debug.js:7658 
      constructor VM1585:3 
      (anonymous function) ext-all-debug.js:8899 
      Ext.ClassManager.Ext.apply.create (index):77 
      (anonymous function) ext-all-debug.js:10515 
      Ext.env.Ready.invoke ext-all-debug.js:10555 
      Ext.env.Ready.doInvokeAll ext-all-debug.js:10524 
      Ext.env.Ready.invokeAll ext-all-debug.js:10492 
      Ext.env.Ready.handleReady ext-all-debug.js:10502 
      (anonymous function) ext-all-debug.js:4415 
      Ext.Function.ExtFunction.bind ext-all-debug.js:4494 
      (anonymous function)

  2. #2
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    Thanks for the report! I have opened a bug in our bug tracker.

  3. #3
    Sencha Premium User
    Join Date
    Dec 2007
    Location
    Stuttgart, DE
    Posts
    51

    Default

    Anything new on this one?
    Is there an ETA? 5.1.1?

    Cheers
    Stefan

  4. #4
    Sencha Premium User
    Join Date
    Dec 2007
    Location
    Stuttgart, DE
    Posts
    51

    Default

    Hey guys,

    anything new on that one? There's not much going on in terms of bug fixing for 5.1.2. Any chance this issue gets fixed before shifting focus fully on Ext 6?

    Sorry for being dogged, but we're on 5.1 and we need these fixes...
    Cheers
    Stefan

  5. #5
    Sencha User
    Join Date
    Sep 2016
    Posts
    23

    Default

    Looks like this bug is still in 6.2.1.29. Any news on that? Workarounds?

  6. #6
    Sencha User
    Join Date
    Sep 2016
    Posts
    23

    Default

    Bump

  7. #7
    Sencha Premium Member
    Join Date
    May 2011
    Posts
    33

    Default

    As a workaround i have overriden the getState function on my store:

    Code:
    getState: function () {
        Ext.log(this.self.getName() + ": getState");
    var result = this.callParent();
    delete result.grouper;
    return result;
    }

Posting Permissions

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