Timo Brembeck

> Another option would be to simply remove the date from the slug, before we retrieve the event from DB. Does it sound okay? Yes, I think removing the date...

> If I understand correctly, we must showing an error message if the slug already exists. An error is maybe a bit much (since the page was successfully saved), but...

For more context information about this issue, see #1646

This is probably also related to #1518 and ultimately https://github.com/django-treebeard/django-treebeard/issues/53.

This is already possible. When adding a link, there is a field "Link to existing content" and when the user searches for existing content, the suggestions contain pages, events and...

Actually, I think it's easier to use if the content type doesn't have to be selected... However, maybe it would be good to point out which type the current suggestion...

@django-treebeard Anyone willing to review this? Thanks a lot in advance!

I think the problem you're experiencing has to do with the way nested sets are defined - since adding a child in the middle of your tree affects the `rgt`...

I think the workaround would be to call e.g. `refresh_from_db()` after each insertion took place: ``` person1.add_child(instance=self.person2) person1.refresh_from_db() person1.add_child(instance=self.person3) person1.refresh_from_db() person1.add_child(instance=self.person4) person1.refresh_from_db() person1.add_child(instance=self.person5) person1.refresh_from_db() ```

This seems to be the related issue at Google: https://issuetracker.google.com/issues/36761530 Since there have been no real updates for 6 years now, I assume this is labeled as "wontfix" internally or...