Iād also like to able to filter events by tags. If you use the nav bar tag filter, it works only for the agenda view, not for the calendar and maps view.
But thatās really complaining on a high level. Iāve just used the plugin on my site for the first time and its fantastic!
Edit: even better, if you could also negate tags, for instance āshow me all events except those tagged āpanel-discussionāā. And then the question becomes, can you do that with combinations of multiple tags? And could it also work for calendar subscriptions?
This great plugin has recently been installed over at https://community.coops.tech and I came here to ask that the date format be customisable, so very happy to discover it already is, thanks!
I guess Iāll now just ask our admins to change it!
There is an issue with the MIME type in the webcal generated link that prevents calendar from displaying events when imported into Office 365 calendar (Google calendar displays the events regardless).
Hereās the report from the validator:
Invalid MIME type detected, should be ātext/calendarā (found MIME type ātext/plain; charset=utf-8ā) near line # 1
Reference: RFC 5545 8.1. iCalendar Media Type Registration
On a side note: thank you for the fantastic work on this plugin! Iām eagerly awaiting the feature to add reminders to events, what is the current status on this?
https://community.coops.tech/ now has much clearer dates, thanks! (and Iām now and admin too, so can tweak further if I so choose! )
2 Mi Piace
csmu
(Keith John Hutchison - Ceiteach SeĆ”n Mac Ćistin)
475
That explains why Mac OSX Calendar says the format is invalid
Problem! Found 1 warning
Warnings
Invalid MIME type detected, should be 'text/calendar' (found MIME type 'text/html') near line # 1
Reference: RFC 5545 8.1. iCalendar Media Type Registration
Problem! Found 2 errors
Errors
This is not an iCalendar file or URL near line # 1
Reference: RFC 5545 3.4. iCalendar Object
Missing VCALENDAR object near line # 1
Reference: RFC 5545 3.4 iCalendar Object
Permalink: https://icalendar.org/validator.html?url=http://discourse.bd2l.com.au/c/cottage-singers/cs-concerts/l/calendar.ics?time_zone=Australia/Adelaide
Permalinks are available when validating by URL. You can use a permalink to send a link of the validation results page using e-mail or web posting.
JSON Permalink: https://icalendar.org/validator.html?url=http://discourse.bd2l.com.au/c/cottage-singers/cs-concerts/l/calendar.ics?time_zone=Australia/Adelaide&json=1
The JSON permalink formats the validation results in JSON format, which can be used by other programs for further analysis.
Would you be so kind and submit the bug report for me?
I tried to register on the Sandbox but I couldnātāI never received the confirmation e-mail (it is not in spam folder either), even after multiple retries. Could you check the SMTP logs on your side?
Sorry about that @md-misko, I think this was a case of Outlook not behaving well with certain email services - Iāll check with angus but Iām not sure what the long term solution is. (Seen mentions of this pop up around meta every once in a while).
I validated your account manually so you should be able to log in and submit the report - let me know if you still run into any issues.
Is the bellow error related to this plugin? (also posted here)
a user created a topic by copy pasting some content from a facebook page; this has crashed the topic iteslf, the category and his activities page. (the rest of the topics and categories of the site remained accessible)
I managed to destroy the topic from the console and everything went back to normal for the user and category.
Is this error related to the mentioned plugin ādiscourse-eventsā?
here follows the errors: info:
NoMethodError (undefined method `nonzero?' for [1564826442, 1564826442]:Array)
/var/www/discourse/plugins/discourse-events/plugin.rb:155:in `has_event?'
Questa patch sembra funzionare! Possiamo dire che la differenza tra avere o meno questa patch per noi ha significato avere un sito rotto o uno (apparentemente) pienamente funzionante.
Questi erano gli effetti del bug:
Discourse non veniva renderizzato per gli utenti anonimi oltre lāintestazione (sito totalmente inutilizzabile).
Per gli utenti registrati, probabilmente i contenuti non in cache (ad esempio le liste āUltimeā) non venivano visualizzati, mentre il resto era un terno al lotto.
Stranamente, su tre amministratori, due hanno perso completamente lāaccesso allāinterfaccia web, mentre il terzo (io) ho ancora potuto accedere allāinterfaccia di amministrazione e creare un backup prima della ricostruzione.
In altre parole: qualsiasi sia il bug, puĆ² diventare grave e bloccare il sito.
Ieri mattina abbiamo aggiornato Discourse e il bug ĆØ apparso alcune ore dopo.
Nota che, se sei stato colpito da questo bug, anche dopo lāaggiornamento potresti ancora riscontrare un problema con lāelenco dei topic āAgendaā (il resto delle funzionalitĆ non ĆØ influenzato da questo specifico problema). Ho creato una PR su Discourse per risolvere questo problema secondario.
