Closed AveshCSingh closed 12 years ago
I'm going to work on this after we're done filtering events on the main page. I'll reuse that code over here.
It might be easier to do this via html + javascript...add css classes to events to designate each type, and then display:hidden, display:block appropriately based on the value of a dropdown.
That was the original plan. We worried that the page might take too long to load as time goes on.
We're planning on keeping events on the moderator page basically forever, right? Then the GET request might have to get 50k lines from the server, causing too much lag.
I'm working on a different solution to this problem for the main page filtering --use CSS classes hidden and visible, but only load a particular time period at a time. I think I'll see if that idea can apply to the moderator page too.
Yes, this makes sense. So maybe only load data within some reasonable time frame...just those events that will be happening from the present time-future? And then have a link for archive to see the past events.
There is no pending. Stuff is approved by default now.
Moderator should choose whether to see approved, declined, or pending events.
I will do this by creating 3 separate views, one for each type of event.