Well you could put the css, js and images onto a different server altogether as long as the cms server can acces the website where they are located. And then just put the full http address into the locations. That way you coul dhave access restricted to the individual people/teams.
On Jan 15, 2:24 pm, jkinzel <[email protected]> wrote: > Thanks Tony, > > A quick follow up. Do you put any CSS images into those folders then > as well? I'm still not entirely convinced this method is going to work > for our particular situation. The problem is I work in a highly > distributed environment and each department wants to be able to > control as much of their site as possible. If we did it in this > manner, we would need to give them access to the virtual folders on > the CMS cluster, something I doubt our system admins will want to do, > so I'm trying to figure out a happy medium for everyone, but it looks > like we may have to make these a content class (despite the > performance hit).
-- 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.
