You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I do not see for which slot a user had registered, if he unregistered later. The log file messages do not contain this information. Can you add the slot id there?
Examples for affected messages:
The user with id 5775 registered to a slot of the organizer activity with the course module id 9390.
The user with id 5775 unregistered from a slot of organizer activity with the course module id 9390.
The user with id 5778 was added to the queue of a slot of the organizer activity with the course module id 9390.
The user with id 5778 was removed from the queue of a slot of the organizer activity with the course module id 9390.
The user with id 5774 has assigned an appointment of organizer activity with the course module id 7866.
The text was updated successfully, but these errors were encountered:
Hey, in our next release (v.3.7.x) we'll focus on the new feature "multiple registrations", so we won't have ressources to improve it at the moment. If you provide a pull request, we can have a look and insert it in our plugin.
Currently I do not see for which slot a user had registered, if he unregistered later. The log file messages do not contain this information. Can you add the slot id there?
Examples for affected messages:
The user with id 5775 registered to a slot of the organizer activity with the course module id 9390.
The user with id 5775 unregistered from a slot of organizer activity with the course module id 9390.
The user with id 5778 was added to the queue of a slot of the organizer activity with the course module id 9390.
The user with id 5778 was removed from the queue of a slot of the organizer activity with the course module id 9390.
The user with id 5774 has assigned an appointment of organizer activity with the course module id 7866.
The text was updated successfully, but these errors were encountered: