Bug report

When using the trackpad for a laptop, the tap event does not fire when selecting files in the Kendo UI FileManager.

Reproduction of the problem

1. Go to our Events Live demo
2. Using a laptop's trackpad, try to select a file.

Current behavior

The tap event will not fire the Select event.

Expected/desired behavior

The tap event should fire the Select event.

Note

This event does fire for a physical mouse click, and with the touch event on a mobile device.

Environment

• Kendo UI version: 2024.2.514
• jQuery version: All Supported Versions
• Browser: all

Bug report

In the FileManager, if you configure the Grid as editable through the views.grid option, clicking on the editable Grid cells results in duplicated row data.

Workaround: - use the setOptions method to enable editing in the Grid - https://dojo.telerik.com/uMAxULUR/4

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/uMAxULUR/7
2. Select the Grid View
3. Click on the Documents cell and then the Images cell several times, without making any changes

Current behavior

The row data is duplicated

Expected/desired behavior

The row data shouldn't be duplicated

Environment

• Kendo UI version: 2024.1.130
• Browser: [all]

For the future it would be nice if a separate "move" endpoint was optionally available since many of us tend to use virtual filesystem layouts instead of real filsystems.

That said, I used the advice here to setup my own custom handling for file moves:

FileManager - Detect move vs copy in UI for ASP.NET MVC | Telerik Forums

If I preventDefault, I can only do 1-2 moves before I am then unable to navigate the folders anymore through either column. If I allow it to propogate and fire off the create and destroy request (my serverside functions ignore these as invalid), the navigation continues to work.

Can you suggest what events I can maybe fire manually to trigger success without making the create and destroy request, or suggest another way to fix this issue?

My move handler:

function onexecute(e) {
        if (e.command == "MoveCommand") {

            var d = {
                'items' : e.options.items,
                'targetfolder' : e.options.target
            };

            $.post('/Data/Gallery_move?aid=@Model.Asset.ID', d)/*, function(data){
            });*/
            
            //e.preventDefault();
        }
    }

Moving files MORE than one level upwards in a folder hierarchy is bugged.

If you have a nested folder hierarchy like this:

folder1

          folder2

                   folder3

1. moving a file from folder1 to folder2 works.

2. moving a file from folder2 to folder1 works.

3. moving a file from folder1 to folder3 works.

4. moving a file from folder3 to folder1 is BUGGED.

I have the issue in my code, but I also tested it in your demo site and it has the same problem.

https://demos.telerik.com/kendo-ui/filemanager/index

I have uploaded a screen dump of the error output from Chrome.

It is in or after the DataBinding event (Comming from Create action), the the error occurs, thus causing the Delete action and refresh of the UI to never occur.

The bug occurs in both Chrome and IE Edge.

Please fix the bug.

I am running into inconsistencies when using the toolbar Search input of a File Manager object after navigating to new folders.  

Simple dojo for reference - https://dojo.telerik.com/aPOtiXex/2

Steps to reproduce

1. Click on "Folder1" in the treeview.
2. In the Toolbar Search, enter the text "Sub 1001".  This will correctly filter the displayed items.
3. Click on "Sub 1001" in the treeview.  Notice that the search filter is still in place, but that it is not applied to the current folder view.
4. In the Toolbar Search, remove the text 1 character at a time.  Notice that as you remove characters in the Search input, the filter IS applied to the current folder view.  Continue removing characters until the Search input is empty.
5. Click on "Folder1" in the treeview.  Notice that the contents of the folder are STILL filtered as if the Search filter was "Sub 1001", even though Search input is currently empty.
6. In the Toolbar Search, add 1 space character, then remove it.  Notice that this finally clears the filter applied to the folcer in step #2.

I am not sure what the best answer for this scenario would be.  Maybe navigating to a new folder should clear the search filter criteria in the toolbar and clear any applied filter criteria to the previous folder?  Or maybe the toolbar search input should be reset to accurately reflect the current applied filter for the folder on navigate?  Something good for your dev team to discuss, but it is clear that the current implementation will create some confusion for users.

Bug report

In FileManager read request is triggered twice when navigating to a parent folder that has a nested folder. The issue does not occur if the folder contains only files without a nested folder.

Reproduction of the problem

1. The issue can be replicated if a nested folder is created in the demo service. The screencast here demonstrates the issue.

Current behavior

Two identical requests are sent when the parent folder is selected.

Expected/desired behavior

There should be a single request when navigating to a parent folder, even if it has a nested child folder.

Environment

