Thanks for this awesome plugin! Is there a way to use the iCal link of a private (member only) forum?
@Globulle Thanks for trying it out ![]()
Not at this time. That will require adding and validating an api key in the iCal feed url.
Is it difficult and/or planned? That would be a powerful tool for my community. Thanks again.
It would be a good feature, but tbh it hasnât been on my radar. I can slot it in about 2-3 months time.
If you need it earlier than that, or with more certainty, you can hire me to do it.
Or if you can gather a few other people who need it, I can bump it up the timetable.
Thank you <3
I think the UX can be improved a little on the desktop, look at this drop down menu.
vs this one

I see itâs not fully localized to portuguese. I can help you translate everything that is not translated yet. How can I help?
What happens if I uninstall your plugin, but have posts with this active?
Is there a way to set the timer input box to 24 hours cycle? Example: 23:00 instead of 11:00 PMâŠthe latter is more used in certain languages.
Hey thanks again for your interest, however youâre using the Discourse Local Dates plugin there, not the Events Plugin. You can test out the Events Plugin on my sandbox: https://discourse.angusmcleod.com.au/c/events.
You made me confused for a moment, but Iâm sure Iâm using your plugin? I mean this is all I have in my .yml
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-sitemap.git
- git clone https://github.com/discourse/discourse-solved.git
- git clone https://github.com/angusmcleod/discourse-locations.git
- git clone https://github.com/angusmcleod/discourse-events.git
The Local Dates plugin is included in Discourse by default. The modal in your screenshot is from that plugin. The Events Plugin modal looks like this
Hereâs a guide to the composer UI
I have translated around 97% of this plugin, except for the stuff I donât knowâŠ
Add a link to the site agenda to the hamburger menu.
What is this supposed to mean? I donât know what is a âhamburguer menuâ.
Let me know and I can finish the translation. After you push it, how I can update my plugin and change the language?
âhamburger menuâ is the menu in the top right corner in the forum that looks like three horizontal lines.
It is so called because the three lines are supposed to represent the three layers of a burger - bun, burger, bun.
I donât know if that helps with the translation.
Iâd like to share some thoughts with you guys:
I absolutely love this plugin. 
It solves a lot of issues Iâve previously had by managing lectures and other courses inside Discourse. Discoure is not just great for civil discussions, it also enables me to keep track on knowledge and development cycles. Unfortunately, the events plugin drives me a little bit crazy.
-
There is fear about future updates and dependencies, that wonât might work any longer. It would be so great, if the core dev team of Discourse would integrate this plugin by default. If the day will come and the plugin stops working, I possibly canât access to the topics any longer. Date and time information, that are extremely relevant, might be no longer available. Especially, if the only workaround to get rid of usability issues, is to disable the plugin.
-
I have a looooot of old events, Iâd like to see (in the right order) into the calendar and agenda. But each edit will highlight the old topic at the categories startpage as new / recent activity. This will be very confusing for others to see, if I bring up topics from 2016 and newer. But how can I disable this?
What do you think guys
Should I stop at the very beginning and keep my old schema of topic names with Date and Name of the event or should I risk a full migration of all events, at least the new ones?
For sure, I can work with manual created TOCs and link each topic/event as I do right know. But I really like to see a more secure, reliable future for this incredible plugin.
There is a built-in action to âreset bump timeâ for each topic edited ![]()
Ed.: itâs built into Discourse core AFAIK:
![]()
Thanks for translating! You can update the events plugin at /admin/upgrade.
I understand the concern, but you canât expect the Discourse team to bring everything into core. There is a fully featured plugin system in Discourse for a reason. I plan to keep supporting this plugin for the foreseeable future.
Thereâs a category setting that allows you to suppress it from the homepage.
Itâs up to you mate
If you have issues, you can post them here and Iâll help you.
Well I have no idea how to translate this for my language in a way people would understand lolâŠ
@angus Iâm happy to help
I just noticed there are some small errors because of the lack of context when translating but now that I see it live, I see that small things can be changed.
That would be like removing a final â.â where it shouldnât be there, but I canât do that anymore in transifex? The option to save changes is greyed out?
I think the quick edit of topic titles, category, tags etc (pencil link next to title) does not bump the topic. This would be another reason @angus to add event details editing there, as Iâve requested previously.
I have this same situation and donât see it as a big deal even if itâs a bit repetitive. I keep the date in the title, in parentheses after the topic title. Example:
hehe. not such a big deal, really, since itâs just an admin setting. You could just call it whatever âmain menuâ is in your language.
Na verdade, Ă© um pouco confuso que a data (e, se definida, tambĂ©m a hora) apareça nos nomes dos tĂtulos dos tĂłpicos, mas, ao trabalhar dentro do tĂłpico, o termo curto desaparece e se torna minimalista.
Existem alguns eventos, como séries de cursos, que não alteram o nome em nada, exceto pela data e pela iteração.
Uma solução ideal para mim e para outros, com (dezenas de) datas existentes jĂĄ no tĂtulo do tĂłpico, seria algum tipo de mĂ©todo de detecção automĂĄtica. Essa funcionalidade deveria manter o valor da data anterior no tĂtulo do tĂłpico e adicionĂĄ-lo automaticamente como data do evento (sem hora especĂfica, 00:00).
Acredito que isso economizaria muito tempo de alguns de nós, evitando a necessidade de alterar centenas de nomes de tópicos e adicionar manualmente os valores de data (e hora). Além disso, ficaria muito mais confiante quanto à confiabilidade, caso o plugin eventualmente pare de funcionar no futuro. A informação mais importante, a data ao lado do nome do evento, estaria onde deveria estar.
Trying to auto-detect dates folks have entered into titles as raw text is not practical. The permutations of formatting are many and various.
Iâm happy to help you out with specific concerns, but I canât really help with the general concern that the plugin may break one day in some unspecified way.
In a cosmic sense, all things break eventually. All I can say is that I plan to continue supporting this plugin for the foreseeable future.
I find this very helpful. Thanks for creating this. ![]()
As far as I know, there are not so many (most commonly used) permutations âŠ
(YY)YY-MM-DD +
DD-MM-YY(YY) +
(YY)YY-MM-D(D) +
D(D)-MM-YY(YY) +
⊠and the written word of the month between the day and year.
⊠with a dot or â-â as separator. And there are existing validation methods out there.
Iâm glad to hear this. This is very kind and I appreciate this.
Discourse requires itâs own (at least virtual) server and is very powerful by default. Most of the features are way better than previous stand-alone / plugin LAMP solutions, Iâve tried dozens over the years. Some people might call it the âEierlegende Wollmilchsauâ.
For the first time in history weâve got a open source solution, I would bet, this could work at least the next 10 years. Perfect for knowledge base use-cases âŠ
Over the past years, Iâm maintaining my instances in the most reliable way. I guess, most of us experienced broken rebuilds, blank pages and other major issues ⊠at least for a couple of minutes up to several hours. Thatâs way, I prefer official plugins more than other great plugins, like this one. Events is amazing, but I donât like to change all of the topic names to have a unified scheme. All of my topic names follow the scheme âDD.MM.YYYY - Nameâ (sometimes with comma instead of - ).
By the way: There is small usability issue.
Iâve experienced an issue with âlongâ category and subcategory names with the new tabs âcalendarâ and âagendaâ next to it. The topic buttons on the top right corner creating a line break. Especially on mobile devices. Therefore, Iâm also looking for a setting to enable a drop-down menu for both new entries OR by merging both views in one tab. You might know, like the list view of this calender on the top right corner.
What do think? ![]()



