I noticed when I was creating pages for organic groups, that the path aliases weren't coming through correctly? When creating a organic group page, you enter the Path for that page, which does seem to work. But the path alias for the organic group is lost. So you should see this: group/foo/foo_page, but instead it is: node/25/foo_page. Where would I look for the path alias to be used for the page?

Comments

moshe weitzman’s picture

I was thinking that sites who need to alias these custom pages would use admin/build/path ... perhaps i should add an url alias field for sufficiently permissioned users.

moshe weitzman’s picture

Category: bug » feature
mshaver’s picture

I was thinking I could use a custom alias, but if my og groups already have a path aliased defined (pathauto), it would be nice to adhere to this. I noticed the same issue when creating views that are tabs attached to a group home page. Since you must use the "node/$group/xxx" as the url to get the tab to show up on the group home page. I actually think the new og_panels module is awesome, but if I'm trying to create a default pages tab for all groups, it's not really possible? You have to use the views as before. Could it be possible for someone to create a default page for all groups?

moshe weitzman’s picture

See og_collections module for default panel pages for all groups.

moshe weitzman’s picture

Status: Active » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

OpenChimp’s picture

+1 for the idea of including the ability to create a path alias for og panel pages. It would be great if it provided a default based on the path_auto settings for the group. :)

Regarding creating a panel page that works for all groups, can't we just use the method outline http://www.tejasa.com/node/160? This method takes advantage of panels node override functionality, and allow for a unique panel layout for each group type.