I would like to see a thumbnail of the image in the FileManager for images. Currently it shows an icon for images. In place of the image icon I would like to see a small thumbnail of the image.
I would like to request the functionality to be able to preview MS Word and PDF documents in the preview pane of the Kendo UI FileManager.
Thank you!
Implement a mechanism that allows the content of a folder to be refreshed every time it is opened. Currently, on opening a folder a request to the "read" end point is sent and the content of the folder is loaded. But on subsequent opening of the same folder the FileManager does not send further requests. If there have been changes to the folder's structure, they won't be reflected in the FileManager, because it doesn't refresh the data. An auto-refresh functionality could resolve that.
A configuration option could allow enabling/disabling this functionality, e.g.,
.AutoRefresh(true)
Request to add these common feature for file manager
1) Back and Forward button / command
2) Cut, Copy and Paste button / command
Is it possible to implement an option that enables the paging of the Grid View?
For example:
@(Html.Kendo().FileManager()
.Name("filemanager")
.Views(gridView => gridView.Grid(grid => grid.Pageable()))
...
)
The FileManager component makes the assumption that all files and directories can be uniquely adressed by name and path.
Unfortunately, this isn't true in many cases: identifying a specific file could require additional information (like database record ID or namespace) that cannot be provided globally for the page and therefore needs to be stored individually with each file entry inside the client's datamodel.
(In my case, different entities in the database have their own "virtual storage" where files are references as items stored in a cloud block storage service. This means that I can several files with the same name and path (but diffreent content) referenced in the database or even several files with the same name and folder linked to the same entity).
As a workaround, if there is no need to represent folder structure at all, the "path" field can be used to hold the database ID of the file and that field can then be used by the Javascript that generate the download link (and other file action URLs).
After trying to use a richer object in the JSON returned to the FileManager Read action, I have come to the conclusiong (confirmed by support), that doing so will break the compnent (rename will not trigger any action on the server, update will cause a JS error inside the kendo libraries).
My suggestion would be to add some additional field to the data model to hold domain-specific information. That field should be handeled in a transparent manner by the Kendo component and it should be made available to any Javascript method. Ideally, I would have loved to be able to add a full set of properties to the client-side object but a single additional string property would actually be enough for everything I need to do.
Hello Team,
when I add new folder then I rename it to 1.1 it show me 1.1.1 but the folder name is 1.1 and in properties 1.1 but I don't want it to show 1.1.1
the file manager add .1 automatically and if I rename it 2.2 it add .2 then the file display name 2.2 .
Please help,
Thank you,
The built-in upload components event cannot be handled through the TagHelper:
<kendo-filemanager name="filemanager">
<upload on-upload="onUpload"></upload>
...
</kendo-filemanager>
When using the following configuration an error is thrown, thus making it unable to set the Grid columns:
<kendo-filemanager name="filemanager" upload-url="@Url.Action("Upload", "FileManagerData")">
<views>
<grid>
<columns>
<column field="name"></column>
</columns>
</grid>
</views>
</kendo-filemanager>
When using the FileManager initialized using the TagHelper and renaming nested folders a 404 error is thrown.
A 404 - File or directory not found is returned
The folder should be renamed
When the FileManager is defined using TagHelpers the defined schema is not serialized
The following FileManager definition:
<kendo-filemanager name="filemanager" upload-url="@Url.Action("FileManagerUpload", "FileManager")">
<filemanager-datasource>
<transport>
<read url="@Url.Action("FileManagerRead", "FileManager")" type="POST" />
<create url="@Url.Action("FileManagerCreate", "FileManager")" type="POST" />
<destroy url="@Url.Action("FileManagerDestroy", "FileManager")" type="POST" />
<update url="@Url.Action("FileManagerUpdate", "FileManager")" type="POST" />
</transport>
<schema>
<filemanager-model id="path" has-children="hasDirectories">
<fields>
<field name="path" type="string" from="Path"></field>
<field name="name" type="string" from="Name"></field>
<field name="extension" type="string" from="Extension"></field>
<field name="created" type="date" from="Created"></field>
<field name="createdUtc" type="date" from="CreatedUtc"></field>
<field name="modified" type="date" from="Modified"></field>
<field name="modifiedUtc" type="date" from="ModifiedUtc"></field>
<field name="size" type="number" from="Size"></field>
</fields>
</filemanager-model>
</schema>
</filemanager-datasource>
<toolbar>
<items>
<item name="createFolder" />
<item name="upload" />
<item name="sortDirection" />
<item name="sortField" />
<item name="changeView" />
<item name="spacer" />
<item name="details" />
<item name="search" />
</items>
</toolbar>
</kendo-filemanager>
generates the following script, without a schema definition:
<script>
kendo.syncReady(function() {
jQuery("#filemanager").kendoFileManager({
"uploadUrl": "/FileManager/FileManagerUpload",
"toolbar": {
"items": [{
"name": "createFolder"
}, {
"name": "upload"
}, {
"name": "sortDirection"
}, {
"name": "sortField"
}, {
"name": "changeView"
}, {
"name": "spacer"
}, {
"name": "details"
}, {
"name": "search"
}]
},
"dataSource": {
"schema": {
"model": {
"id": "path",
"hasChildren": "hasDirectories"
}
},
"transport": {
"destroy": {
"type": "POST",
"url": "/FileManager/FileManagerDestroy"
},
"read": {
"type": "POST",
"url": "/FileManager/FileManagerRead"
},
"update": {
"type": "POST",
"url": "/FileManager/FileManagerUpdate"
},
"create": {
"type": "POST",
"url": "/FileManager/FileManagerCreate"
}
}
}
});
});
</script>
The FileManager DataSource schema should be serialized
File Manager's toolbar overflow button does not show when the items are marked with the overflow setting.
The overflow button is not displayed when one of the items is configured with the overflow setting.
The overflow button should be displayed when one of the items is configured with the overflow setting similar to the conventional toolbar widget's items.
The AllowedExtensions configuration for the Upload in the FileManager is not exposed and allowed extensions cannot be configured.
The following configuration for the Upload in a FileManaget is not supported:
@(Html.Kendo().FileManager().Name("filemanager")
.Upload(upld=>upld.Validation(val=>val.AllowedExtensions(new string[] { ".doc" , ".jpg" })))
)
while it is available in a standalone Upload component:
@(Html.Kendo().Upload()
.Name("files")
.Validation(validation => validation.AllowedExtensions(new string[] { ".pdf" }))
)
The allowed extensions should be configurable in the FileManager
File Manager's built-in Search tool filters incorrectly when the input is cleared.
Regression introduced with 2023.1.314
Clearing the Search input's value does not re-render the existing folders and files.
Clearing the Search input's value should re-render the existing folders and files.
When setting the <dialogs>
and/or <messages>
configuration of the FileManager TagHelper
<dialogs>
<upload />
<rename-prompt />
<delete-confirm />
<move-confirm />
</dialogs>
<messages>
<dialogs>
<upload clear="Clear files" />
<move-confirm />
<delete-confirm />
<rename-prompt cancel="Do not rename" ok-text="Yes rename"/>
<export-as-dialog />
<search />
</dialogs>
</messages>
an error is is shown and the configuration cannot be compiled:
RZ2011 Tag helpers 'Kendo.Mvc.TagHelpers.FileManagerDialogsUploadSettingsTagHelper' and 'Kendo.Mvc.TagHelpers.FileManagerMessagesDialogsUploadSettingsTagHelper' targeting element 'upload' must not expect different TagStructure values.
Add the above configuration an the try to compile the FileManager TagHelper configuration.
No error should be thrown and a valid configuration should be compiled.