Ticket #168 (new enhancement)

Opened 3 years ago

Last modified 3 years ago

Front page should show as many of the newest events it can as default

Reported by: jamie Assigned to: somebody
Priority: normal Milestone: WishList
Component: View Version:
Severity: normal Keywords: front page showing events
Cc:

Description

Right now the default is to show the next week. If their are no posts this week, then nothing is displayed. This won't make people want to post next week. And then we never get any posts.

(August 16)Right now there is more then one event in the database, but only one shows up on the cover(my.dsu.ca). Right now, it doesn't even look like anyone looks at it but Phil. And this could even turn off societies/people from visiting even now before we move out of beta.

If we listed all we could, we'd have like 3+ and it'd at least have a reason to keep checking to see if it's cool. So we should view as many as we can up to a number that isn't waaaay too much info on the front, but still shows it is getting more things in it.

Change History

27/08/05 02:17:59 PM changed by cjordan

  • owner changed from somebody to obaltzer.

so the question about how to do this is how to do it efficiently.

Can we run selects iteratively each time incrementing a time constraint by a week and stop when we have exacted 4 or 5 distinct group classes?

Just a quick thought

27/08/05 02:52:00 PM changed by jamie

Hmm.

Well, the problem we are going to have here is that if we have a million posts from one group class, and none for a long time from another, we are either:

a) Going to have a whooole bunch of information on the page by the time we have enough to show it.

or

b) Going to display different time periods for each.

But something along those lines is what we should be doing...

01/09/05 01:04:20 AM changed by obaltzer

  • milestone changed from Release to WishList.

I am setting the default to a 30 day window, which is equivalent to "This Month". Move it to the wishlist for further investigation. An idea would be to take unlimited time an have an option for the selector to retrieve a maximum of 10 events (using LIMIT), which means we get all the events, but never more than 10 for one selector if there are too many events in that infinite time period.

02/09/05 01:29:26 AM changed by obaltzer

  • owner changed from obaltzer to somebody.