I may have a big misunderstanding about sitegroups. Is it legal to have root topics (up="0") in different sitegroups with the same name? E.g.
SiteA
- Topic - "Main" SiteB
- Topic - "Main"When I try to add topic "Main" to SiteB in Aegir, it gives me an error because of the name collision. However, I can programmatically create the new topic using the mgd_create_topic function.
mgd_auth_midgard( "admin!SiteB", "pass", false); mgd_create_topic( 0, "Main", ...);
HOWEVER... if I then perform a mgd_get_topic_by_name( 0, "Main")... it appears that I may get either SiteA's Main or SiteB's Main... maybe depending on the sort order in the database?? I have seen, for example...
mgd_auth_midgard( "admin!SiteB", "pass", false); $top = mgd_get_topic_by_name( 0, "Main");
and $top returns the SiteA Main topic!
So, is it true that Aegir is actually doing the right thing by enforcing uniqueness of root topic names across sitegroups?
If this is the case, then it would seem that the value of sitegroups is greatly lessened. It would seem that if you wanted assign sitegroups to different organizations, it might be impossible to enforce uniqueness of topic names between companies.
Any information about this would be greatly appreciated! BTW, I'm using Midgard 1.5 on RedHat 9, using the noddle.net rpms.
Thanks in advance! /Jim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
