mike - i was wrong, the date argument in the url uses hyphens to demark the datetime variables (i.e., "2010-02-03").
the path for the test View (event_calendar2) is set to "eventcalendar2/%/%" (%'s being arguments that are passed into the view).
the Arguments for the event_calendar2 view (NOTE: this is for the 'Calendar page' display, not the defaults, just in case) are set to;
"Date: Date (node) Content: Date & Time (field_event_start) - From date
Taxonomy: Parent term"
so http://theforest.org.uk/eventcalendar2/ ... 3/workshop
should only display 2 items, but it shows them all and i can't understand where i'm missing a trick.
firstly, in the options for setting an argument to be "Taxonomy: Parent term", it doesn't let one choose from what taxonomy ('Event type' or 'Event location') the term should be from. maybe it's just agnostic and should be able to compute either.
(the difference between "Taxonomy: Parent term" and "Taxonomy: Term" should be moot here - neither taxonomy is set to be hierarchical, and i've tried setting it to both)
if i flip the arguments around ("Taxonomy: Parent term", then "Date: Date (node) Content: Date & Time (field_event_start) - From date") then i get a blank calendar, even when trying to preview with wildcards for both arguments ("all/all")......
but if i override the title of the page in the taxonomy argument options to be "test title - %1, %2", it comes out with "test title - February, 2010, workshop", so it is getting it..
(i tried turning on validation, i.e., so it validates the second argument is an actual taxonomy term, but if it's already getting it but not acting on it then that wouldn't help anyway)
a great overview of Views arguments can be found here