Moodle

enrol_config.php?enrol=ldap settings not being set

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.8
  • Fix Version/s: 2.0
  • Component/s: Enrolments
  • Labels:
    None
  • Database:
    MySQL
  • Affected Branches:
    MOODLE_18_STABLE
  • Fixed Branches:
    MOODLE_20_STABLE

Description

When trying to set:

enrol_ldap_course_idnumber:
Update local data
Lock value

enrol_ldap_course_shortname:
Update local data
Lock value

enrol_ldap_course_fullname:
Update local data
Lock value

enrol_ldap_course_summary:
Update local data
Lock value

I try and set the values to "Yes" but it does not stay, it submits fine but when going back to the page the settings are still "No"

Issue Links

Activity

Hide
Rahim Virani added a comment -

We use them alot, if an instructor modifies the idnumber to their course it will disconnect all their enrollments further more because the master data source is from our student record system they whould not be able to change the name or shortname, It is assigned by the student record system. This did work in 1.6.5 but is broken in 1.6.5+
[ Show » ]
Rahim Virani - [12/Jul/07 05:28 AM ] We use them alot, if an instructor modifies the idnumber to their course it will disconnect all their enrollments further more because the master data source is from our student record system they whould not be able to change the name or shortname, It is assigned by the student record system. This did work in 1.6.5 but is broken in 1.6.5+

Show
Rahim Virani added a comment - We use them alot, if an instructor modifies the idnumber to their course it will disconnect all their enrollments further more because the master data source is from our student record system they whould not be able to change the name or shortname, It is assigned by the student record system. This did work in 1.6.5 but is broken in 1.6.5+ [ Show » ] Rahim Virani - [12/Jul/07 05:28 AM ] We use them alot, if an instructor modifies the idnumber to their course it will disconnect all their enrollments further more because the master data source is from our student record system they whould not be able to change the name or shortname, It is assigned by the student record system. This did work in 1.6.5 but is broken in 1.6.5+
Hide
Michael Quintero added a comment -

I'd like to add my support for fixing or bringing back this functionality. I'm working on a project to bring a Moodle installation online to replace my institution's Blackboard, and these two features are pretty much essential for how we'd like to do it!

My test installation is using 1.8-stable downloaded on 7/19.

Show
Michael Quintero added a comment - I'd like to add my support for fixing or bringing back this functionality. I'm working on a project to bring a Moodle installation online to replace my institution's Blackboard, and these two features are pretty much essential for how we'd like to do it! My test installation is using 1.8-stable downloaded on 7/19.
Hide
Robert Lamaster added a comment -

Please do not remove these fields. Like several others here, we would like to see this feature fixed. Our courses are populated in Active Directory by scripts that pull from a school registration database. This creates a need to "update local" and "lock" for two reasons:

  • If teachers change the ID number for their course, it no longer matches the course in AD... so Moodle will create a new blank course.
  • If we change anything in the school registration database, such as the course description or ID, that change will occur in AD, but then not match Moodle. Again, depending on what was changed, Moodle will create a new blank course with the new ID. The old course will no longer have student or teacher enrolment.
    So... this is a VERY important feature to get working.
Show
Robert Lamaster added a comment - Please do not remove these fields. Like several others here, we would like to see this feature fixed. Our courses are populated in Active Directory by scripts that pull from a school registration database. This creates a need to "update local" and "lock" for two reasons:
  • If teachers change the ID number for their course, it no longer matches the course in AD... so Moodle will create a new blank course.
  • If we change anything in the school registration database, such as the course description or ID, that change will occur in AD, but then not match Moodle. Again, depending on what was changed, Moodle will create a new blank course with the new ID. The old course will no longer have student or teacher enrolment. So... this is a VERY important feature to get working.
Hide
Randy Thornton added a comment -

I was wondering what the status of this issue is.

The Affected Versions is listed as 1.8 but I have this issue still in 1.9.2 and the issue is still listed as open.

This is a VERY important issue to fix in an LDAP enabled environment where course info is brought over from an enrollments database of some sort. I think these fields are absolutely essential to any serious LDAP enabled professional installation based on automated updates into LDAP from an external enrollments database.

Show
Randy Thornton added a comment - I was wondering what the status of this issue is. The Affected Versions is listed as 1.8 but I have this issue still in 1.9.2 and the issue is still listed as open. This is a VERY important issue to fix in an LDAP enabled environment where course info is brought over from an enrollments database of some sort. I think these fields are absolutely essential to any serious LDAP enabled professional installation based on automated updates into LDAP from an external enrollments database.
Hide
Iñaki Arenaza added a comment - - edited

As far as I know, this issue is sill unresolved (the functionality has never been implemented).

Saludos. Iñaki.

Show
Iñaki Arenaza added a comment - - edited As far as I know, this issue is sill unresolved (the functionality has never been implemented). Saludos. Iñaki.
Hide
Rahim Virani added a comment -

@Inaki,

The functionality was available in 1.5 and 1.6.

Show
Rahim Virani added a comment - @Inaki, The functionality was available in 1.5 and 1.6.
Hide
Randy Thornton added a comment -

@ Iñaki

Thanks for the confirmation.

For the time being, we have overcome the issue of "Lock value" by simply changing the permissions on the Teacher role so that the permissions changeidnumber, changeshortname, and changefullname are set to Prohibit. This works as expected. That should prevent a lot of support issues with accidently changed settings.

But it would be important to have a push/pull updates from LDAP source data working nicely. Even if not dynamic o nuser login like the LDAP course creation process, at least an admin script that could be run when needed.

Thanks

Show
Randy Thornton added a comment - @ Iñaki Thanks for the confirmation. For the time being, we have overcome the issue of "Lock value" by simply changing the permissions on the Teacher role so that the permissions changeidnumber, changeshortname, and changefullname are set to Prohibit. This works as expected. That should prevent a lot of support issues with accidently changed settings. But it would be important to have a push/pull updates from LDAP source data working nicely. Even if not dynamic o nuser login like the LDAP course creation process, at least an admin script that could be run when needed. Thanks
Hide
Iñaki Arenaza added a comment -

Rahim,

There has never been code to deal with those settings (you can check it yourself by having a look at the CVS logs for that file), so I highly doubt it was available in 1.5 and 1.6

Saludos. Iñaki.

Show
Iñaki Arenaza added a comment - Rahim, There has never been code to deal with those settings (you can check it yourself by having a look at the CVS logs for that file), so I highly doubt it was available in 1.5 and 1.6 Saludos. Iñaki.
Hide
Petr Škoda (skodak) added a comment -

I suppose this should be working fine in 2.0, please reopen if not
thanks for the report!

Show
Petr Škoda (skodak) added a comment - I suppose this should be working fine in 2.0, please reopen if not thanks for the report!

Dates

  • Created:
    Updated:
    Resolved: