An application for keeping dates and events.
Mar 29 2019
Mar 28 2019
Mar 27 2019
Feb 12 2018
Is there someone working on this feature?
Dec 21 2017
The apparent lack of support for scheduling in UTC in much more mature calendar software (Google Calendar / Calendar.app) further suggests that this is not an important feature for most users.
Nov 29 2017
Nov 28 2017
@epriestley what do you think of creating another column in the calendar_eventinvitee table, something like a bool futureStatus so that when we get a list of invitees back, we can check for that flag. I think this would mean a lot of date comparisons (seems inefficient), and I'm not quite sure when to populate event stubs. For example, if the futureStatus flag is set to true for instance 10, and there are stubs for instances 15 and 20, when would 15 and 20 get converted to have the updated status?
Aug 31 2017
@mna Please follow our bug reporting guidelines if you feel you've encountered a bug. This task is several years old and not relevant.
Hi everyone, when I open the datepicker (e.g. via https://secure.phabricator.com/calendar/event/edit/form/default/ ) today (it is August 31st), then it defaults to today (August 31st).
Aug 16 2017
- recurring tasks
- start dates for tasks
The latter is basically what your example is about, right? Because if I have just renewed the SSL certificate then a new task is created (due date being in one year), but it should not possible to start that right away, as it's not necessary. You would use a start date as well, wouldn't you?
Aug 6 2017
I can confirm this.
Jul 27 2017
This almost certainly has nothing to do with being invited via a project. I'm just going to merge this into T10448, which will moot it.
Jul 13 2017
I've seen complaints about this on phabricator.wikimedia.org as well, so I can confirm that this is an issue.
Jul 11 2017
Hm, this screenshot made me dig a bit into the whole thing, so here is what I've found:
First, my date format is different because of my settings:
Why does your date format look different than ours? Is that a local modification or do we support this somewhere I'm not aware of.
Merging over so there is one thread on this topic. We're happy to reopen if you have new reproduction steps we can follow or if you can verify on a Phacility test instance.
I can't reproduce this (again)
Here's the proof: F5042439
Jul 10 2017
Jul 9 2017
Jun 30 2017
I think it's probably reasonable for us to warn about RSVP'ing to an event which has already ended. I'd guess this is usually a mistake, and in cases where it isn't some kind of weird off-label workflow is taking place and the warning is probably fine.
Jun 29 2017
Jun 13 2017
Should not, but looks like there are. I updated to master now, and it works now.
I used the current version, but there should be no meaningful changes to this behavior between your version and HEAD.
That's weird since I exactly did the same with my version from above. Did you used the current or my version? Or should I update and try if I can reproduce it at the master?
I can't reproduce this. Here's what I did:
Example 1: You can't create an event from day 1 0:00 till day 1 23:59
Version infos are:
phabricator 0d1654446be6de43b2bd12fcc247db0dc1a46464 (Sat, Jun 10) arcanist c04f141ab0231e593a513356b3832a30f9404627 (Fri, Jun 9) phutil 74a1350416eb2df825c2315d6519bee03f77bee9 (Mon, Jun 5)
Jun 12 2017
Jun 11 2017
May 9 2017
May 1 2017
I cancelled and reinstated E1486 to force a cache clear with the new code, which seems to have resolved this in production.
I think we're too conservative about invalidating this cache. To reproduce:
Apr 25 2017
@epriestley, what's weird is, I still have this on my bug install, despite having the latest stable updates. I checked, and the migration definitely ran. Thoughts on how to debug this further?
Apr 18 2017
KDE has some interest in this as our contributors are distributed around the world.
Apr 17 2017
I originally posted this feature suggestion because I needed to put a tradeshow event in the calendar. The tradeshow took place in another time zone, and when I got there I realized that the calendar entry was on the wrong day. I also frequently schedule conference calls with clients and suppliers in other time zones.