• Kendo UI version: 2022.1.119
• Browser: [all ]

Bug report

When a node in the TreeView of a Kendo UI FileManager is selected, then the parent node is collapsed, and re-expanded, the selection is removed.

Reproduction of the problem

1. Go to the following Progress Kendo UI Dojo.
2. Expand the Root node
3. Select Folder Inner 1
4. Collapse Root
5. Re-expand Root

Current behavior

The selected node within a parent after collapsing and expanding will lose its selection. Here is a screencast of the above in action.

Expected/desired behavior

The selection should persist even upon expanding/collapsing parent nodes.

Environment

• Kendo UI version: 2021.2.616

Bug report

Calling the loaded method on a FileEntry instance does not reset the loaded flag.

function onNavigate(e) {
            var filemanager = e.sender;
            var path = e.path;
            var entry = filemanager.dataSource.get(path);
            if (entry.loaded()) {
                entry.loaded(false);
            }
        }

Reproduction of the problem

1. Run this dojo
2. On the TreeView section of the Filemanager navigate to both folders, so the contents of the folders are loaded
3. Navigate between the Folders using the TreeView and note the loaded flag is not reset

Current behavior

Calling entry.loaded(false); does not reset the loaded flag of a FileEntry instance.

Expected/desired behavior

Calling entry.loaded(false); should reset the loaded flag of a FileEntry instance.

Environment

• Kendo UI version: 2021.1.330
• Browser: [all]

Bug report

In mobile devices, when a nested folder is renamed in the FileManager, the parent folder is displayed in the dialog for renaming.

Reproduction of the problem

1. Open our Demos and choose a mobile device in the emulator
2. Create a nested folder and try to rename it.

Current behavior

The parent folder name is displayed in the dialog for renaming. The parent folder is renamed after saving (screencast)

Expected/desired behavior

It should be possible to rename nested folders on mobile devices.

Environment

• Kendo UI version: 2021.1.224
• Browser: [ all ]

Feature Request

The tooltip for the ListView button (ListView) in the FileManager is misleading. Consider renaming it to "thumbnails" or less confusing text. Currently, it leads to the impression that the items would be represented as normal list instead of as items in the ListView widget.

Expected/desired behavior

Less confusing text should be used for tooltip for the ListView button.

As of version  "@types/kendo-ui": "2020.3.0":

FileManager methods: path, view, getSelected, getSize have return type void, which is a pain to handle since it can't even be cast to bool.

FileManager method navigate doesn't accept params, should accept string 'path'.

FileManager method executeCommand doesn't accept params, should accept as per https://docs.telerik.com/kendo-ui/api/javascript/ui/filemanager/methods/executecommand .

FileManagerContextMenu interface is missing all event handlers: close, open, activate, deactivate, select.

The following are not exposed:
- kendo.data.schemas
- kendo.ui.filemanager.commands

Follow steps in sample at https://dojo.telerik.com/@GaloisGirl/OJUPoYOY/8

• Actual result: the call to "create" has no information that the new folder should be created in "folder 1"
• Expected result: the call to "create" should contain information about the path, for my back-end to create an entry in the correct place

Probably related to https://feedback.telerik.com/kendo-jquery-ui/1473893-filemanager-no-path-passed-to-datasource-read-method / https://github.com/telerik/kendo-ui-core/issues/5890

Bug report

Reproduction of the problem

1. Reproducible in the demos: https://demos.telerik.com/kendo-ui/filemanager/index
2. Type in "Doc" in the FileManager's search input
3. Double-click the Documents folder
4. Clear the search input
5. Click the Home icon in breadcrumb

Current behavior

The FileManager shows only the Documents folder

Expected/desired behavior

The FileManager shows all folders on root level (Documents and Images)

Environment

• Kendo UI version: 2020.2.617
• jQuery version: x.y
• Browser: [all]

I'd like to request the ability to hide and display certain files.  For example, hide all pdfs, but show docx files.

Thanks!

Hi,

I've tried to configure resizable columns in File manager grid like in the following 

sample

It works, but I got a confirm popup panel when I try to resize ...

What's wrong ..??

Thanks

Bug report

Reproduction of the problem

Dojo example.

1. Click on "Folder" in the treeview

Current behavior

The file in the selected folder is displayed as "undefined"

Expected/desired behavior

The file data is properly retrieved and displayed.

A workaround is available in this dojo example: https://dojo.telerik.com/ORImIvaC

Environment

• Kendo UI version: 2020.1.114
• jQuery version: x.y
• Browser: [all]