@ChrisBeach I’ll take a look at it first thing tomorrow morning.
If you’re talking about changing the formatting of the time, you can do that via the site settings events event label format
and events event label short format
.
@ChrisBeach I’ll take a look at it first thing tomorrow morning.
If you’re talking about changing the formatting of the time, you can do that via the site settings events event label format
and events event label short format
.
There is something wrong with the button in german translation:
This should be fixed now
@ChrisBeach I’ve nearly finished adding event times to all the relevant emails (the different types of topic notifications and topic invites). It’s on the add_email_support
branch which is currently running on my sandbox.
Injecting custom topic variables into email templates and their plain-text counterparts is non-trivial, so it will take a bit more testing before I merge the feature branch into master. It should be merged sometime tomorrow.
@angus some bugs and feature suggestions after using this plugin for a few weeks now on my site:
crazy idea: how about an event calendar for groups? e.g. messages can be given event info, displayed on the calendar, and subscribed to by members of the group. calendar group page gets a calendar menu item.
Minor bug. Quoted event topic gets a bit of munged looking text prepended to the quoted text. See screenshot. What I’d expect is no event info or something prettier, like an event icon and a short event label.
My agenda here is:
Release email support for events. My work on this was disrupted by travel. I’m putting the finishing touches on this now.
Add a setting to add a hamburger menu item for events (the top menu item can currently be toggled in the top menu setting).
Add site level settings for event visibility and trust controls
Fix the preview display issue.
Do you mean the Add to Calendar button within the topic? hm I’m not sure hiding it on past events is a good idea. Sometimes people like to add past events to their calendar for completeness, or record keeping. Is there another concern here?
Nice idea. I’ll consider it in a bit more depth after I’ve done the above.
All good things - thanks much. When you say “release email support for emails” do you mean “email support for events”?
Yeah, this is what I mean. I dunno about other people, but I have never wanted to add an event in the past to my calendar - maybe worth asking around. In the meantime, I guess it does no harm to display it.
Yup that’s the one
Ok I’ve just merged v1 of event emails.
https://github.com/angusmcleod/discourse-events/commit/c11891b2b1300cb84b0609398db39b22a28e8a9d
For all emails mentioned below:
The event details have been inserted into both the html and the plain text version.
No email translation ‘templates’ have been overridden. i.e. You should still be able to use any custom email templates (there may be conflicts in some custom cases).
The event label takes the format: unicode calendar - start datetime - end datetime - event timezone
Invitations
For both user and non-user invitations:
The event details have been inserted to the topic excerpts below the title
The words “invited you to a discussion” have been changed to “invited you to an event”
Notifications
For every type of user notification email (associated with an event topic):
New Setting
You will need to set a default timezone for events using the new events_default_timezone
site setting (defaults to UTC).
This is necessary because if an event itself does not have a timezone set, there needs to be a fallback on the server as it’s impossible to detect the email recipient’s timezone.
cc @ChrisBeach
Excellent! Thanks for doing this Angus. I’ll let you know how this goes on my forums.
I’ve been assisting a couple of communities who have expressed interest in using events on their Discourse instances.
Today they both rely on Facebook for events because it allows users to RSVP and organisers to assess demand. The recent privacy furore has them desperate to cut ties ASAP.
Are there any plans to add the ability to RSVP to an event?
I guess we’re potentially looking at three elements:
It might also be desirable to have the ability to limit the total number of RSVPs.
Cool!
I guess you could have a poll in the event topic that people can use to RSVP. Not possible I don’t think to limit the number of respondents to polls. Or you can simply ask people to reply to RSVP.
0 voters
Hi Angus,
I haven’t yet seen an email but have got quite a few errors in my logs
Apologies about the unhelpful screenshot but am on mobile and it’s quite difficult to copy and paste the full details:
hmm. I can’t repro this, but as a precautionary measure I’ve reverted master to the previous state until I figure out what’s going on there.
Please “upgrade” discourse-events to go back to the old version.
Thanks @Angus. I’m upgrading as we speak.
FYI I’ve updated too and am not seeing these errors.
@angus - Ah I’ve just delved deeper and found I might be wasting your time here - apologies. These errors began earlier in the week than when I upgraded your plugin.
Yes. After taking a look at @ChrisBeach’s logs, his issue is not Events plugin related.
I’ve re-applied the events emails to master.
https://github.com/angusmcleod/discourse-events/commit/7a84370681af1b164c0b2eb368ed30bd7faf38f0
I understand there may be concerns about emails not working properly with this change.
This plugin has been subject to testing in the context of the tests_passed
branch of Discourse for some time. I’ve updated those tests so that now every commit will be tested against all of the core Discourse rspec tests, including the all the core email tests.
An instance with this plugin, with the email changes included, passes all core rspec tests.
You can check the CI status of this repo here: Travis CI - Test and Deploy Your Code with Confidence
I’m greatly enjoying the calendar and am already finding it useful. Really nice job, @angus!
Sorry to harp on about issues I’ve already raised above, but wanted to point out again that long titles are getting cut off, making events hard to read. Maybe others here have ideas on how this might be improved. Some ideas: