Results 1 to 9 of 9

Thread: Extjs grid makes an unwanted load call when using column filters

    You found a bug! We've classified it as EXTJS-14620 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #1
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default Extjs grid makes an unwanted load call when using column filters

    As I asked here http://stackoverflow.com/questions/2...column-filters when enabling filters for grid columns ExtJs makes load call at initiation phase (exactly like what autolod:true does) . You can check this fiddle : https://fiddle.sencha.com/#fiddle/8m5 for an example too.
    How can I stop or change this behavior? is it bug or not?

  2. #2
    Sencha User slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,165

    Default

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

  3. #3
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default

    Ok, I found a work around for it :

    Code:
    Ext.override(Ext.data.Store, {
        initConfig: function (config) {
            this.callParent([config]);
            if (this.remoteFilter) this.autoFilter = false;
        },
        listeners: {
            load: function () {
                if (!this.autoFilter && this.remoteFilter)
                    this.autoFilter = true;
            }
        }
    });

  4. #4
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default

    why did this bug is not resolved in Ext 5.1 ?

  5. #5
    Sencha Premium User SebTardif's Avatar
    Join Date
    Feb 2011
    Location
    Cambridge, MA
    Posts
    1,295

    Default

    Quote Originally Posted by Mahmoud690 View Post
    why did this bug is not resolved in Ext 5.1 ?
    5.1 was cut by throwing a dice. My team was finding 4 bugs per day everyday, when Sencha cut the release...

    They are hundred of known bugs. Spending entire day to find out a bug is known for months is 'normal'.

  6. #6
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default

    Quote Originally Posted by SebTardif View Post
    My team was finding 4 bugs per day everyday, when Sencha cut the release...

    They are hundred of known bugs. Spending entire day to find out a bug is known for months is 'normal'.
    Shame on ExtJs. I think they should revise their test approach. They have 125000 test cases which run automatically but I think it is just a number. Mabe only 10% of these test cases are useful and functional. Just releasing 5.1 takes about 6 months!

    I think we should wait for 5.2...oh !....how long does it take? 1 month? 2 months? 6 months or a year?! just god knows.

  7. #7
    Ext JS Premium Member
    Join Date
    Apr 2008
    Posts
    394

    Default

    Quote Originally Posted by Mahmoud690 View Post
    Shame on ExtJs. I think they should revise their test approach. They have 125000 test cases which run automatically but I think it is just a number. Mabe only 10% of these test cases are useful and functional. Just releasing 5.1 takes about 6 months!

    I think we should wait for 5.2...oh !....how long does it take? 1 month? 2 months? 6 months or a year?! just god knows.
    If I were really skeptical, I'd expect the first build that has few enough bugs to be really useful will be a support subscriber only release and will occur immediately after then next annual payment is required. How much will the cost go up next year anyway?

  8. #8
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default

    ha ha! This bug is not fixed in 5.1.1 (after about 9 months!) . Also the current work around does not work anymore!!

  9. #9
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default

    And now workaround for Ext 5.1.1 :


    Code:
    Ext.override(Ext.data.Store, { 
       initConfig: function (config) { 
           this.callParent([config]); 
           if (this.getRemoteFilter()) {
                this.setRemoteFilter(false);
                this._workAroundAutoFilter = true; 
            }
        },    
        listeners: { 
           load: function () { 
               if (this._workAroundAutoFilter) {
                    this.setRemoteFilter(true);
                    this._workAroundAutoFilter = false; 
                }          
          }     
       }
    });

Tags for this Thread

Posting Permissions

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