Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Blank tag in editor schedule (only some devrooms) #72

Open
cosenal opened this issue Dec 10, 2024 · 3 comments
Open

[bug] Blank tag in editor schedule (only some devrooms) #72

cosenal opened this issue Dec 10, 2024 · 3 comments

Comments

@cosenal
Copy link

cosenal commented Dec 10, 2024

I am editing the schedule, and noticed that talks from our track (Quantum Computing) are under a blank tag – see screenshot. Same for another track, which is still empty though.

Screenshot 2024-12-10 at 11 43 36

I asked this on the devroom-managers mailing list and @kopasiak pointed out the following:

I think this can be related to the fact that something is wrong in
pretalx DB/code because when I was exporting submissions using a
script that worked in last year I noticed that some "tracks" are not
json objects as it used to be (i.e. {"en": "Python"}) but are stored
directly as strings aka Python. In case it helps this is a list of
devrooms that are returned as string instead of proper json objects:

Distributions
Low-level AI Engineering and Hacking
Modern Email
Open Source In The European Legislative Landscape and Beyond
Quantum Computing
Radio
Swift
@johanvdw
Copy link
Member

Thanks for the report. This is a bug in the code importing the tracks from the proposals. It is probably solved as soon as the track object is saved once in pretalx. I'll do that for these tracks, but keep the issue open so it does not occur next year (until the import is adjusted).

@johanvdw
Copy link
Member

The issue should no longer occur for this year.

@cosenal
Copy link
Author

cosenal commented Dec 10, 2024

@johanvdw I can confirm the room is now in the dropdown list, thanks! Also good idea on keeping this open to track a more long-term fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants