Refactor: Align Talk and Video Component URLs with Tickets Component Schema

[mariobehling]

The Talk and Video components currently use different URL structures from the Tickets component.
To ensure consistency across the unified Eventyay platform, all public and admin URLs in Talk and Video should follow the same schema:

https://next.eventyay.com/{orgname}/{eventslug}/[component]/

There are exceptions for the Talk component where the /talk slug is not really needed.

This includes all subpages such as schedule, sessions, speakers, rooms, and admin views.

---

🧭 Expected Unified URL Structure

Component	Example Old URL	New Unified URL
Tickets (unchanged)	—	https://next.eventyay.com/{orgname}/{eventslug}/
Talk	https://next.eventyay.com/{eventslug}/	https://next.eventyay.com/{orgname}/{eventslug}/talk
Video	https://next.eventyay.com/video/{eventslug}	https://next.eventyay.com/{orgname}/{eventslug}/video

➡️ All related subpages must follow the same pattern, for example:

• {orgname}/{eventslug}/cfp

• {orgname}/{eventslug}/sessions

• {orgname}/{eventslug}/speakers

• {orgname}/{eventslug}/video/schedule

• {orgname}/{eventslug}/video/sessions

• {orgname}/{eventslug}/video/rooms/{id}

• {orgname}/{eventslug}/video/admin/...

---

🧩 Requirements

• Update routing for all public and admin pages in Talk and Video to use {orgname}/{eventslug}.

• Apply the same pattern to sessions, rooms, speakers, recordings, and related subroutes.

• Ensure internal navigation, API calls, and templates reference the new URLs.

• Add redirects from legacy URLs to maintain backward compatibility.

• Validate that speaker invites, CFP links, and session/room URLs continue to function after migration.

---

🧪 Testing Checklist

• Confirm new URLs render correctly for Talk and Video.

• Verify redirects from old URLs work.

• Test event context resolution via {orgname} and {eventslug}.

• Check all subpages (schedule, sessions, speakers, rooms, admin views).

• Validate cross-component navigation between Tickets, Talk, and Video.

---

🔗 References

• Unified branch: enext

• Related components: eventyay-talk, eventyay-video, eventyay-tickets

Labels: frontend, backend, routing, unification, video, talk, urls

---

Would you like me to append a short Backward Compatibility Strategy section with redirect examples for Nginx/Django to make migration seamless?

[mariobehling]

Please see below. The URL structure is not yet entirely as expected. Due to new 500 errors after recent merges I also cannot fully test on test site, but the following needs to be changed:

1. Talk slug
   Previously https://next.eventyay.com/{eventslug}/ should be -> https://next.eventyay.com/{orgname}/{eventslug}/talk

2. In correct implementation of {orgname}/{eventslug}/speaker
   Expected is {orgname}/{eventslug}/speakers

3. In correct implementation of the link "Sessions". It directs to {orgname}/{eventslug}/talk
   Expected is {orgname}/{eventslug}/sessions

[mariobehling]

We still need this to be working:
Previously https://next.eventyay.com/{eventslug}/ should be -> https://next.eventyay.com/{orgname}/{eventslug}/talk