#2218 closed enhancement (fixed)
Meetings: Event repetition options need to be more dynamic
Reported by: | hlashbrooke | Owned by: | SergeyBiryukov |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Make (Get Involved) / P2 | Keywords: | has-patch has-screenshots |
Cc: |
Description
On Make/Meetings, the current options for event repetition allow you to set events to repeat monthly or weekly on a specified date (such as the 2nd of every month), but you can't specify something to repeat on a date like the first Thursday of every month.
The monthly Community Team chat has a schedule exactly like that - it occurs on the first Thursday of every month, which means that it is consistently incorrect on Make/Meetings. For reference, here is the post for that meeting: https://make.wordpress.org/wp-admin/post.php?post=1710&action=edit
I don't know if there are other meetings that follow a similar schedule, but it would be great to have that sort of repetition as an option.
Attachments (7)
Change History (29)
#1
@
8 years ago
- Summary changed from Event repetition options on Make/Meetings need to be more dynamic to Meetings: Event repetition options need to be more dynamic
This ticket was mentioned in Slack in #community-events by hlashbrooke. View the logs.
7 years ago
This ticket was mentioned in Slack in #meta by hlashbrooke. View the logs.
7 years ago
This ticket was mentioned in Slack in #meta-wordcamp by sergey. View the logs.
7 years ago
#6
@
7 years ago
- Keywords has-patch has-screenshots added; needs-patch removed
In 2218.patch:
- Add a
"Week of month""Occurrence in a month" option: 2218.PNG, allowing for a more flexible schedule like the first and third Thursday of every month for the Community Team. Day of week is taken from the Start Date. - Include "Biweekly" option from #3075.
- Remove obsolete JS code for Tab navigation. It causes an error, as the post type does not support text editor.
- Remove unused variables in
::save_meta_boxes()
. - Some coding style and readability fixes.
Props should include @SergeyBiryukov and @ketuchetan for his initial patch on #3075.
cc @coreymckrill
#8
@
7 years ago
Add a "Week of month" option, allowing for a more flexible schedule like the first and third Thursday of every month
Just noticed that "Week of month" is not an accurate label for that. Maybe "Occurence in a month"?
#9
@
7 years ago
2218.2.patch changes the label to "Occurence in a month": 2218.2.PNG. The logic is accurate as is.
#10
follow-up:
↓ 11
@
7 years ago
This is great @SergeyBiryukov! I assume the occurence day will be based on the day of the week that the start date falls on? So if the start date is a Thursday, then the meeting will repeat on the 1st and 3rd Thursdays of each month. If that's the case, then this is spot on for what the goal of this ticket was.
#11
in reply to:
↑ 10
;
follow-up:
↓ 15
@
7 years ago
Replying to hlashbrooke:
I assume the occurence day will be based on the day of the week that the start date falls on?
Yes, that's correct.
#12
@
7 years ago
2218.3.patch fixes a typo: Occurence
→ Occurrence
.
#15
in reply to:
↑ 11
@
7 years ago
Replying to SergeyBiryukov:
Replying to hlashbrooke:
I assume the occurence day will be based on the day of the week that the start date falls on?
Yes, that's correct.
That's perfect then - thanks for working on this!
#16
in reply to:
↑ 13
@
7 years ago
Replying to ocean90:
Does this include a fix for #1657?
2218.4.patch does :) Next date should only be calculated if the start date has already passed, which isn't the case for meetings starting later this week. If the start date is not passed yet, it should be used as is.
#17
@
7 years ago
New summary for 2218.4.patch:
- Add an "Occurrence in a month" option: 2218.3.PNG, allowing for a more flexible schedule like the first and third Thursday of every month for the Community Team. Day of week is taken from the Start Date.
- Include "Biweekly" option from #3075.
- Include a fix for #1657: meetings with a Start Date later on the current week are no longer skipped.
- Remove obsolete JS code for Tab navigation. It causes an error, as the post type does not support text editor.
- Remove unused variables in
::save_meta_boxes()
. - Some coding style and readability fixes.
Props should include @SergeyBiryukov and @ketuchetan for his initial patch on #3075.
Related: #3075