From what I can see, this fork is just a copy of angusmcleod/discourse-events with no commits that update it for the latest Discourse changes (including Ember 5 support). It doesn’t seem to address the deprecated code paths causing the current errors.
From community posts and testing, here’s what I understand:
The original Events Plugin is not currently compatible with Discourse’s Ember 5 upgrade.
Users have reported issues with event-rsvp and add-event modals, causing breakages.
A temporary workaround is to force Discourse to use Ember 3 by adding EMBER_VERSION=3 in app.yml — but this is not a long-term fix and may cause future breakage.
This situation has persisted into early 2025 without an official update from the plugin maintainers.
Questions:
Can anyone confirm if my understanding above is accurate?
Has anyone successfully run the awesome-it/discourse-events fork on the latest Discourse without the Ember 3 fallback?
Is there an actively maintained fork or alternative plugin that replicates the Events Plugin’s features?
Any confirmation or correction would be appreciated so I can plan whether to:
Stick with the Pavilion plugin and use Ember 3 fallback
@staff could I request a small moderation update to the OP of this topic?
The plugin here (“Discourse Events”) is not Pavilion-maintained and it currently contains
deprecated Ember code (this.router). This has been confirmed in this support thread,
where the recommendation was to disable the plugin if installed.
Right now the OP doesn’t make that clear, which risks confusion with the official Discourse Calendar / Event plugin. Would you consider adding a short note at the top
(e.g. “ This plugin is unmaintained and contains deprecated code. Not to be confused with the official discourse-calendar plugin”)?
Thanks angus - really glad you’ve kept this functionality going. I know you’d stepped back from supporting discourse-events professionally, so it means a lot that you still took the time to push a fix here.
I’ve tested the commit and it solved the router error on my site.
I also saw what Lhc_fl pointed out earlier about the event-label helper using deprecated code - that’s still something to clean up in future. And as davidtaylor noted, those warnings (associated with deprecated APIs) shouldn’t break a site by themselves, so it makes sense that your router fix was the piece needed to get things working again.
Appreciate you keeping this plugin alive on current Discourse.
I have inherited a hosted discourse instance and would like to move to the native Discourse Calendar and Events plugin, mainly because of the warnings I am getting about deprecated features and because I can manually upload events to our site.
However when I remove or disable the plugin the category that was linked to the plugin no longer loads and I get a handy error
That sucks! It looks like it is all a bit gummed up, eh.
My guess is that it would take a fix of the plugin to unpick that. And that would take significant time / energy (i.e. money) to do. Of note, there is active work going into it right now, so you might be in luck if you update your site:
Perhaps you could move the topics out of that category and then delete it. You should (hopefully) still be able to navigate to it via /c/football-1/saints-fixtures/34/l/latest to do it via the UI, or you could maybe export / re-import them via the rails console if needed.
This plugin is unmaintained and contains deprecated code. Not to be confused with the official discourse-calendar plugin”)?
