Project

General

Profile

Actions

Bug #17587

closed

Recurring event issues

Added by Raymond Hoh almost 2 years ago. Updated 3 months ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Category name:
Events
Target version:
Start date:
2023-01-30
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

I came across a few bugs while testing events:

  • Dates for recurring events are not displayed correctly in list view. The first event date is shown instead of the actual recurring event's date.
  • Recurring date info is missing on single event pages. For a point of reference, a recurring event page looks like this in Event Organiser: http://demo.wp-event-organiser.com/events/event/fortnightly-event/. Do we want to port over the "This event is running from X until Y. It is next occurring on Z" line or the "Upcoming Dates" section? (Also, venue map is missing on our single event page as well.)

Will add a fix for the former, but could use some feedback on the latter.


Files

Screenshot_2023-01-31_11-19-36.png (80.8 KB) Screenshot_2023-01-31_11-19-36.png Boone Gorges, 2023-01-31 12:21 PM
2023-02-06_174402.png (94.3 KB) 2023-02-06_174402.png Raymond Hoh, 2023-02-06 08:51 PM
Events (logged In) Calendar view.jpg (403 KB) Events (logged In) Calendar view.jpg Sara Cannon, 2023-02-08 10:50 AM
Events (logged In) List view.jpg (912 KB) Events (logged In) List view.jpg Sara Cannon, 2023-02-08 10:50 AM
Events (logged In) Single Event.jpg (646 KB) Events (logged In) Single Event.jpg Sara Cannon, 2023-02-08 10:50 AM
Actions #1

Updated by Raymond Hoh almost 2 years ago

Dates for recurring events are not displayed correctly in list view. The first event date is shown instead of the actual recurring event's date.

This one is fixed in https://github.com/cuny-academic-commons/cac/commit/e9134a4bd6573bb4d45178a3a6b99cfbcfdc617d and is available for testing on cdev.

Actions #2

Updated by Boone Gorges almost 2 years ago

Ray, thanks for flagging the issue with recurring events.

The attached screenshot shows what it'd look like with the EO language ported over. I made it a bit smaller and put it in italics because the language is fairly wordy. What do others think?

I'll open a separate issue to discuss venue maps, as that change might require some more significant design changes.

Actions #3

Updated by Raymond Hoh almost 2 years ago

The attached screenshot shows what it'd look like with the EO language ported over. I made it a bit smaller and put it in italics because the language is fairly wordy. What do others think?

I've opted to make the language even more wordy :)

I think it's important to know how often the recurring event is repeating, especially when clicking on a future recurring event from the "All Upcoming" page. This is available for testing on cdev. (I've also attached a screenshot for those unable to access cdev: https://redmine.gc.cuny.edu/attachments/24562) Open to other ideas on how to re-word or display this recurring info.

Actions #6

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 2.1.1 to 2.1.2
Actions #7

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 2.1.2 to 2.1.3
Actions #8

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.3 to 2.1.4
Actions #9

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.4 to 2.1.5
Actions #10

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.5 to 2.1.6
Actions #11

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.6 to 2.1.7
Actions #12

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.7 to 2.1.8
Actions #13

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.8 to 2.1.9
Actions #14

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.9 to 2.1.10
Actions #15

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.10 to 2.1.11
Actions #16

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.11 to 2.1.12
Actions #17

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.12 to 2.1.13
Actions #18

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.1.13 to 2.1.14
Actions #19

Updated by Boone Gorges about 1 year ago

  • Target version changed from 2.1.14 to 2.1.15
Actions #20

Updated by Boone Gorges about 1 year ago

  • Target version changed from 2.1.15 to 2.1.16
Actions #21

Updated by Boone Gorges about 1 year ago

  • Target version changed from 2.1.16 to 2.2.1
Actions #22

Updated by Boone Gorges about 1 year ago

  • Target version changed from 2.2.1 to 2.2.2
Actions #23

Updated by Boone Gorges about 1 year ago

  • Target version changed from 2.2.2 to 2.2.3
Actions #24

Updated by Boone Gorges about 1 year ago

  • Target version changed from 2.2.3 to 2.2.4
Actions #25

Updated by Boone Gorges 12 months ago

  • Target version changed from 2.2.4 to 2.2.5
Actions #26

Updated by Boone Gorges 11 months ago

  • Target version changed from 2.2.5 to 2.2.6
Actions #27

Updated by Boone Gorges 11 months ago

  • Target version changed from 2.2.6 to 2.3.1
Actions #28

Updated by Boone Gorges 11 months ago

  • Target version changed from 2.3.1 to 2.3.2
Actions #29

Updated by Boone Gorges 10 months ago

  • Target version changed from 2.3.2 to 2.3.3
Actions #30

Updated by Boone Gorges 9 months ago

  • Target version changed from 2.3.3 to 2.3.4
Actions #31

Updated by Boone Gorges 9 months ago

  • Target version changed from 2.3.4 to 2.3.5
Actions #32

Updated by Boone Gorges 8 months ago

  • Target version changed from 2.3.5 to 2.3.6
Actions #33

Updated by Boone Gorges 8 months ago

  • Target version changed from 2.3.6 to 2.3.7
Actions #34

Updated by Boone Gorges 7 months ago

  • Target version changed from 2.3.7 to 2.3.8
Actions #35

Updated by Boone Gorges 6 months ago

  • Target version changed from 2.3.8 to 589
Actions #36

Updated by Boone Gorges 6 months ago

  • Target version changed from 589 to 2.4.1
Actions #37

Updated by Colin McDonald 6 months ago

Mentioned this on the dev call earlier as a possible small summer project to complete some Events directory upgrades that are already relatively far along (see #17712) as well. Let's discuss how much work is still needed here, or in next week's call.

Actions #38

Updated by Boone Gorges 5 months ago

  • Target version changed from 2.4.1 to 2.4.2
Actions #39

Updated by Boone Gorges 5 months ago

  • Target version changed from 2.4.2 to 2.4.3
Actions #40

Updated by Boone Gorges 4 months ago

  • Target version changed from 2.4.3 to 2.4.4
Actions #41

Updated by Boone Gorges 4 months ago

  • Target version changed from 2.4.4 to 2.4.5
Actions #42

Updated by Raymond Hoh 3 months ago

  • Status changed from New to Staged for Production Release

Most of this was completed back in the 2.1.1 milestone. See https://github.com/cuny-academic-commons/cac/commit/429b246154ef0064ae535423186c55bd296bb3a2 .

I've just updated some styles to better match the design comps in https://github.com/cuny-academic-commons/cac/commit/94ef30c7f31af969a45b54fdfc341ed5fefcce40 .

Actions #43

Updated by Boone Gorges 3 months ago

  • Status changed from Staged for Production Release to Resolved
Actions

Also available in: Atom PDF