Community Milestone Walkthrough Fixes

[davinotdavid]

Description of the Change

Each of the items for the milestone has been tackled in a commit so it is easier to check it individually:

• Sort google calendars by primary first
• Remove zoom placeholder reference in VideoMeetingLink step
• Fix missing i18n label for custom availabilities
• Fix height not filling the window for public routes
• Extend width and change id of Share Your Link input

Benefits

• Better UI polish for the Community Release

Applicable Issues

Fixes #1440

[rwood-moz]

All of the updates look good. Although I am seeing an issue when running locally. I had availability set to Mon-Fri. If I go into Availability, click on Sat and Sun to add those days to availability, then try to save, the updated availability never save and in the console I am seeing this error:

postgresql-1  | 2026-01-20 18:14:01.793 UTC [5418] ERROR:  duplicate key value violates unique constraint "ix_schedules_slug"
postgresql-1  | 2026-01-20 18:14:01.793 UTC [5418] DETAIL:  Key (slug)=(CUqb/sT7KYmNkgi2absvBA==) already exists.
postgresql-1  | 2026-01-20 18:14:01.793 UTC [5418] STATEMENT:  UPDATE schedules SET slug=$1::VARCHAR, weekdays=$2::JSON, time_updated=now() WHERE schedules.id = $3::INTEGER
backend-1     | TRACE:    185.199.109.133:39926 - ASGI [172] Send {'type': 'http.response.start', 'status': 500, 'headers': '<...>'}
backend-1     | INFO:     185.199.109.133:39926 - "PUT /schedule/2 HTTP/1.1" 500 Internal Server Error
backend-1     | TRACE:    185.199.109.133:39926 - ASGI [172] Send {'type': 'http.response.body', 'body': '<21 bytes>'}
backend-1     | TRACE:    185.199.109.133:39926 - ASGI [172] Raised exception
backend-1     | ERROR:    Exception in ASGI application

Do you see this also or is it just my stack for some reason?

[davinotdavid]

@rwood-moz thanks for the review! That's an interesting error, seems like it is complaining of a duplicated schedule id 🤔 I don't see it happening on my end. Does this happen if you do a complete wipe of the containers + volumes?

Screen.Recording.2026-01-20.at.1.16.37.PM.mov

[rwood-moz]

@rwood-moz thanks for the review! That's an interesting error, seems like it is complaining of a duplicated schedule id 🤔 I don't see it happening on my end. Does this happen if you do a complete wipe of the containers + volumes?
Screen.Recording.2026-01-20.at.1.16.37.PM.mov

I did blow away the containers/volumes the first time but I just did it again and restarted the stack and this time it works, sorry maybe I missed a volume the first time or something.

[devmount]

lgtm!