mirror of
https://github.com/openSUSE/osem.git
synced 2026-08-15 20:54:03 +00:00
Furrest City's modified version of OSEM
http://osem.io
fae6332c36
The home and splash page render a link to the schedule based purely on the `schedule_public` flag, even when an admin has not yet selected a schedule or scheduled any events. Following that link rendered the schedule view, which then failed inside `_carousel.html.haml` because `@rooms` (and the selected schedule) had no data — a 500 error instead of a graceful response. Treat `schedule_public` as an allowance rather than an unchecked control: introduce `Program#any_published_schedule?` (true only when the flag is on *and* there is at least one event in a selected schedule) and use it to decide whether to render the link from the home and splash pages. The schedule controller now returns 404 when no event has been scheduled, so bookmarked URLs surface as "not found" instead of an internal server error. |
||
|---|---|---|
| .github | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| dist | ||
| doc | ||
| lib | ||
| public | ||
| spec | ||
| vendor | ||
| .codecov.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .haml-lint.yml | ||
| .haml-lint_todo.yml | ||
| .overcommit.yml | ||
| .rubocop.yml | ||
| .rubocop_todo.yml | ||
| .ruby-gemset | ||
| .ruby-version | ||
| CHANGES.md | ||
| CODE_OF_CONDUCT.md | ||
| config.ru | ||
| CONTRIBUTING.md | ||
| docker-compose.override.yml.example | ||
| docker-compose.yml | ||
| docker-compose.yml.production-example | ||
| Dockerfile | ||
| Dockerfile.production | ||
| dotenv.example | ||
| Gemfile | ||
| Gemfile.lock | ||
| Gemfile.next | ||
| Gemfile.next.lock | ||
| INSTALL.md | ||
| LICENSE | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
| SECURITY.md | ||
Open Source Event Manager - osem.io
An event management tool tailored to Free and Open Source Software conferences.
Trial
Check out our demo at https://osem.copyleft.dev
Installation
Please refer to our installation guide.
How to contribute to OSEM
Please refer to our contributing guide.
Contact
GitHub issues are the primary way for communicating about specific proposed changes to this project. If you have other questions feel free chat us up in the #osem channel on libera.chat IRC.