[EventCalendar] archive listing problems

[Alex Tingle]

Hi Kris,

On 24 Oct 2006, at 09:36, Kris Rhoades wrote:

>> *	Is there a way to use multiple categories then after the event date
>> a category is erased, deleted, or otherwise changed?
>
>> Once more in English? ;-)
>
> When I make the post I want to be able to select categories: "upcoming
> events and past events"
> When the event date comes I would like the post to only appear in "past
> events" and not in "upcoming events"
> If you look at my "past events" page
> (http://thewellministries.org/schedule/?cat=2) you will see that some 
> of the
> upcoming events show up because I set both categories when I made the
> original post. I don't want to show upcoming events in this category 
> list
> but only past events.
> I'm going to try your "before today" and "after today" to see if that 
> helps.
> But maybe you could include in your files that the default "event" 
> category
> is an "after today" list only and all others are "before today".

That's not the case.

If you have selected "Keep Events Separate", then the event category 
listing is equivalent to "ec3_after=today" (and event posts are kept 
off the front page).

Otherwise, the plugin doesn't affect the posts listed or their order.


>> *	Is there a way to format the event date differently, ie. side by
>> side instead of top and bottom?
>
>> "Top and Bottom"? I really don't know what you mean.
>
> Now the date is listed as such: (top and bottom)
>      DATE_OF_EVENT
>      TIME_OF_EVENT
>
> I would like to change it to: (side by side)
>      DATE_OF_EVENT     TIME_OF_EVENT

Ah, OK. If you only ever have one time for each event, then you can 
just call ec3_the_schedule() in your template with different 
parameters: 
	http://wpcal.firetree.net/template-functions/ec3_get_schedule

If you have more complicated events. then you would have to write your 
own version of ec3_get_schedule(). It shouldn't be too hard.

I would like to make the formatting of this in-post data more flexible. 
I thought about it for a couple of hours last weekend, and decided it's 
too much work for the next release. I'll have a stab at improving it 
for v3.2.

-Alex