[Beta 1] Saki's FileTree for Ext 2.0

[jbird526]

Button disappearing seems to be BrowseButton problem. Try to ask loeppky to look at it.

Im sorry, upon further investigation, there are known issues with IE 6/7 with the BrowseButton.

[sdrew]

Thsi is how I fixed the browse button disappearing issue in Ext.ux.UploadPanel.js in the onRemoveFile:function, comment out these lines:

// if (wrap) {
// wrap.remove();
//}

Steve.

[sdrew]

Hmm, difficult to say anything reasonable on that. Is it UploadPanel, IE7 (why not IE6 then?) or Ext problem? No idea.

Somebody else?

Its not Ext as I use alot of Ext and windows/forms etc with IE7 and no leaks, only adding UploadPanel introduce that and as I explained your website shows the problem also.

If you notice the leaks they are elements added by Ext.ux.UploadPanel.js in the initComponent function.

It adds up to about 10-20 Meg each time you open the uploadPanel window and add a file to it. IE7 never gets that memory back so on workstations average memory they slowed down very quickly.

I put alerts in the destroy functions of UploadPanel, but they never get called, should they on page unload?

I'm sure its another IE7 bug, but must be some way to workaround that.

Thanks.
Steve.

[mystix]

Thsi is how I fixed the browse button disappearing issue in Ext.ux.UploadPanel.js in the onRemoveFile:function, comment out these lines:

// if (wrap) {
// wrap.remove();
//}

Steve.

might better to simply check for IE (so you don't end up breaking the code):

if (wrap && !Ext.isIE) {
    wrap.remove();
}

[jbird526]

might better to simply check for IE (so you don't end up breaking the code):

if (wrap && !Ext.isIE) {
    wrap.remove();
}

Ive tried both ways of commenting out and adding the isIE. Still not working for me but I really appreciate the response by the community. Im sure its my implementation, because I am still having problems with getting the browse button to click. The hovering DIV never fully overlays the button for me.

[ferrenliu]

I catch an error, when I use this filetree to create 'NewDir'. The error just throw in IE8 beta2 like below
------------------------
Type not equal
------------------------
I trace and found out the error has be throw at the code of ExtJs 2.2. Detail is

node.ui.getEl().scrollIntoView(this.tree.body);

Any body know how to fix it?

[jsakalos]

Generally, Ext doesn't support browser's beta releases, however, Ext team is glad to be informed on problems. If it's core Ext problem, find please an appropriate thread and post it there.

[Arthur.Blake]

I admit it looks misleading. Upload file is menu item of UploadPanel, including everything below it.

Not exactly sure why that menu item is needed at all? Is it supposed to be a "header" for the display items below it? IMHO It is very misleading. Pressing Ctrl-U on FF 2/Linux causes View Source popup. Why not remove this menu item? Is not the 'Add' item by itself clear enough?

Also, unrelated, I noticed a little security issue on your server side... Creating a folder with a name such as "../aaa" underneath a folder named "hello" causes the folder to be created one level up as "helloaaa". Creating folders such as "../../../hello" doesn't do anything noticeable (presumably it created the folder on your server in a place that I shouldn't have access to!?!)

Another little irritating issue (FF2/Linux), creating a new folder, causes the window to scroll up to the point where New Folder is shown at the very top.

Thanks for your great ux!

[wulfshayde]

Hi Saki,

Great plugin, though I've had an error arise that I can't figure out for the life of me. I'm using Coldfusion for the server side language and uploads were working, but recently they've stopped.

This is my .js

    var upform = new Ext.ux.UploadPanel({
             id:'uppanel',
             url:'/index.cfm',
             path:'/site/modules/IT/UserFiles/attachments/',
             baseParams:{
                 event:'addAttachment',
                 returnFormat:'json'
             },
             maxFileSize:1048576,
             bodyStyle: 'width: 99%; margin-bottom: 10px;'
    });

And my back-end cf code:

    <cffunction name="addAttachment" access="public" output="true" returntype="void">
        <cfargument name="event" type="any" />
        <cfoutput>{"success":true}</cfoutput>
        <cfabort />
    </cffunction>

I keep getting the error "cannot decode JSON object"...

I'm only responding to the request with that one line {"success":true} so what am I missing?

Thanks in advance...

[jsakalos]

Put a breakpoint in the code and see what is real responseText received. Generally, if it had worked before, I'd search for the change that could have caused it is failing now. New version of something?