The showactivitydates field had the wrong length of 4. This changes
it to 1.

It should be under the "Completion tracking" subheading just like in
the course form.

Simey Lameze authored Feb 26, 2021 and jun committed Apr 02, 2021

Part of MDL-70817

Simey Lameze authored Mar 09, 2021 and jun committed Apr 02, 2021

Part of MDL-70817

Simey Lameze authored Mar 13, 2021 and jun committed Apr 02, 2021

Part of MDL-70817

Simey Lameze authored Mar 08, 2021 and jun committed Apr 02, 2021

Part of MDL-70817

The activity information output component displays information about
an activity module that can contain:
1. Activity dates
2. Completion information
   a. A manual completion button; or
   b. A list of automatic completion conditions and their statuses.

This patch also includes a new JS module called
core_course/manual_completion_toggle for toggling the
completion state of activities that support manual completion.

Add the functionality of toggling the completion state of an
activity with manual completion to the core_course/repository
JS module.

Allow the core_completion_update_activity_completion_status_manually
web service function to be called from AJAX as well. This is needed
by the new manual completion toggle button in the
core_course/completion_manual template.

* Class cm_completion_details builds the custom completion details
for an activity module.

This change removes references in code and comments to a few
deprecated functions that were accidentally missed in the larger
change.

The code changes only affect service_users.php. I made it support
custom user profile fields in this query, because it was easy
enough, rather than adding another TODO to fix later.

Note that there wasn't any case of multiple testcase classes in
1 file. All the cases reported in the issue were false positives
caused but other "mock/fixture" files being named _test.

So all this issue does is:

1) rename any _test suffixed class in test files, because we are
   going to start renaming a lot of test classes to _test.

2) ensure that the 2 test case classes modified in this issue,
   are already observing the filename = classname rule that will
   be implemented soon (and verigy it works).

This patch adds some changes to guarantee that OpenBadges 2.1 (OBv2.1)
will return always the same JSON format that OBv2.0 (because the only
difference between both versions it's the BadgeConnect API).