As a Commons user, I would like a more useful default group landing page

One thing occurred to me about the design here: It looks like the content is sorted by post-date descending, but this wont make sense for event nodes since people typically want to sort by event date.

Any recommendations for a light weight ux friendly solution here that fits with the current design :)?

If we're going to include events, we probably want to exclude events in the past.

It looks from the screenshots that this will close issue #1305168: Make Group Menu Display on all Nodes belonging to a group (edit: actually on second thoughts, won't make any difference really, there'll still be little besides the breadcrumbs that remind us we're reading content within a group when viewing a node)

On #2 http://drupal.org/project/views_or would solve this problem, I'm using it exactly for that type of scenario. Problem is, some people might want to see old events.

Marking as "needs work" based on the in-progress patch at #1426616: Group home page improvement, which, is marked as a dupe.

Here's a patch that continues from laurentc's earlier patch.

Changes:

- Set the 'content' tab name via the existing commons_core_set_node_tab_title() callback
- Intercept node/%node/nid via Views argument and 404 if the argument doesn't validate as a group content type
- Related context changes to get consistent blocks on these pages.

Based on discussions with lisarex today, it's ok to leave the Q & A and Events tabs in place.

Laurentc pointed out that the group description in the comp is currently in a part of the page (between the node title and tabs) that we can't target. We probably need to define a new variable via preprocess for inclusion in page.tpl.php to print the group description there, or ay13 suggested that we could define a new page region and place the group description eg via context.

Here's a revised approach that uses context to place the main group content listing View. In my testing this also sets the correct FBSS context for the group activity stream.

The main view here still needs some text improvements (remove blog from title and empty text).

There is still the "Page not found" when viewing content with this patch.

Don't know what we have going on with the hashes in here, is that really normal?

-        'commons_core-group_members' => array(
-          'module' => 'commons_core',
-          'delta' => 'group_members',
+        'views-24dcb59a56254e5a470ee2f23590eed2' => array(
+          'module' => 'views',
+          'delta' => '24dcb59a56254e5a470ee2f23590eed2',
           'region' => 'sidebar_last',
           'weight' => 1,

laurentc resolved the comment in #10 as an artifact in his local environment from previous versions of the patch.

@lightsurge: Those appear to be uuids - I'm not as familiar with Context exports as other exportables, but those block deltas appear to be accepted on fresh installs in our testing.

This patch removes themes/commons_roots/views-exposed-form.tpl.php , which hard-coded a collapsed fieldset around exposed Views filter blocks, making the fieldset impossible to expand by default through the Form API.

Some next steps in addition to those in #9 about empty text:

- Make the exposed filter elements display on the same line
- Display the group description above the tabs (unless lisarex feels that it looks good below the tabs)
- Provide an upgrade path and default for new Commons installs for our altered FBSS Context configuration. Note: FBSS implements its own context system that is separate from the Context module and is not exportable. To export the settings necessary for proper placement of the group activity stream per the comp, we need to export the FBSS-specific OG context, via something similar to:

  $data = facebook_status_all_contexts();
  $fbss_og_context = $data['og'];
  $fbss_og_context['context'] = 'group-home-status-box';
  $fbss_og_context['visibility'] = 3;
  drupal_write_record('facebook_status_contexts', $fbss_og_context, 'type');

Patch update. Improvement of group content filter and group sidebar blocs

Thanks for the improvements here.

To help me with context switching between this and #1411684: New homepage for authenticated users, I'm posting a screenshot a group homepage with the patch from #14.

It seems like the To Dos from #12 remain.

There was a missing file in patch. I've added the theme file to 6.x-2.x. The patch will work for filters but there are the following todos:
- Display the group description above the tabs (unless lisarex feels that it looks good below the tabs)
- Provide an upgrade path and default for new Commons installs for our altered FBSS Context configuration.

I reverted the commit referenced in #16 (http://drupalcode.org/project/commons.git/commit/ee9059e) and added the new file to the attached patch.

We've been working on this at http://drupal.org/sandbox/ezrag/1432998.

I think the remaining tasks are:

- Verify the upgrade process

- Preprocess:
--Update the preprocess code to check the $node->body and if it's not set, use $node->og_mission instead.
-- Make sure to properly sanitize the output (currently is suceptible to cross-site scripting)
-- Ideally move to commons_origins template.php since this is specific to that theme, rather than commons_core.module.

- Change "Group activity" tab menu title to match group title per the comp
- Set the breadcrumb for the group pages to Home=> Community => Group directory
-Theme the "Recent content" block - For me it looks like https://skitch.com/ezra-g/g963x/our-community-c2
- Visual highlighting of the group description per the comp

Here's the latest patch from the sandbox group-homepage branch. Doing a test deployment shortly to verify for upgrading sites.

Here's the latest from our sandbox dev branch. I plan to commit this shortly.

Re-rolled with the --binary flag.

This is committed - Thanks everyone!

http://drupalcode.org/project/commons.git/commit/c42d2de