See screenshot, the white submenus on a page like 'Student Life' which point to the view which lists the relevant groups, are pretty insignificant and difficult to spot.

I actually would rather the group listings feature on the page context, ideally for me if placed underneath the page, or perhaps in the sidebar? i.e. a block for 'Student Life' clubs

Also, there doesn't seem to be any obvious way to add a new group 'type' to a page, for example, to have 'classes' in Student Life as well as 'clubs' (I can't even seem to find the context that's putting the club announcements/events etc blocks on these nodes).

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

lightsurge’s picture

Category: feature » bug
Status: Active » Needs review
FileSize
2.33 KB
10.64 KB

There was already an appropriate block view for clubs/departments/teams but it didn't seem to appear anywhere, so this might be a bug.

Here's a patch that puts it in the sidebar when viewing either a group type parent page (i.e. Student Life) or a group. This is also handy as it allows a user to backtrack to a group page easily from viewing a group node.

jgraham’s picture

Assigned: Unassigned » penguininja
penguininja’s picture

I'm actually on the fence about displaying a list of groups in each section in the sidebar—hence the view blocks that don't show up anywhere. My thought in excluding them from the sidebar was that it could become too crowded if a school had, say, 50 departments on their site. The compromise was made to move that to a page in the secondary menu, but I agree this isn't the most intuitive page to find. I'll discuss this with the other members of my team and get back to you.

Regarding creating a new group type, that won't be supported in this distro. Feel free to create your own content types as necessary on your own sites, it just won't be a supported task in Julio. We felt that adding new content types was too complex a task for the majority of our users. (Though if you do create "classes", you might consider creating a feature set for it so that other users can download and use that functionality!)

lightsurge’s picture

My thought in excluding them from the sidebar was that it could become too crowded if a school had, say, 50 departments on their site.

Yes, actually, I see your point :-/

Been thinking about this as I expect with even the first site I might build with this, I'll get a question like, for example, 'Can I have a links page as well as club pages in the Student section'.

One solution I suppose would be to alter the text of 'Clubs' to 'Pages', so that each group is a 'section' as opposed to specifically a club. Of course, if one of those pages is 'Clubs', you could no longer have separate group managers for each club, even though you can have nested pages in an og_menu. Can only think of using og_subgroups, but that looks to be a long way off 7.x-2.x compatibility with OG or indeed a stable 7.x release.

Of course, apart from things like 'clubs' and 'departments' other content could probably just be non-groups, so perhaps something like book module could be used to add sub-pages to the container pages like 'Student Life'. The downside there would be the inability to set content editorial ownership through OG, though.

(Though if you do create "classes", you might consider creating a feature set for it so that other users can download and use that functionality!)

Actually that was a rubbish example of mine, I suppose classes could be Departments!

jgraham’s picture

@lightsurge I'm not sure if I follow your scenario completely regarding

'Can I have a links page as well as club pages in the Student section'.

please see the attached screenshot. The 'secondary links' for each of the sections are sub-menus that can be edited. Unfortunately we have #1512924: Error editing menus: Call to undefined function og_load_multiple() blocking that functionality right now but that functionality should be available once that is resolved if I understand your scenario correctly.

We will not be adding book module to the stack.

jgraham’s picture

FileSize
91.62 KB

missed screenshot referenced in comment 5 :-/

lightsurge’s picture

Title: Group listings on parent page? » How to add subsections to main sections, with links in the secondary (group) menus
Category: bug » support
Status: Needs review » Active

It seemed I needed to have another play with this today, but having tried it, I'm still not sure how the secondary menu for each of the main sections is populated. I suppose this relates to #1517050: Document how to use group posts.

I wasn't completely sure what you meant but thought it might relate to structuring the main section secondary menus with either 'group posts' or 'administrative units' depending on whether or not I want to add share-able/structured areas (i.e. groups that can have membership and subsections through og_menu, using 'administrative units') or simple single owner pages (i.e. group posts).

However, with 'administrative units', when creating them, I only have the option to place them in the primary links menu. With group posts, I don't have the option to place them in a menu at all.

With both, if I remember to take note of the path immediately after creating them, I can add them to the group menus fine, but this doesn't seem particularly user friendly?

jgraham’s picture

Title: How to add subsections to main sections, with links in the secondary (group) menus » Make it easier to add items to menus
Assigned: penguininja » jgraham

I think the best way to address this is to add two links on the respective nodes.

One link will be "Add link to [TEAM NAME] menu" the other will be "Add link to [TOP-LEVEL] section" the language will need to be cleaned up but the [TEAM NAME] link will link to whatever menu corresponding to the group the menu is in, and [TOP-LEVEL] will correspond to whatever section eg. student life, academics etc.

jgraham’s picture

This should be consistent with the flag/feature functionality.

lightsurge’s picture

This could work quite well with the autocomplete in #1516446: Autocomplete for internal links for nivo slider link fields (or something like it).

#8 could be a good way of immediately flagging a newly created node to a menu.

Using an autocomplete helper (if it were moved to julio_core) -> from the 'manage menus' admin UI in a group, we would also be able to reference existing nodes to a group menu, or external links, in a user friendly way.

lightsurge’s picture

Related: #475968: Path helper interface for menu module

Seems there are 3 general suggestions for better menu usability

  1. An autocomplete helper in menu administration
  2. Improving ability to add items to menus from the node
  3. Ability to add items within the currently active menu item (i.e. prepopulated)

I actually think having all three wouldn't hurt. I suppose 2) is what you're planning on, @jgraham

lightsurge’s picture

lightsurge’s picture

lightsurge’s picture

Issue summary: View changes

extended query on how to add group types