Moodle

From Iñaki Arenaza (iarenuno at eteo.mondragon.edu) Sunday, 30 April 2006, 03:22 AM:

I guess they just got copied from the auth/ldap config screen, but they are really not used at all.

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+

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.

We are also using LDAP enrolment and if one cannot lock the id number then it makes enrolling via LDAP pointless. As a previous poster mentioned a simple change by an instructor to the id number will make it so that their enrolments are no longer synched with the registrar's data. I am guessing this is also related to the inability to change the LDAP context for the non-editing teacher role earlier on the same page.

The issue remains in 1.9, as well.

We would find it very helpful if we could lock the ID field, as well, or we lose enrollments. Privileges aren't sufficiently granular to restrict the ability to change the ID without removing teachers' ability to change the course settings--and for various reasons, we can't do that.

I'd also like to voice support for making the "Update local" feature functional. There will be times when our course names will change, and we'd like to change that in our LDAP directory (using data from our Student Information System) and have it propogate to Moodle automatically.

Is there any intention of activating this feature?

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.

Adding my +1 to Robert Lamaster above. We need to be able to lock certain course settings, either dependent on the plugin that created the course, or globally.

Thanks for reporting this issue.

We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported.

If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

Michael d;

lqjjLKA0p6

I'm closing this issue as it has become inactive and does not appear to affect a current supported version. If you are encountering this problem or one similar, please launch a new issue.