Hey, it looks like I can create my own folders per user profile, and then direct the Editor to use them per user profile:

Create a custom folder (example: #Domain#-#RandomText#-UserName): like /CompanyX-2FK12K-User1/ 
Editor1.SetSecurityImageGalleryPath = "~/CompanyX-2FK12K-User1/uploads" (exact syntax specified in doc). Is this the pattern recommended by CuteSoft? It would be good enough for me.

 

There's another thing worth noting. We want to have the concept of Super Users and Users. Super Users can create templates, I understand that Cute Editor supports the creation of non-editable templates (very cool) through tag attributes and we will use that. But it would be nice to pull this off by looking up a custom rights table in the DB. Please let us know if this is possible. And this brings up another issue: How do we show a folder of publically sharable templates created by the Super Users as well as show a table of privately created templates (and privately viewable) created by the regular User? The clunky work-around I am thinking of is to write a daemon to replicate a copy of the "public templates" to each private users' folders. Example: ~/CompanyX-2FK12K-User1/Templates/Public/.

 

It would be important that this folder is not mutable. Users shouldn't be able to delete or edit things. They can always copy it to their private folder and attempt to change the copy. And again it would be nice to be able to tag certain "master templates" as not mutable.

 

Yeah... a lot of specs.. but can we do it with Cute Editor? The docs are a little sparse or maybe I am not looking in the right section.

 

Any help would be greatly appreciated!

 

Regards,

-- David