[SOLVED] Group homepage tabs with different paths

After thinking about this some more there may be other questions to answer that help solve this problem.

1) What exactly does the Organic groups: Groups argument do? I see it validates group nodes on the node ID. Is there anyway to make that go against the node title?

2) How would we handle two arguments? Basically making the first argument be the (group) node type and the second being the node title (assuming we solve #1 above).

And to summarize the original post for easier reading....

I'm trying to create tabs on my group home pages, each tab representing a different content type... and using a more elaborate URL alias for each different group content type.

Here are a couple of things I learned...

* Views do not (and should not) overwrite a node. The node seems to always win out.
* To have view page tabs show up on a node, have the page url use node/%/

Here is how I went about this...

I will do a more thorough step-by-step writeup when I have more time.

1) Create the group content types and give it a machine readable name (e.g. team, social, etc.) that you want to use in the path.

2) Create the pathauto settings (e.g. groups/[type]/[title-raw]) for each of your group content types.

3) Clone the og_ghp_ron view so you can make modifications.

4) Add a page for each group posting content type (e.g. news, discussions, events, etc.) that you want a tab for. Set the page url using the following nomenclature node/%/news. Set the menu to tab and give it a tab name.

Up to this point it has been pretty easy. The only issue now is that each tab points to node/%/ instead of groups/[type]/[title-raw]/ (desired). Here's where it sort of gets tricky but with the rules module we can handle this.

5) Create rules to remove and create the additional aliases to point to node/%/

(the following is copied from another thread I was researching which actually helped me solve this issue.)

Here was my basic rule setup...

Delete Node Aliases Ruleset
- Delete all aliases that point to system path
- Delete all aliases that point to system path
- ... (and so forth)

Create Node Aliases Ruleset
- Create alias #1 to point to path A
- Create alias #2 to point to path B
- ... (and so forth)

Triggered Rules
- IF new node created (and any other conditions) THEN call Create Node Aliases ruleset.
- IF node deleted (...) THEN call Delete Node Aliases ruleset.
- IF node updated (...) THEN call Delete Node Aliases and then call Create Node Aliases

So far this has worked great but I'm sure issues will arise. One I can think of off-hand is how the aliases are built. I use tokens and build the aliases using the [title-raw] token. It's possible that two nodes could have the same title. That would create the same alias twice, each pointing to a different node.

So after all of this, when a group node is created / updated I end up with the tabs on the group node and the appropriate aliases. I need to test whether using the raw tokens is best or not however.