filemanager override the default behavior open action

filemanager suggestion

My backend only receives\delivers encrypted blobs. (It don’t have the keys, it’s incapable of decrypting the file contents before sending then to the client browser)

I’m implementing every method by extending fileManager.services.Backend as suggested in Working with Server of UI Complex Widgets, File Manager Webix Docs

Because of that returning a url in “directLink” is meaningless as the server would send an encrypted file, where the ideia is for it to be decrypted at client side and only then served to the user.

Having a way of telling the filemanager “thanks for pointing the user want to open file X, but do nothing pal, let me handle that from here onwards” would be nice.

Returning false instead of the full path? What do you think?
I know my case is just away of the curve, but I can imagine there are other people, in another scenarios that would benefit from it.

Hello @Luciano_Hebert ,

Thank you for the suggestion and for the detailed explanation of your use case.
However, returning false from directLink won’t work as a cancellation mechanism. The open and download methods in the Operations service pass the result directly to window.open without checking for a false value, so you can’t prevent the action that way.

But you can achieve this by customizing the Operations service and rewriting its open and download methods with your own logic.

Please check the example: Code Snippet