Moodle

allow enrolment modules to modify the course edit form

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.8, 1.8.1, 1.8.2
  • Fix Version/s: 2.0
  • Component/s: Course, Enrolments
  • Labels:
    None
  • Affected Branches:
    MOODLE_18_STABLE
  • Fixed Branches:
    MOODLE_20_STABLE

Description

The authentication plugin can lock fields on the user edit form, but the enrolment plugin can't modify the course settings form.

This is a problem, because our enrolment system pulls most of the data from an external system. We rely on certain fields being in a certain form to synchronize properly. Also, some fields will get overwritten when the synchronization is done. If we let teachers edit them, it causes confusion.

It should be fairly easy to have a method on the enrolment class that can modify the form.

Issue Links

This issue blocks:
MDL-4537 can't lock LDAP course ID number in admin Minor Open
MDL-9979 enrol_config.php?enrol=ldap settings not being set Major Closed
This issue will help resolve:
MDL-5219 Course Settings are getting to long Minor Open
This issue has been marked as being related by:
MDL-17949 List of problems related to potential enrolment rewrite in 2.0 - META Minor Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Alan Trick added a comment -

Also, some options are completely irrelevant for our enrolment plugin (like cost). Being able to remove those would cut down the unnecessarily long page.

Show
Alan Trick added a comment - Also, some options are completely irrelevant for our enrolment plugin (like cost). Being able to remove those would cut down the unnecessarily long page.
Hide
Permalink
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
Permalink
Petr Škoda (skodak) added a comment -

yes, this is now possible in 2.0
thanks for the report

Show
Petr Škoda (skodak) added a comment - yes, this is now possible in 2.0 thanks for the report

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.