Results 1 to 7 of 7

Thread: [3.3 Beta][CLOSED-1183] this.config[i].destroy not a function

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    May 2008
    Posts
    45
    Vote Rating
    0
      0  

    Exclamation [3.3 Beta][CLOSED-1183] this.config[i].destroy not a function

    I get in Ext 3.3 beta the Error (FF 3.6.8) "this.config[i].destroy is not a function" in "ext-all-debug.js"# on row 48699.

    In Ext 3.1.1 i had the same problem before (Existing Topic: http://www.extjs.com/forum/showthread.php?t=91686)
    The Bugfix from mystix fixed the problem in 3.1.1. In Ext 3.2 it worked without the Bugfix.

    Now in 3.3 beta i get the same Error again an the Bugfix from mystix works for me. but that isn't a great solution so i hope you can fix this.

    thanks

  2. #2
    Sencha User Jamie Avins's Avatar
    Join Date
    Mar 2007
    Location
    Redwood City, California
    Posts
    3,661
    Vote Rating
    19
      0  

    Default

    Thanks for the report.

  3. #3
    Sencha User edspencer's Avatar
    Join Date
    Jan 2009
    Location
    Palo Alto, California
    Posts
    1,939
    Vote Rating
    11
      0  

    Default

    @sxxl is this bug reproducible with any of our examples or some sample code you can provide? I can check for the existence of the destroy function to fix this but would prefer to understand the cause first.
    Ext JS Senior Software Architect
    Personal Blog: http://edspencer.net
    Twitter: http://twitter.com/edspencer
    Github: http://github.com/edspencer

  4. #4
    Sencha User
    Join Date
    May 2008
    Posts
    45
    Vote Rating
    0
      0  

    Default

    Thanks for your response. I couldn't reproduce the bug with any of your examples.

    But i think i have found the issue.

    My Sitation:
    The first time when i add (ajax call) the grid in a empty container i get no error, but if i try to add a grid in the cointainer with an existing grid i get the error.

    The Error only occurs if i use the RowAction Plugin from Saki.

    Code:
    new Ext.ux.grid.RowActions({
        header:jsRequestGateway.lang["general_actions"],
        autoWidth:false,
        keepSelection:true,
        actions:[{
            iconCls:'application-edit',
            tooltip:jsRequestGateway.lang["user_edit"],
            callback:function(grid, record) {
                console.log('a');
            }
        },{
            iconCls:'cross',
            tooltip:jsRequestGateway.lang["user_delete"],
            callback:function(grid, record) {
                console.log('b');
            }
        }]
    })
    Ext 3.3 provides the function xtype:'actioncolumn' now i have replaced my old RowAction with this new build in function and i dont get the "this.config[i].destroy not a function".

    Code:
    {
        xtype:'actioncolumn',
        header:jsRequestGateway.lang["general_actions"],
        width:80,
        scope:this,
        items:[{
            iconCls:'application-edit',
            tooltip:jsRequestGateway.lang["user_edit"],
            handler:function(grid, rowIndex, colIndex){
                 console.log('a');
            }
        },{
            iconCls:'cross',
            tooltip:jsRequestGateway.lang["user_delete"], 
            handler:function(grid, rowIndex, colIndex){
               console.log('b');
            }
        }]
    }
    Is this a general Extjs bug or was the RowAction Plugin the reason for the error ?

    thx for your answers

  5. #5
    Sencha User
    Join Date
    May 2008
    Posts
    45
    Vote Rating
    0
      0  

    Default

    Thanks for your response. I couldn't reproduce the bug with any of your examples.

    But i think i have found the issue.

    My Sitation:
    The first time when i add (ajax call) the grid in a empty container i get no error, but if i try to add a grid in the cointainer with an existing grid i get the error.

    The Error only occurs if i use the RowAction Plugin from Saki.

    Code:
    new Ext.ux.grid.RowActions({
        header:jsRequestGateway.lang["general_actions"],
        autoWidth:false,
        keepSelection:true,
        actions:[{
            iconCls:'application-edit',
            tooltip:jsRequestGateway.lang["user_edit"],
            callback:function(grid, record) {
                console.log('a');
            }
        },{
            iconCls:'cross',
            tooltip:jsRequestGateway.lang["user_delete"],
            callback:function(grid, record) {
                console.log('b');
            }
        }]
    })
    Ext 3.3 provides the function xtype:'actioncolumn' now i have replaced my old RowAction with this new build in function and i dont get the "this.config[i].destroy not a function".

    Code:
    {
        xtype:'actioncolumn',
        header:jsRequestGateway.lang["general_actions"],
        width:80,
        scope:this,
        items:[{
            iconCls:'application-edit',
            tooltip:jsRequestGateway.lang["user_edit"],
            handler:function(grid, rowIndex, colIndex){
                 console.log('a');
            }
        },{
            iconCls:'cross',
            tooltip:jsRequestGateway.lang["user_delete"], 
            handler:function(grid, rowIndex, colIndex){
               console.log('b');
            }
        }]
    }
    Is this a general Extjs bug or was the RowAction Plugin the reason for the error ?

    thx for your answers

  6. #6
    Sencha User Animal's Avatar
    Join Date
    Mar 2007
    Location
    Bédoin/Redwood City
    Posts
    30,856
    Vote Rating
    88
      0  

    Default

    The RowAction plugin is now deprecated (Sorry Saki!) in favour of the ActionColumn which provides the same service.

    The RowAction plugin, if it going to be a Column, needs to implement the full Column interface which now includes a destroy method.
    Longtime Sencha engineer. Now surplus to requirements apparently...

  7. #7
    Sencha User evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    18,986
    Vote Rating
    934
      0  

    Default

    This looks like a compatibility issue with a user extension, so I suggest you report it to the original author so they can update it. Unfortunately there's just too many extensions out there made by users for us to check.
    Twitter - @evantrimboli
    Former Sencha framework engineer, available for consulting.
    As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

Similar Threads

  1. Replies: 11
    Last Post: 3 Jan 2011, 12:31 PM
  2. Replies: 2
    Last Post: 15 Apr 2009, 6:03 AM
  3. Replies: 2
    Last Post: 15 Apr 2009, 6:03 AM
  4. [CLOSED] BETA 5: El.setXY(int x, int y, FxConfig config)
    By rob_berlin in forum Ext GWT: Bugs (1.x)
    Replies: 1
    Last Post: 19 Jun 2008, 5:21 AM
  5. Replies: 6
    Last Post: 23 Jun 2007, 5:00 AM

Posting Permissions

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