Views Date range seems to be the perfect module for what I'm trying to achieve but I think I miss something.

The site is for a theatre that has archives that span for many years. These years are split in 2 seasons, Spring and Autumn.

What I'm trying to do is to create a View where 2 arguments would give me the shows for one season, like www.example.com/shows/2009/spring would give me all the shows that happened between January and June 2009. Or else, anything that would allow me to get the shows by season.

Obviously, the node type has a date field. Setting the "year" argument is easy to do without Views Date range but for the time being, let's forget about it.

I created a View with a single argument that splits the year in 2 - january to june and july to december - each with its own label, "spring" and "autumn". This is what I get:

www.example.com/shows/2009/spring: all the shows from 2009
www.example.com/shows/2009: all the shows from 2009
www.example.com/shows/spring: no sorting, all the the shows from all the years
www.example.com/shows/spring/2009: no sorting, all the the shows from all the years

I think that what I miss is how to pass the date range argument in the URI.

Comments

Crell’s picture

Status: Active » Fixed

That's not quite what this module does.

This module provides a *summary* view. That is, if you don't specify a date range it shows you a bulleted list of "Spring 2009", "Winter 2009", etc. options. Each of those options is a link to the date range you specify, eg, "shows/2009-01-01--2009-06-01". That's the format that the date module needs to show that range.

If you want to turn that string into something nicer like shows/2009/spring, your best bet is to simply set a URL alias for that.

yul63’s picture

Thank you !

I missed the right format to pass the values. I'll try to figure out something about the URIs. I'll let you know if I find something useful.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.