⭐ New Features
- The event details show the user why it is not possible to register for a slot. Reasons for this may include lack of community membership for reserved places, exclusion from a community, or lack of requirements due to the settings in the feature preview. (commit: 5ea09384, #118)
- Happy New Year! 🎉 (commit: 59951b1b)
- Custom styling for GTO. (commit: 180a382d)
- Reservations for the groups now always display the name in a tooltip, even if the community has its own logo. (commit: a6652996)
- By moving the community administration to its own page (Update 09.12.2024), the member overview can take up more vertical space. (commit: 912d38ac)
🐞 Bug Fixes
- Reservists no longer advance to slots that are not available to them. The /random_slot command now also only selects available slots. (commit: 50fec8c6)
- If a user was banned from a community, they could no longer join any other community. (commit: edd0e7d1)
🔮 Feature Preview
- The experiment with extended information on requirements (detailed requirement list) has been discontinued. The additional information does not provide any meaningful added value and overloads the settings of the available requirements for event details. (commit: 8aa54296, 15418573)
- Requirements for the entire event, individual squads and slots. The requirements for a slot are built up additively via the hierarchy. To participate, all conditions of the slot + squad + event must therefore be met. (commit: d0c255dd, 705bee40, 6853e191, 403e79c0)
- Display of requirements for the event, squad and slot. (commit: a6652996, 1ecaef35, 60bf9f83)
- Participants can mark requirements that they do not yet meet and for which self-assignment is permitted as fulfilled for themselves via the event details. After that, they will no longer be notified that they do not meet the requirement for other events. (commit: 9f483ac0, 497f106a)
- Community administrators have been given the option to manage the fulfilment of requirements without permitted self-assignment for members in their community’s member overview. (commit: dd5f1a4c, baecd936)
- In the management of available requirements, in addition to the names and authorisation for self-assignment, the obligation and images for the individual requirements can now also be configured. (commit: f438dd6a)
- Explanation of rejected slot attempts. (commit: 50fec8c6)
- When a member leaves a community, all fullfilled requirements for that community are automatically deleted. (commit: 1cd9a07b)
🔨 Technical
-
Performance improvements in the member overview.
- Where previously a separate ban dialogue was created for each member, there is now only one, which is also reused for managing the requirements. (commit: dd5f1a4c)
- All administrative actions for members are now only downloaded by administrators, which optimises initial access to the site for everyone else. (commit: 6a72c48f)