Timo Brembeck

@JoeyStk Before trying to implement the export ourselves, I think we should first try to get this up and running: https://django-import-export.readthedocs.io/en/latest/ If it doesn't work out for whatever reason, we...

> Shouldn't stuff like this ideally be implemented in the frontend? That way, they could decide how to display all the relevent poi information and we would only have to...

> Is this issue still relevant or is this already satisfied by our current system? We only have a counter of how many elements are selected, now how many elements...

@dkehne I guess it's not really required, but if we implement an iCal import, it might be a trivial task to implement the export as well. But prio should stay...

It would just be a little bit more convenient and we would have the option to export multiple events at once, or past/future/draft events that are not shown in the...

I cannot reproduce the problem for JPEG files. Since JPEG is essentially the same as JPG, I don't see a reason why it wouldn't work. The example image works for...

@nkclemson Awesome, thanks a lot for your interest in our project! :rocket: Sure, feel free to work on this and ask any questions if something is unclear.

> And we're back to 81,7% 😅 Well, that's on me :innocent: And will be fixed with #2772 hopefully.

maybe @svenseeberg can help?

I think this is just a limitation of Django's [widget implementation](https://github.com/django/django/blob/225d96533a8e05debd402a2bfe566487cc27d95f/django/forms/templates/django/forms/widgets/input.html). The `name` of a widget is a special attribute which is directly inherited from the field name and cannot...