I have had to deal with issues such as these also. However, the authorization packages worked pretty well for me. I created a parent folder for the image, and then a set of subfolders for the various groups that needed access. I applied some folder authorization packages and I managed to restrict the groups to their appropriate subfolders.
On Jan 13, 12:29 pm, CraigNY <[email protected]> wrote: > This is driving me nuts, and frankly, seems so basic. > > We have lots of users, they use a content class with an image. Because > people are people, they are constantly uploading and replacing images. > Ergo, each group is to have its own image folder. Might not be Reddot > approved, but otherwise we'd have anarchy and that is what my bosses > want. So that is what they are getting. > > Apparently, if I restrict folders based on authorizations, then that > is a problem since the image element MUST have a default folder. So I > either have to make about 40 copies of this content class for no > reason or figure out how to programmatically have the default folder > match the authorization. > > This is a serious waste of my time and I am growing ever more > frustrated with this product. > > Or am I whining and is there a better way of doing this. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
