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 âGefĂ€llt mirâ
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?'
Dieser Patch scheint zu funktionieren! Der Unterschied, ob wir diesen Patch haben oder nicht, bedeutete fĂŒr uns, entweder eine defekte Website oder eine (offensichtlich) voll funktionsfĂ€hige Website zu haben.
Dies waren die Auswirkungen des Fehlers:
Discourse wurde fĂŒr anonyme Nutzer nicht ĂŒber die Kopfzeile hinaus gerendert (völlig unbenutzbare Website).
FĂŒr registrierte Nutzer wurden wahrscheinlich nicht zwischengespeicherte Inhalte (z. B. âNeuesteâ-Listen) nicht gerendert, und der Rest war GlĂŒckssache.
Seltsamerweise verloren von drei Administratoren zwei den vollstÀndigen Zugriff auf die Web-OberflÀche, wÀhrend ein dritter (ich) weiterhin auf die Admin-Schnittstelle zugreifen und vor dem Neuaufbau ein Backup erstellen konnte.
Mit anderen Worten: Egal, was der Fehler ist, er kann zu einem schwerwiegenden Problem werden, das die Website lahmlegt.
Gestern Morgen haben wir Discourse aktualisiert, und der Fehler trat einige Stunden spÀter auf.
Beachten Sie, dass Sie, falls Sie von diesem Fehler betroffen waren, auch nach dem Update möglicherweise weiterhin Probleme mit der âAgendaâ-Themenliste haben (der Rest der FunktionalitĂ€t ist von diesem speziellen Problem nicht betroffen). Ich habe einen PR an Discourse eingereicht, um dieses sekundĂ€re Problem zu beheben.
