I’m having an issue with a single user being the author/Web site manager/group owner of more than one OpenScholar site (these are all scholar sites at the moment).
What I’m trying to do is have a central user manage all the sites for the school. She has done the initial content setup for these sites, in conjunction with a website relaunch for the school that occurs next week. The goal is to centralize OpenScholar site administration with her and her office. Faculty have not yet been trained and the faculty users have not yet been setup (with the exception of a few pilot users). Once faculty are trained and added to the system, we would like to limit their permissions so they don’t use the control panel – they would use the “green buttons” to add/edit content and contact the central user as needed to modify Features, Theme and other site settings. We want it to be super easy for faculty to add and edit content and not have to trouble them with learning the ins and outs of the Control Panel.
My idea was to essentially make John Doe a Scholar User (not Scholar Admin or Web site manager) of his own scholar site.
The problem is the system is tying the bio/cv feature to the user, not the site. So, the first bio/cv that was setup is displaying on every site the central user owns. Further, the system is getting confused with auto-alias, if there is a custom page with the same name on multiple sites owned by the central user, the system is appending integers to the end of the URL alias, even though the sites are different. For example: www.site.com/j-doe/custompage and www.site.com/sallysmith/custompage-1
My idea seemed like a good way to tackle our use case but obviously we have hit a snag - is there a solution to this problem? Any thoughts or ideas for other ways to accomplish limiting what people can see/do on their own scholar sites? Is leaving the website manager field blank an option (see screen grab)?