search

csumb / csumb-gatsby

A @gatsbyjs version of the CSUMB website.
https://csumb.edu
MIT License
5 stars 0 forks source link

Events not showing leaving the live feed too early #486

Closed thburns closed 4 years ago

thburns commented 4 years ago

https://csumb.edu/osu/virtual-programming vs https://edit.csumb.edu/osu/virtual-programming

We are looking at the event Monte's music it is happening tomorrow at 11am but it isn't showing up on the live page but it does show up on the edit page.

My guess is the system dates are off by like a day still?

Screen Shot 2020-08-24 at 11 46 30 AM Screen Shot 2020-08-24 at 11 46 24 AM
codywall commented 4 years ago

Looks like it actually is showing up on the live site, but the order is off. Looks like it's because in the 'All dates' field, the date is actually set to August 27. Maybe they changed the date and that didn't correctly update the date field. I'll take a look at it. image

thburns commented 4 years ago

I did delete 8/25 once to test it out. looks like it got published....

On Mon, Aug 24, 2020 at 12:03 PM Cody Wall notifications@github.com wrote:

Looks like it actually is showing up on the live site, but the order is off. Looks like it's because in the 'All dates' field, the date is actually set to August 27. Maybe they changed the date and that didn't correctly update the date field. I'll take a look at it. [image: image] https://user-images.githubusercontent.com/22305037/91085044-b5f04680-e601-11ea-85ca-c62f749508e8.png

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/csumb/csumb-gatsby/issues/486#issuecomment-679308387, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK2UUPE37OWTWUSYC2ZOWH3SCK2ONANCNFSM4QJZVDYA .

-- Tom Burns User Experience Specialist Web Services 831-582-3732 California State University, Monterey Bay

thburns commented 4 years ago

Doesn't look like the cache fixed it.

Are there some rules just for the event feed that need to be adjusted? Cause i know you fixed it for the dashboard and the main event feed but would the event block be different rules too?

-Tom

On Mon, Aug 24, 2020 at 12:04 PM Tom Burns thburns@csumb.edu wrote:

I did delete 8/25 once to test it out. looks like it got published....

On Mon, Aug 24, 2020 at 12:03 PM Cody Wall notifications@github.com wrote:

Looks like it actually is showing up on the live site, but the order is off. Looks like it's because in the 'All dates' field, the date is actually set to August 27. Maybe they changed the date and that didn't correctly update the date field. I'll take a look at it. [image: image] https://user-images.githubusercontent.com/22305037/91085044-b5f04680-e601-11ea-85ca-c62f749508e8.png

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/csumb/csumb-gatsby/issues/486#issuecomment-679308387, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK2UUPE37OWTWUSYC2ZOWH3SCK2ONANCNFSM4QJZVDYA .

-- Tom Burns User Experience Specialist Web Services 831-582-3732 California State University, Monterey Bay

-- Tom Burns User Experience Specialist Web Services 831-582-3732 California State University, Monterey Bay

codywall commented 4 years ago

That's probably it. I'll try to look into it tomorrow, or later this week if I haven't finished this CeDiploma implementation by then.

codywall commented 4 years ago

It looks like the issue was the 8/25 date was added to the bottom of the all dates list, rather than into its place in chronological order. Once the event feed found the date closest to the current date, it used that and stopped looking, so it didn't see the correct date at the bottom of the list. I went into the edit page and fixed it.

It would be nice if Drupal ordered them chronologically for us, but I'm working on a fix to put them in order before the feed is created.

codywall commented 4 years ago

Everything should be working as expected now. A big win was I was able to fix the issue where recurring events were being order by their first date in event feeds rather than the upcoming one. So event feeds should be working much better now.