So my project now requires version control on documents, not just a file explorer. I decided I could try to accommodate this by having both a file explorer and a grid, the grid being old versions of what the currently selected file in the explorer.
We are using a database on our backend and it is implemented and functional with the file explorer. To be able to do version control I was able to modify the server side code to allow for versioning. I have two issues, both being with the file explorer that are stopping me from implementation of version control.
1. I need to be able to communicate from the file explorer to the grid that houses historical files. When a user clicks a file in the file explorer, I need ajax to load the historical files. Again, I have the backend set up already to do this. I do not see any onclick, or onClientClick methods available to use at the fileexplorer. How can I access these events to trigger the ajax.
2. The upload that comes with File Explorer is pretty out of the box and I see no way to access it. Whenever I try to upload a file that already exists I receive:
"A file with a name same as the target already exists!"
How can I trump this message and allow inserting into the data. This is not an overwrite. Since I had to extend the FileBrowserContentProvider class for my DB implementation I assume that the uploader is calling one of the methods in my custom provider, which in turn is telling the front end that the record exists. Basically, what server side method that I over wrote does the out of the box uploader call to determine a file already exists? Whatever method that is I need to apply code to always return that the file does not exist.
If we can resolve these two issues I will have a working File Explorer/ Grid user control that can do Version Control.
Thank you in advance for any input or help.
We are using a database on our backend and it is implemented and functional with the file explorer. To be able to do version control I was able to modify the server side code to allow for versioning. I have two issues, both being with the file explorer that are stopping me from implementation of version control.
1. I need to be able to communicate from the file explorer to the grid that houses historical files. When a user clicks a file in the file explorer, I need ajax to load the historical files. Again, I have the backend set up already to do this. I do not see any onclick, or onClientClick methods available to use at the fileexplorer. How can I access these events to trigger the ajax.
2. The upload that comes with File Explorer is pretty out of the box and I see no way to access it. Whenever I try to upload a file that already exists I receive:
"A file with a name same as the target already exists!"
How can I trump this message and allow inserting into the data. This is not an overwrite. Since I had to extend the FileBrowserContentProvider class for my DB implementation I assume that the uploader is calling one of the methods in my custom provider, which in turn is telling the front end that the record exists. Basically, what server side method that I over wrote does the out of the box uploader call to determine a file already exists? Whatever method that is I need to apply code to always return that the file does not exist.
If we can resolve these two issues I will have a working File Explorer/ Grid user control that can do Version Control.
Thank you in advance for any input or help.