Hey Manuel ![]()
My question is, how do I find the latest version number of this plugin now?
Or does this concept of version number not exist anymore?
Exactly. Since the code is included in core, there is no separate version number anymore.
Ahhhh, the version number, not the last version⦠@RGJ is right, there is no more version numbers for core plugins.
Couldnāt agree more! Itās an important area of functionality for many communities but this implementation is, sadly, IMO kind of a mess. I hate to say that, Discourse has really been taking some great strides in usability, design, etc. lately. But this is clearly far behind and seems to need a lot of work, if not a complete overhaul.
So⦠I decided to try to make my own more event-focused plugin. Hereās a video demonstrating some of its features after 3 days of vibe coding.
All of this stuff works, though Iām sure there are a lot of bugs still (and definitely a ton of layout, styling, and visual polish to do). My hope is to iterate on it for a week or so, with a good portion of that being bug fix and polish (feature freeze planned for tomorrow), after which I hope to deploy it on my own instance for live use. If things work out maybe Iāll be able to share it later, with the giant caveats around it being entirely vibes. ![]()
Hereās a short list of most of what it does:
- Completely stand-alone events entities, with/without topics or chats (both work)
- Venue and room handling (rooms within venues)
- Room reservation with locations (multiple rooms per location), reservation contention handling, dedicated pages for locations and rooms, hours of operation for rooms, capacity, etc.
- Month, week, day, venue (events per venue), and list views with rich filters across all views
- Rich Event description editor and settings, repeat, All Day events, time zone support, event capacity, room capacity
- Location pages with maps, rooms-at-location list, events-at-location list
- Quick access to full event info from calendar and other views (pop-up details)
- Drag on day/week view to create events + times (auto-filled in new event form)
- Auto-filled event creation info depending on where/how the event is created, e.g. from a Room, that room is auto-filled
- Calendar (ICS) subscriptions at multiple levels (per-calendar, per-location, etc.)
- Permissions system for a variety of controls (who can create rooms/locations vs. events, etc.)
- Drafts and publish/unpublish state for events, locations, rooms (and canceled state for events)
- RSVP, event capacity, etc.
- Events list widget for sidebar, event list in Categories
- Most of this also works in mobile, though thatās still heavily WIP in particular
- Probably other stuff Iām forgetting
Is it too much? Maybe! But I want to see what Iāll find useful before I prune. ![]()
I also hope to have a comprehensive range of settings in the back-end. If I can emulate some of what the existing official Events/Calendar plugin does with e.g. sorting topics by event date, Iāll try to do so.
I find that interesting
.
In my opinion, it would be better to implement a complete event management system with parameters to enable or disable event modules to meet everyoneās needs. Currently, you always have to add different plugins to fulfill a request, so a very comprehensive plugin can only be beneficial for everyone
.
Which AI do you use for coding?
Thatās more or less what I intend. I want to make different functions configurable and enable/disable in settings, within reason. I havenāt designed the plugin as modular from the beginning, perhaps I should have. But the functions are interconnected enough and I didnāt want to have it require its own plugins.
I use both Codex (OpenAI) and Claude (Anthropic, of course), both directly rather than through alternative harnesses/environments like Cursor. I get better use out of my subscription dollars this way, and in general I havenāt found the short-term advantages of other tools to make up for their various downsides. Staying in each respective companyās own native coding tools and ecosystem has served me better and better over time, and I use MCPs and skills to make up the difference (e.g. experimenting with novel memory skills backed by on-disk markdown files, or ygrep for file search, etc.).