Results 1 to 4 of 4

Thread: EXT 4.1.3: error when removing nodes from tree

    Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format.
  1. #1

    Default EXT 4.1.3: error when removing nodes from tree

    I try to remove a node from a tree

    node = tree.getRootNode().findChild("id", "myId", true);

    This produces an error in (the red line)
    The error occurs because store is of type TreeStore, and TreeStore does not have a remove function. It inherits from AbstractStore and the remove function is added in Store.When I remove the boolean (node.remove(false)) then there's no error, but the node is kept in the store...

    This error did not occur in Ext 4.1.1

    callback = function(operation)
    args = [me, operation];
    if (operation.wasSuccessful()) {
    for(storeCount = stores.length; i < storeCount; i++)
    { store = stores[i];
    store.remove(me, true);
    if (isNotPhantom) {
    store.fireEvent('write', store, operation);
    Ext.callback(options.success, scope, args);
    } else
    Ext.callback(options.failure, scope, args);
    Ext.callback(options.callback, scope, args);

    Any help would be appreciatedCaius Caesar
    Last edited by Caius Caesar; 24 Jan 2013 at 7:04 AM. Reason: missing linebreaks

  2. #2
    Sencha Premium User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Gainesville, FL


    Have you tried with 4.2?
    Mitchell Simoens @LikelyMitch

    Check out my GitHub:

    Posts are my own, not any current, past or future employer's.

  3. #3


    No, didn't realize it was out there. It's still in Beta, isn't it?

    We have a big app in the making and experience some issues with every Ext upgrade. We moved just yesterday from 4.1.1 to to 4.1.3. and we can't afford to upgrade the minute there's a new version out.

    Having said that, we do make an effort not to stay behind too far, so when 4.2 is released, we will try it and upgrade quickly, if there are no issues.

    In the meantime...

    What about the bug. It looks like an outright omission to me. Will there be some sort of patch?

    Caius Caesar

  4. #4
    Sencha User
    Join Date
    Jun 2013


    i have the same problem in ExtJS 4.2.1

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