In the FileExplorer's init event, I am setting a custom provider and the upload and delete paths (based on custom security implementation). Before upgrading to the Q2 release, everything worked fine. Now...
My "solution" was to wrap everything in the init function inside the following if condition:
|if (!Page.IsCallback && !Page.IsPostBack) |
| docExplr.Configuration.ContentProviderTypeName = typeof(FileContentProvider).AssemblyQualifiedName; |
| /// other logic |
| docExplr.Configuration.DeletePaths = UserOwnedPaths; |
| docExplr.Configuration.UploadPaths = UserOwnedPaths; |
| docExplr.EnableCreateNewFolder = true; |
That fixed the issue, great... except that now the FileExplorer control doesn't appear to be using the custom content provider for postbacks.
Another issue I noticed was that I have some links that use a querystring parameter to set the initial path for the FileExplorer. Even when my partial "solution" is in place, it does not work in this scenario unless I switch to a different folder and then switch back.
I suspect that these issues are related to the change in the Q2 release so that the tree and grid are populated on the initial page load, rather than using callbacks. I'm hoping Q2 SP1 will fix those issues, but I see that hasn't been released yet. Has anyone else encountered this? Figured out a fix for it?