I have a client who wants to build two OpenACS sites. They are sort of like Siamese twins. The sites each have their own domain name, and they look different. Some of the data to be stored is confidential, and so groups must be used to control what area of each site each user can access. The two sets of users will have a fairly large intersection, and should have the same group membership in both sites. Users will authenticate against an external Radius server instead of having local logins.

At first glance this looks like a good use of subsites, but the shared data seems like a problem. For example, there will be a lot of text content (probably stored in xowiki) and some of it needs to be viewable from both sites, though one of them can be designated as the only one that gets write access to it. I have not looked closely at subsites yet but this does not sound like how I understood them to work.

Any suggestions as to the best way to approach this?

Thanks in advance!

I figured out the problem, but not how to fix it.

In acs-subsite/www/admin/groups/new.tcl, the name of the new group is collected from the user in groups.group_name. This value ends up stored in acs_object through some form builder mojo in groups::new (acs-subsite/tcl/group-procs.tc) that I don't fully understand. After that it gets run through convert_to_i18n, but the same mojo does not happen there, and I can't seem to get at the value myself to pass it on to convert_to_i18n. The end result is that my nice group name gets converted to an i18n key with a blank message associated with it.

I'll file a bug. Fortunately, for my purposes I can comment out the call to convert_to_i18n, since I don't need it.

Hi Janine,

Is it true that your plan is to have two subsites, under the Main Subite? That there will be some members who will have access to both subsites, but not all?

From what I have learned about permissions and groups in OpenACS, you will need to add those users who need to read both subsites, to the groups for those subsites.

The original idea of subsites, afaict was to have some content that could appear in two different subsites, and users would be restricted to just the subsite they were a member of. In this case, the users only are in one subsite, but teh shared content (somehow) shows up in both places. Most likely this was intended to be accomplished by mounting a package in both subsites.

I don't know of anyone using OpenACS this way, so we need to take what exists, and mold it to our needs, I guess you need some way to setup a user so it will be amember of two different groups easily.