We are using CuteEditor to allow users to build a blog that contains photos.
In order to do that, they need to be able to upload photos. Now obviously, I don't want one user to update a second users photos. So every person gets their own gallery library. That worked perfectly, I do that through the ASP.NET interface that allows me to specify a specific folder for the gallery.
Now we have a need for some common photos that they can pull down for 'favorites'. So there is a 'common library' that they can use to pull pictures for their profile. So the way I have it set up now, is there are 2 libraries in the gallery (separated by the '|'). A 'common' library, and their 'personal' library. Again, works perfectly. Well, almost.
We have a situation where people are accidently uploading to the 'common' library instead of their 'personal' library. I would like to set the 'common' library up as 'read only', but leave the 'personal' library as 'read/write'.
Now, I know your initial response is to just handle this through Windows Security, and block the ASP.NET userid from having write access. Well, there are 2 problems with that.
#1) We update the common library through the admin interface. So that interface must have 'read/write' access to the library. I can use impersonation on the admin side, impersonate a windows user with write access, and I can get around this issue. While I don't like doing this, it does work. If this were my only issue, I would be fine right here.
#2) The bigger problem, is that when I set the 'common' library to read only, the user receives a program failure that I cannot easily handle. This makes an unfriendly user experience. The BEST solution, is be able to tell CuteEditor that it can only upload to one of the libraries, and not the other.
Any other ideas?