Changed the autogeneration of schedule names to use slugified user (person) name, rather than login. Logins are mostly email addresses, and may contain characters not permitted in the URL pattern for schedule names, and are less readable in the contexts where schedule names are used.
- Legacy-Id: 18567
This commit is contained in:
parent
9b6c5735c9
commit
227f83b0da
|
@ -92,7 +92,7 @@ class SecrMeetingTestCase(TestCase):
|
|||
new_meeting = Meeting.objects.get(number=number)
|
||||
|
||||
self.assertTrue(new_meeting.schedule)
|
||||
self.assertEqual(new_meeting.schedule.name, 'secretary1')
|
||||
self.assertEqual(new_meeting.schedule.name, 'sec-retary-1')
|
||||
self.assertTrue(new_meeting.schedule.base)
|
||||
self.assertEqual(new_meeting.schedule.base.name, 'base')
|
||||
self.assertEqual(new_meeting.attendees, None)
|
||||
|
|
|
@ -10,6 +10,7 @@ from django.contrib import messages
|
|||
from django.db.models import Max
|
||||
from django.forms.models import inlineformset_factory
|
||||
from django.shortcuts import render, get_object_or_404, redirect
|
||||
from django.utils.text import slugify
|
||||
|
||||
import debug # pyflakes:ignore
|
||||
|
||||
|
@ -227,7 +228,7 @@ def add(request):
|
|||
)
|
||||
|
||||
schedule = Schedule.objects.create(meeting = meeting,
|
||||
name = "{}1".format(request.user.username),
|
||||
name = "%s-1" % slugify(request.user.person.plain_name()),
|
||||
owner = request.user.person,
|
||||
visible = True,
|
||||
public = True,
|
||||
|
|
|
@ -48,7 +48,9 @@
|
|||
</select>
|
||||
</form>
|
||||
</li>
|
||||
{% if meeting.schedule %}
|
||||
<li><button onclick="window.location='{% url "ietf.secr.meetings.views.rooms" meeting_id=meeting.number schedule_name=meeting.schedule.name %}'">Official Schedule</button></li>
|
||||
{% endif %}
|
||||
</ul>
|
||||
</div> <!-- button-group -->
|
||||
|
||||
|
|
Loading…
Reference in a new issue