I want to create a shared folder where users can get images from.  I've seen another post on this (using impersonate), but the way I found to work was to create a virtual folder in IIS to the folder I want to share, then create a physical folder with the same name in the 'users' folder.  That way, the folder shows up in the 'gallery' window.

 

I can now browse to that folder in the 'gallery' window, but when I select and insert an image, the URL is being corrupted.  Instead of seeing /Uploads/Users/John/common/Common_Picture01.jpg I get /Uploads/Users/John/on_Picture01.jpg

Judge,

 

How did you set up Image Gallery path propery?

 

 

 

 

 

Thanks for the reply Adam.  I was actually using the 'Programmatic Security' example from the CuteSoft sample pages (implementSecuritypolicy.aspx).  I put the virtual directory in the 'uploads/users/John' folder and had it point to the 'uploads/member' folder. 

 

I did notice another strange thing: when I've selected the current user as 'John (admin)', I get the error I described above, but when I've selected 'Administrators' and browse to the 'uploads/users/John/common' and select an image from the image gallery, the URL appears as /Uploads/Members/Common_Picture01.jpg (which is basically correct; it's remapping the URL to the real image location, but that's fine).

Judge,

 

Please use app-based path or absolute path. The relative path may cause problems in some situations.

//use the app-based path 

Editor1.Setting["security:ImageGalleryPath"]= "~/uploads";

//use the absolute path 
Editor1.Setting["security:ImageGalleryPath"]= "/uploads";

Keep me posted

Adam, I changed the path to absolute, but I'm getting the same results.  After more testing, it seems like this will work if the virtual directory points below the user's 'uploads' folder, but not if it points above it.  When I redid this test will another folder, I got the error below.  Again, to recreate this all I did was create a virtual directory in IIS that points to a folder, then create a physical folder with the same name.

 

The 'impersonate' solution you posted was quite a while ago, is this still the only other solution to create 'shared' folders?  Because I need my users to be able to create these folders through my web app on the fly, without access to IIS.

(http://cutesoft.net/forums/3413/showpost.aspx)

 

Are you using impersonate?

 

If so, please follow the steps below:

 

1. please check your web.config file and make sure you use impersonation in your web config.