In one conference track there were 2 events with the same name, for the second event the tabs would not load, so it couldn’t be deleted. Workaround was to rename the title first, which fixed the tabs, and allowed deleting the duplicate.

Submitted by Danny Groenewegen on 9 November 2018 at 15:02

On 15 November 2018 at 12:17 Elmer van Chastelet commented:

When I look at the implementation, it seems to already use the event key as tab id. Duplicate event names should not cause such issue, except when there is a difference between the event keys that gets filtered out in HTML/URLs. Do you remember the event name?


On 15 November 2018 at 12:17 Elmer van Chastelet closed this issue.

On 15 November 2018 at 12:17 Elmer van Chastelet reopened this issue.

On 15 November 2018 at 12:17 Elmer van Chastelet tagged 1.3.0

On 15 November 2018 at 12:25 Elmer van Chastelet commented:

If the diff between those events were in a non-word character or a whitespace, this indeed could result in a shared tab-id.

//escaping of tab id
/(\W|\s)+/.replaceAll("-",s)

On 21 November 2018 at 16:00 Elmer van Chastelet removed tag 1.3.0

On 21 November 2018 at 16:00 Elmer van Chastelet tagged 1.6.0

Log in to post comments