You found a bug! We've classified it as a bug in our system. We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #281
    Sencha Premium Member
    Join Date
    Aug 2007
    Location
    Pilsen, Czech Republic
    Posts
    40
    Vote Rating
    0
    dherbolt is an unknown quantity at this point

      0  

    Default


    Quote Originally Posted by usha.basavaraju View Post
    Trying to migrate from ext2 to ext4.
    Used compatability file also.But still getting this error
    Error: [Ext.extend] Attempting to extend from a class which has not been loaded on the page.
    javascript//ext-4.1.1a/ext-all-debug.js
    Line 4391

    Please help..
    It seems that you are trying to extend ExtJS class which does not exists in ExtJS4 anymore. You can try to use ext-all-dev.js instead of ext-all-debug.js. ext-all-dev.js logs many useful informations into browser's console.
    You can also set breakpoint into ext-all-dev.js to line 5908 (impl. if Ext.extend) and see the name of non-existing superclass.
    Code around the line 5908:
    Code:
        //<feature classSystem.backwardsCompatible>
        // Backwards compatible
        Ext.extend = function(subclass, superclass, members) {
            if (arguments.length === 2 && Ext.isObject(superclass)) {
                members = superclass;
                superclass = subclass;
                subclass = null;
            }
    
            var cls;
    
            if (!superclass) {
                Ext.Error.raise("Attempting to extend from a class which has not been loaded on the page.");
            }
    Note that in ExtJS4 you should use Ext.define instead of Ext.extend to define a new class/subcalss.

  2. #282
    Sencha User
    Join Date
    Oct 2007
    Location
    Berlin, Germany
    Posts
    889
    Vote Rating
    9
    wm003 will become famous soon enough

      0  

    Default


    You really should upgrade to Ext 3.4 first and ensure everything works fine. Then try the compatibility layer (which is meant for Ext 3-> Ext 4) again and try to migrate to Ext4. It will probably throw errors again, but these may be different or easier to fix. Do you also use 3rd party plugins/extensions which the compatilbilitylayer may not support? Then you also need to get Ext 4 Version of them. Ext3-4 is pain enough for large projects but Ext2-4 without a working Ext3 Version of your project will probably never get finished.

  3. #283
    Sencha User
    Join Date
    Feb 2013
    Posts
    2
    Vote Rating
    0
    rageshp_moxie is on a distinguished road

      0  

    Default


    Hi all,
    Good Day ..

    I have upgraded my Application from extjs 3 to extjs 4. But my Firebug is showing error :

    TypeError: clsData.postprocessors is undefined


    Ext.apply(Ext.panel.Panel.prototype, {
    ext3-compat.js (line 31)


    TypeError: Ext.panel.Panel is undefined
    Ext.apply(Ext.panel.Panel.prototype, {
    ext3-compat.js (line 31)


    TypeError: clsData.postprocessors is undefined
    postprocessor = clsData.postprocessors.shift(),
    ext-all-debug.js (line 4718)


    TypeError: Ext.Container is not a constructor
    hidden:false

    Here is my code :

    var TabItem = new Ext.Container
    (
    {
    title: TabData[iTab].text,
    tabCls: showTabStrip ? 'TabStripVisible' : 'TabStripInvisible',
    id: tabId,
    itemId: tabId,
    idPrefix: Id,
    layout: 'border',
    anchor: '0 0',
    plain:true,
    hideBorders: true,
    items:
    [
    {
    layout: 'anchor',
    region:'west',
    hideBorders: true,
    width: 10,
    minWidth:1,
    id: Id + 'PaneLeft',
    cls: 'SD_PanelLeft',
    bodyStyle: 'background-color: transparent',
    hidden:false

    },{
    region: 'center',
    layout: 'border',
    hideBorders: true,
    id: Id + 'Main',
    items: MainItems
    },{
    layout: 'anchor',
    region:'east',
    hideBorders: true,
    width: 10,
    minWidth:1,
    cls: 'SD_PanelLeft',
    bodyStyle: 'background-color: transparent',
    hidden:false
    },
    {
    region: 'south',
    cls: 'SD_PanelLeft',
    bodyStyle: 'background-color: transparent',
    height: 10,
    hidden:false
    }
    ]
    }
    );

    Please help.

  4. #284
    Sencha User
    Join Date
    Feb 2013
    Posts
    2
    Vote Rating
    0
    rageshp_moxie is on a distinguished road

      0  

    Default Ext 3 to 4 Migration issue

    Ext 3 to 4 Migration issue


    Hello


    TypeError: m.postprocessors is undefined

    R eload the page to get source for: http://localhost:1339/Content/js/ext/ext-all.j


    Can you please help

  5. #285
    Sencha User
    Join Date
    Apr 2013
    Posts
    4
    Vote Rating
    0
    er_abhisinha is on a distinguished road

      0  

    Default AutoHeight grid view in ExtJs4

    AutoHeight grid view in ExtJs4


    Hi,

    I have recently started migrating my app to use ExtJs4 which previously was using ExtJs 3.X.

    Now, so as to set the auto height of GridPanel in ExtJs 3.x I used to extend gridview class using code:

    var autoheightgridview = ext.extend
    (
    ext.grid.gridview,
    {
    onlayout: function ()
    {
    ext.get(this.innerhd).setstyle("float", "none");
    this.scroller.setstyle("overflow-x", "scroll");
    }
    }
    );

    but while migrating my app to ExtJs 4.2.x I have modified my code to:

    Ext.define('Ext.grid.AutoHeightGridView', {
    extend: 'Ext.view.Table',
    onLayout: function ()
    {
    Ext.get(this.innerHd).setStyle("float", "none");
    this.scroller.setStyle("overflow-x", "scroll");
    }
    });

    which I guess defines a new class Ext.grid.AutoHeightGridView.

    Now when i assign this class in the View property of grid panel I get error:

    config is undefined if (config.grid.isTree) {

    The code which I am using is:
    var xg = Ext.grid;
    var grid1;

    grid1 = new xg.GridPanel({
    store: store,
    cm: cm1,
    viewConfig: {
    forceFit: false
    },
    //height: 343,
    autoHeight : true,
    loadMask: true,

    //width: 800,
    width:getAdminGridWidth(),
    view: new Ext.grid.AutoHeightGridView(),
    renderTo: 'bdy',
    viewConfig: {
    onLoad: Ext.emptyFn,
    listeners: {
    beforerefresh: function(v)
    {
    // v.scrollTop = v.scroller.dom.scrollTop;
    // v.scrollHeight = v.scroller.dom.scrollHeight;
    // v.scrollLeft = v.scroller.dom.scrollLeft;
    // v.scrollWidth = v.scroller.dom.scrollWidth;
    },
    refresh: function(v)
    {
    // v.scroller.dom.scrollTop = v.scrollTop +
    // (v.scrollTop == 0 ? 0 : v.scroller.dom.scrollHeight - v.scrollHeight);
    // v.scroller.dom.scrollLeft = v.scrollLeft +
    // (v.scrollLeft == 0 ? 0 : v.scroller.dom.scrollWidth - v.scrollWidth);
    }
    }
    },

    bbar: new Ext.PagingToolbar({ pageSize: 10,
    store: (store), displayInfo: true, displayMsg: 'Displaying records {0} - {1} of {2}', emptyMsg:"No records to display"})
    });


    Can someone tell me where exactly I am going wrong? Any help will be highly appreciated.

  6. #286
    Sencha User
    Join Date
    Jan 2009
    Posts
    8
    Vote Rating
    0
    oniram88 is on a distinguished road

      0  

    Default


    Error:

    TypeError: operation is undefined

    if (this.sortParam && operation.sorters && operation.sorters.length > 0) {line 1594





    File: ext3-compat.js
    line: 1593

    before: getParams: Ext.Function.createInterceptor(Ext.data.ServerProxy.prototype.getParams, function(params, operation) {

    after: getParams: Ext.Function.createInterceptor(Ext.data.ServerProxy.prototype.getParams, function(operation) {


    I insert a console.log(arguments) in the function ad i see that i receive only one argument:
    "Ext.data.Operation"

  7. #287
    Sencha Premium Member ethraza's Avatar
    Join Date
    Jun 2007
    Location
    Brazil
    Posts
    362
    Vote Rating
    3
    ethraza is on a distinguished road

      0  

    Default Viewport layout problem

    Viewport layout problem


    Hi.

    After a long time away from ExtJs now I'm back, trying to migrate my ExtJs3 websystem to ExtJs 4, so I can buy an Architect licence and start new wild stuff with it.

    I have made a lot of progress. It is not showing error any more. But it is showing some weird layout behavior that I can't find how to fix.

    My app is made by a Viewport and it is acting like that:
    1- When I click the left panel hide button, it goes away but left a twin behind, that can be hiden too.
    2- The button (a help button) on the left panel is not showing up.
    3- On the center panel, the tab is behaving slow and strange, not always layouting.
    4- Still in the center panel, there is a Grid on the first tab, but only the Grid header is showing up, the Grid body id behind a div that contains nothing and if I give this div a 0 height, the Grid shows up.

    If all the problems are not related, I would like to ask some insight at least on the first problem.

    Here is the app with ExtJs 3: http://websys.ghsix.com.br/?comp=1
    Here is the app with ExtJS 4: http://websys.ghsix.com.br/dev/to4.html?comp=1

    Thanks for n F1.
    LAMPE (Linux / Apache / MySQL / PHP / ExtJs)

  8. #288
    Sencha User
    Join Date
    Jan 2008
    Location
    Levittown, PA
    Posts
    316
    Vote Rating
    2
    mjhaston is on a distinguished road

      0  

    Default


    Quote Originally Posted by mschwartz View Post
    I am watching our 3.4 project deteriorate before my eyes. First it was double click on a grid row -> open tab in tab panel leaves everything in the whole browser selected, now the grids are failing.

    After we've spent tens of thousands of dollars developing and supporting this application, a port to 4.1 is an enormous task. And even if we did port to 4.1, 5.x will come out and leave our 4.1 version obsolete.

    After seeing how we've been left in the dust by Sencha, how can I recommend we use it for any core applications? We'll continue to use Sencha products where appropriate, but we won't expect a lifetime beyond a couple or three years anymore.


    This is what I'm deathly afraid of .... We are just getting rolling with ExtJS applications. I've written three so far. The first was in ExtJS 3.4 and I see what you are talking about. My GoogleMap extension is now blocked by most browsers, I know this is a third-party extension I'll have to take care of. I also see a basic form that has crazy left-right scroll bars across the page in Firefox, but not other browsers. That wasn't there when I developed it a year ago!

    The other two application are written in ExtJS 4.x (I believe 4.2 for both). I guess I will need to go back through that 3.4 app and convert it all. It's not easy. There are a lot of little config that have changed that aren't obvious.

    Will I need to do this in a year or two and convert my 4.x stuff to 5.x just to get it to work? This will be a tough sell. I work on an IBM iSeries (AS/400) where stuff written 20 years ago still works without issue. The users love the new look and functionality of my apps, but will management love the maintenance?

  9. #289
    Sencha User ovillemain's Avatar
    Join Date
    Sep 2011
    Location
    France
    Posts
    3
    Vote Rating
    0
    ovillemain is on a distinguished road

      0  

    Default Compatibility mode + Combobox with PageSize = Error

    Compatibility mode + Combobox with PageSize = Error


    Pagination in combobox is impossible with compatibility layer ("ext3-compat.js").


    Firefox > Firebug says :
    Code:
    + TypeError: config.store is undefined
    ext-all-dev.js (ligne 49276)
    > me.callParent([config]);
    Chrome > Developer Tools says :
    Code:
    Uncaught TypeError: Cannot set property 'pageSize' of undefined (ext3-compat.js)

    HTML file :
    Code:
    <html><head>
      <script type="text/javascript" src="https://mydomain/path/ext-4.2.1.883/ext-all-dev.js"></script>
      <script type="text/javascript" src="https://mydomain/path/ext-4.2.1.883/compatibility/ext3-core-compat.js"></script>
      <script type="text/javascript" src="https://mydomain/path/ext-4.2.1.883/compatibility/ext3-compat.js"></script>
      <link rel="stylesheet" type="text/css" href="https://mydomain/path/ext-4.2.1.883/resources/css/ext-all.css" />
      <script type="text/javascript" src="https://mydomain/path/getusers.js"></script>
    </head>
    <body>
      <div id="mydiv"></div>
    </body>
    </html>
    JS file "getusers.js" :
    Code:
    Ext.onReady(function() {
      Ext.create('Ext.form.field.ComboBox', {
        pageSize     : true, // <== throws error if "true" and use of "ext3-compat.js" on dropdown
        valueField   : 'id',
        displayField : 'name',
        store        : {
          fields   : ['id', 'name'],
          proxy    : {
            type   : 'ajax',
            url    : 'https://mydomain/path/getusers.php',
            reader : {
              type : 'json',
              root : 'users'
            }
          },
          pageSize : 5
        },
        renderTo : 'mydiv'
      });
    });
    That works without "ext3-compat.js", or if there is no pagination with combobox.

  10. #290
    Sencha User
    Join Date
    Feb 2014
    Posts
    4
    Vote Rating
    -1
    darkwata is an unknown quantity at this point

      0  

    Default Error how to resolve

    Error how to resolve


    I get the following error:

    Code:
    [BREAKING][4.0][Ext.Component] applyTo: Attempted to render the component to the applyTo target's parent node, but this failed. You must resolve this manually before the component can render. This is a breaking change that cannot be resolved in the compatibility layer!
    If I do a stack trace it looks like it happens here and seems to be related to prototype:

    Code:
    this.panel = Ext.create('Ext.panel.Panel', {            renderTo:'fileManagerPane',
                border:false,
                tbar: [
                {
                    text:'New',
                    handler:this.newWorkspace.bind(this)
                    },
    
    
                    {
                    text:'Deploy',
                    handler:this.getListOfChanges.bind(this, this.deployWorkspace)
                    },
    
    
                    {
                    text:'Delete',
                    handler:this.deleteWorkspace.bind(this)
                    },
                    this.workspaceSelector
                ]
            });
    before that code I have this line (Element is from prototype):

    Code:
    workspaceSelector:new Element('select')
    Any help would be greatly appreciated.

Similar Threads

  1. Migration to 3.0
    By tillda in forum Community Discussion
    Replies: 5
    Last Post: 17 Aug 2009, 7:19 AM
  2. Migration to 2.0
    By scaswell1 in forum Ext GWT: Help & Discussion (1.x)
    Replies: 1
    Last Post: 7 Jul 2009, 9:56 PM
  3. migration 1.0 to 3.0
    By alien3d in forum Ext 3.x: Help & Discussion
    Replies: 2
    Last Post: 1 Jun 2009, 5:38 AM
  4. Migration GXT 1.2.4 to 2.0
    By G.edwin in forum Ext GWT: Help & Discussion (1.x)
    Replies: 2
    Last Post: 15 May 2009, 6:26 AM

Thread Participants: 110

  1. aconran (1 Post)
  2. mystix (1 Post)
  3. ap (2 Posts)
  4. evant (1 Post)
  5. ethraza (1 Post)
  6. steffenk (5 Posts)
  7. brookd (4 Posts)
  8. dherbolt (2 Posts)
  9. tore.kjorsvik (1 Post)
  10. wm003 (2 Posts)
  11. stevil (4 Posts)
  12. vlads (3 Posts)
  13. paubach (1 Post)
  14. BuckBazooka (1 Post)
  15. dbraiden (1 Post)
  16. mjhaston (1 Post)
  17. demon222 (1 Post)
  18. SToto98 (1 Post)
  19. rebe (1 Post)
  20. zombeerose (6 Posts)
  21. rich02818 (3 Posts)
  22. sg707 (3 Posts)
  23. vpopa (1 Post)
  24. hschaefer123 (3 Posts)
  25. jchau (1 Post)
  26. chrisvensko (1 Post)
  27. DannyMeister (3 Posts)
  28. dajester2008 (1 Post)
  29. mschwartz (4 Posts)
  30. wgpubs (4 Posts)
  31. LisburnLad (2 Posts)
  32. edspencer (3 Posts)
  33. firefoxSafari (9 Posts)
  34. Luckyman (3 Posts)
  35. oniram88 (1 Post)
  36. danguba (7 Posts)
  37. cnesbit (2 Posts)
  38. Jangla (1 Post)
  39. MuadDib-DK (1 Post)
  40. abctenorio@gmail.com (1 Post)
  41. uzver (3 Posts)
  42. zhangt (2 Posts)
  43. peet (3 Posts)
  44. ZachG (3 Posts)
  45. yyogev (7 Posts)
  46. pcr (4 Posts)
  47. 大漠穷秋 (1 Post)
  48. jacurry (4 Posts)
  49. excyberlabber (6 Posts)
  50. dongryphon (3 Posts)
  51. Henrik Rutzou (1 Post)
  52. hazimdikenli (1 Post)
  53. paparent85 (1 Post)
  54. Ekambos (3 Posts)
  55. burnie (1 Post)
  56. aaronbartell (1 Post)
  57. mattgoldspink (1 Post)
  58. dbrin (1 Post)
  59. CraigMyers (1 Post)
  60. Francois Lecroart (5 Posts)
  61. BulletzBill (1 Post)
  62. tumbochka (1 Post)
  63. a.l (2 Posts)
  64. c.darmon (8 Posts)
  65. Dipish (1 Post)
  66. blex2010 (2 Posts)
  67. kpalser (1 Post)
  68. ldonofrio (2 Posts)
  69. DHainzl (6 Posts)
  70. MrSparks (2 Posts)
  71. rebeccapeltz (1 Post)
  72. Jeremy Solarz (1 Post)
  73. RLBruggers (2 Posts)
  74. Ourysso (1 Post)
  75. jjohnston (1 Post)
  76. ShaneMc (9 Posts)
  77. msmolyak (1 Post)
  78. watermark (1 Post)
  79. lukefowell89 (3 Posts)
  80. winkelmann (1 Post)
  81. willjohnathan (1 Post)
  82. cayenne_08 (1 Post)
  83. SebTardif (3 Posts)
  84. mberrie (3 Posts)
  85. rijkvanwel (1 Post)
  86. george4voc (1 Post)
  87. Jehu (2 Posts)
  88. freeranger (4 Posts)
  89. Inoc (1 Post)
  90. eCoast (1 Post)
  91. dstarr@allofe.com (3 Posts)
  92. bee (2 Posts)
  93. /mbr (3 Posts)
  94. ptraczynski (1 Post)
  95. qqjianyue (1 Post)
  96. jmf10024 (1 Post)
  97. Reggae (2 Posts)
  98. wimh (1 Post)
  99. jas88 (1 Post)
  100. Roho (1 Post)
  101. lokisapocalypse (1 Post)
  102. ovillemain (1 Post)
  103. Flashmattic (2 Posts)
  104. testnina123 (1 Post)
  105. jlimaye (2 Posts)
  106. rivanov (1 Post)
  107. usha.basavaraju (1 Post)
  108. rageshp_moxie (2 Posts)
  109. er_abhisinha (1 Post)
  110. darkwata (2 Posts)