Moodle

Unable to set visible or separate group setting for activities from within activity settings

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 1.8
  • Fix Version/s: 1.8
  • Component/s: Groups
  • Labels:
    None
  • Environment:
    XAMPP XP MySQL 4.0.18 PHP 5.1 1.8 beta
  • Database:
    MySQL
  • Affected Branches:
    MOODLE_18_STABLE
  • Fixed Branches:
    MOODLE_18_STABLE

Description

A course has one group of students
Course settnigs: Group mode: Visible, Force No
Group toggle icon is visible for activities and changes state (visually at least when clicked)
In either a new or existng assignment (probably others too) Group mode is No or Yes

There is no way to change the group mode other than select No or Yes. If Yes is selected there is no way of knowing if this is setting Visible or Seperate group mode for that activity.

Also just noticed that if Course settings are set to Sepaerate and Force=Yes, it is possible to select No for group mode in the activity settings. If one does this, the group mode icon on the course page still reflects the forced group mode setting for the course.

Issue Links

Activity

Hide
Ray Lawrence added a comment -

It has been suggested elsewhere:

"I think group mode YES + allow accessallgroups capability = visible groups. Group mode YES + prevent/prohibit accessallgroups capability = separate groups. group mode NO = no group. So an activity set up using group mode can be a separate groups activity or a visible groups activity, depending on the user capabilities."

However, this seems at odds with the commentary in moodledocs: http://docs.moodle.org/en/Capabilities/moodle/site:accessallgroups

"This (accessallgroups capability) allows a user to access all groups in the given context, regardless of the group mode.
For example, a user with this capability set can browse forum posting of other groups when group mode of the forum activity is set to SEPARATE_GROUPS. "

I must confess that I haven't checked this out but the above reads to me like this does not seem quite the same thing as the behaviour described in the "Group mode" help file:

" * No groups - there are no sub groups, everyone is part of one big community

  • Separate groups - each group can only see their own group, others are invisible
  • Visible groups - each group works in their own group, but can also see other groups"
Show
Ray Lawrence added a comment - It has been suggested elsewhere: "I think group mode YES + allow accessallgroups capability = visible groups. Group mode YES + prevent/prohibit accessallgroups capability = separate groups. group mode NO = no group. So an activity set up using group mode can be a separate groups activity or a visible groups activity, depending on the user capabilities." However, this seems at odds with the commentary in moodledocs: http://docs.moodle.org/en/Capabilities/moodle/site:accessallgroups "This (accessallgroups capability) allows a user to access all groups in the given context, regardless of the group mode. For example, a user with this capability set can browse forum posting of other groups when group mode of the forum activity is set to SEPARATE_GROUPS. " I must confess that I haven't checked this out but the above reads to me like this does not seem quite the same thing as the behaviour described in the "Group mode" help file: " * No groups - there are no sub groups, everyone is part of one big community
  • Separate groups - each group can only see their own group, others are invisible
  • Visible groups - each group works in their own group, but can also see other groups"
Hide
Eloy Lafuente (stronk7) added a comment -

Hi, just one personal opinion:

Once more, I think that all those settings, based on capabilities" should be handled directly from the activity configuration interface, i.e. in the forum/chat/assignment.... mod forms, teachers should see the 3 options (no, separate, visible) and use that interface, with help files and so on, to define their group mode. Then, the corresponding add/update module should perform the required actions, adding/deleting capabilities/overrides or whatever is necessary.

I find (and I guess 99% of users too) it really more usable/consistent than adding, saving, updating, going to overrides and saving.

And this is a general thought not only about groups and their way to be configured but to ALL the settings that, being activity based, rely on internal use of capabilities/overrides. Let's do that easy for moodlers!

Ciao

Show
Eloy Lafuente (stronk7) added a comment - Hi, just one personal opinion: Once more, I think that all those settings, based on capabilities" should be handled directly from the activity configuration interface, i.e. in the forum/chat/assignment.... mod forms, teachers should see the 3 options (no, separate, visible) and use that interface, with help files and so on, to define their group mode. Then, the corresponding add/update module should perform the required actions, adding/deleting capabilities/overrides or whatever is necessary. I find (and I guess 99% of users too) it really more usable/consistent than adding, saving, updating, going to overrides and saving. And this is a general thought not only about groups and their way to be configured but to ALL the settings that, being activity based, rely on internal use of capabilities/overrides. Let's do that easy for moodlers! Ciao
Hide
Ray Lawrence added a comment -

+1 for that view point.

The only reason I din't mention it was I'd made the assumption this was a deliberate design decision which was too far along to change (wish I'd spotted this earlier ).

The current i.e. up to 1.7 approach makes sense imo and works fine as far as I can see.

Something that occurs to me too is that changing things here means that anyone with access to activity settings also must be granted permission to overide roles.

Given the nature of users who are likely to be creating/editng activities this may not present a problem in practice that often, but creating a dependency here (and elsewhere - ref. Eloy's post) doesn't seem the best idea in the world.

Show
Ray Lawrence added a comment - +1 for that view point. The only reason I din't mention it was I'd made the assumption this was a deliberate design decision which was too far along to change (wish I'd spotted this earlier ). The current i.e. up to 1.7 approach makes sense imo and works fine as far as I can see. Something that occurs to me too is that changing things here means that anyone with access to activity settings also must be granted permission to overide roles. Given the nature of users who are likely to be creating/editng activities this may not present a problem in practice that often, but creating a dependency here (and elsewhere - ref. Eloy's post) doesn't seem the best idea in the world.
Hide
Pieterjan Heyse added a comment -

I would also like to vote for a revert like 1.6 was. All my end users are very confused now that they cannot select 1 of the 3 modes in the config interface of the activity.

so also a +1 from me.

Show
Pieterjan Heyse added a comment - I would also like to vote for a revert like 1.6 was. All my end users are very confused now that they cannot select 1 of the 3 modes in the config interface of the activity. so also a +1 from me.
Hide
Ray Lawrence added a comment -

Tagging this on here as I believe it's related....

Group settings are now present for resources too, they weren't before..... I'm not sure how this will work.

Show
Ray Lawrence added a comment - Tagging this on here as I believe it's related.... Group settings are now present for resources too, they weren't before..... I'm not sure how this will work.
Hide
Nicolas Connault added a comment -

Duplicate of MDL-8564

Show
Nicolas Connault added a comment - Duplicate of MDL-8564

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: