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.

Sign up for GitHub

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

Jump to bottom

get rid of on_website or move to plugin #97

Open
johanvdw opened this issue Feb 22, 2025 · 1 comment
Open

get rid of on_website or move to plugin #97

johanvdw opened this issue Feb 22, 2025 · 1 comment
Labels
pretalx-main Issues that make sure our customizations can run without forking pretalx

Comments

@johanvdw
Copy link
Member

The on_website logic is not present upstream. We should either get rid of it or move it to a plugin, to make sure we can use upstream code without migrations.
@johanvdw johanvdw added the pretalx-main Issues that make sure our customizations can run without forking pretalx label Feb 22, 2025
@johanvdw
Copy link
Member Author

all relevant talks for 2025 have 'on_website' set, so we can ditch the logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pretalx-main Issues that make sure our customizations can run without forking pretalx
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@johanvdw