Ambiguity conflict between equally names tracks and teams

[bkimminich]

Having a team with the same name as a track will make some (or maybe even all) generated links go to the team instead of the track.

Workaround: Do not use identical names for tracks and teams, duh! :grinning:

[fzipi]

I think that it is a bug in the teams partial.

[fzipi]

Well, I can't reproduce that in production. Links are generated using the type: in the front matter. So it should generate the correct one if the type is track or team.

@bkimminich Could you provide more info about it?

[bkimminich]

I deleted the team OWASP Juice Shop until this gets fixed. If you create any team with the same name as an existing track you should experience this issue.

[fzipi]

Will try using that, thx.

[fzipi]

Could you please add again your team? Thanks!

[bkimminich]

Done, PR is up!

[bkimminich]

Still not fixed. Try going to https://open-security-summit.org/tracks/owasp-juice-shop/working-sessions/juice-shop-hackathon2/ and then click the "Track" link to "OWASP Juice Shop". It will send you to https://open-security-summit.org/teams/owasp_juiceshop/ instead of expected https://open-security-summit.org/tracks/owasp_juiceshop/.

[fzipi]

Weird. It doesn't...?

[bkimminich]

I guess Hugo doesn't know the difference between types. If you create a participant named "OWASP Juice Shop" I'm pretty sure link will all go there as its alphabetically seen first by Hugo... Just a wild guess... 🤔

[fzipi]

Well, it's not hugo, is how we use it :( That specific step is generic, so we weren't checking the document's type. But I think we should rewrite it.

Will create a new issue with the generic problem, so we can think in a more generic solution.