[EventCalendar] Big Calendar features & suggestions (Was Re: [PATCH 3]...)

[Matthew Middleton]

Your problem must be due to cached javascript or
different versions of different files.  That
ec3_calendar_category_filter element always gets
created, whether there is category filtering or not. 
It simply serves the purpose of holding that variable
for later access.  I looked at
http://longislandna.org/?page_id=4 - and it doesn't
look like the latest patch with category filtering is
even applied.

When I rework the javascript a bit to allow for
multiple calendars, I will change how some of this
works.  For example, the category filter property
should be a property of the calendar <div> element
rather than being in an empty <span> with a fixed ID.


--- firetree_ec3 at spamex.com wrote:

> Matthew, I have not had a chance to look over it
> yet, but I'll bet  
> this is indicative of an issue.
> 
> I noticed that my Web Developer toolbar gave an
> error in the JS script.
> 
> Error: filter_element has no properties
> Source File:
>
http://localhost/~cmarshall/longislandna.org/public_html/
> 
> wp-content/plugins/eventcalendar3/ec3.js
> Line: 70
> 
> The code in question is this:
> 
> // namespace
> function ec3()
> {
>    WindowOnload( function()
>    {
>      /*Matthew: get category filtering set up*/
>      var filter_element = document.getElementById 
> ('ec3_calendar_category_filter');
>      ec3_filter_by_categories =
> filter_element.getAttribute 
> ('ec3filter'); <- Here be problem
> 
> I'll lay odds that, because I didn't declare any
> categories (remember  
> that I just plonked this straight into my original
> install),  
> filter_element is null. You might want to test for
> it.
> 
> _______________________________________________
> Blog: http://wpcal.firetree.net/
> EventCalendar at firetree.net mailing list
> Unsubscribe:
> http://penguin.firetree.net/eventcalendar
>