I tried this out and the inability to use a '~' is a deal breaker, so I went back to 6.1x branch. However I did notice some undesirable behavior when I installed and played with the 2.x branch.

First, I set the Subdomain for Organic Groups - this was very simple and easy. I had already setup a Group Node that had no groups made, and also associated an existing content-type with 100+ nodes to a group-post.

As soon as I created a new Group, all my existing content-type was immediately sent to that subdomain. Ex: It existing as www.mydomain/event/nameofeventhere - after creating the group and doing nothing else, these became groupname.mydomain.com/event.nameofeventhere. The Path Aliases did not change and there appeared no way to force them off the subdomain to the main site.

Also, when on the group hompage (groupname.mydomain.com) and clicking menu links, the subdomain did not change. Ex: clicking "About" from the Primary Links menu took me to groupname.mydomain.com/about instead of www.mydomain.com/about.

That said, without the ability to use a ~ for subdomains, the 2.x branch is unusable for my needs.

Comments

Robin Millette’s picture

Priority: Major » Critical

I've been exploring this as well. In includes/subdomain_mode_group.inc:get_content_subdomain($nid) change "WHERE n.nid = %d" with "WHERE og.nid = %d". Seems to work...

@Richard-411 Why exactly do you need the ~ ?