Thread

I am working on a site for an small cinema. They have one screen, and play movies from a variety of genres (which I have used categories for), in general they have 3 performances per day.

A typical scenario is that a their main movie will play for two to three weeks except on Wednesdays, when they have a ‘Popcorn Flick’ for one of the evening performances, and a Sunday, when they play a ‘classic’.

I am looking for a method of linking films -> show times -> dates without there being a discrete entry for each showing.

As far as I can tell Repeet doesn’t allow for multiple entries on the same date so I don’t think I can use that, and I know that Playa can handle multiple relationships, but I can’t figure out whether I need to have all of them (films, show times and dates) as separate weblogs. It seems wrong to have a ‘Date’ weblog, and possibly wrong to have a ‘show times’ weblog???

Any ideas?

Thanks in advance,

Adam

did you get some solution for this issue ?
I have similar case with theatre, where the events can be repeating on a certain dates and times ....
just wondering which is the best solution for displaying all moth program for example

Count me in on this solution and I will work on it in the meantime.

I was thinking about using Repeet, but reading this forum I realized that there might be a lot of problems with displaying and dynamically sorting the event table

We ended up staying simple.

Created a weblog for the movies and one for show times, then created a relationship from show times to movies (the show times weblog has only one custom field, which is the relationship to movie).

After entering the movie the client can then add as many show times as needed for it. The show times are named by date and time of performance like so; ‘Show 20090512 1930’ (Show <- titles cannot start with a number, YYYYMMDD HHMM) to keep them in order naturally (by date then time). The client can load them at any time but must manipulate the Date fields to have the ‘Entry Date’ at the exact time and date that the movie starts, then the ‘Expiration Date’ a minute after (to make sure the show listing disappears after the start of the movie).

The calendar can then be used almost standard out of the box and a little trickery is needed for the ‘Coming Soon’ section as shown.

{if '{entry_date format="%U"}' >= '{current_time format="%U"}'} {!-- This gets future entries only --}

The client can handle it simply and it leaves them the ability to handpick show times and repeats etc.

If you need any more info feel free to DM me. The site isn’t live yet (as we are now going back and forth on designs).

this sounds like a great idea Adam,
the theatre staging is something so similar. So basically after publishing an entry with Title, actors, pictures, video, you can open the weblog “Dates”, which is in relation with the weblog “Staging” and then to put the entry dates for this and next moth.

How this can be sortable on the from table results, however?
I have form with sorting features like: Current month only, chosen day, chosen week, next month only (this is more interesting )

Vladyn,

You would probably have to do something special with the entry_date calculations linked with some reverse_related_entries tags.

We are just using the almost standard calendar code on the site, which is enough for the client.

Best of luck.

Adam

The thing that considering me is that separating a weblog for each Event dates will bring up a huge amount of entry duplicates in the edit panel

There shouldn’t be any duplicates in the Events unless they had two showings happening simultaneously.

Yes there will be a lot of entries, but that’s why it’s having its content managed, don’t forget the Expiration Date, that helps to tidy up what is displayed.

We ended up staying simple.

Created a weblog for the movies and one for show times, then created a relationship from show times to movies (the show times weblog has only one custom field, which is the relationship to movie).

After entering the movie the client can then add as many show times as needed for it. The show times are named by date and time of performance like so; ‘Show 20090512 1930’ (Show <- titles cannot start with a number, YYYYMMDD HHMM) to keep them in order naturally (by date then time). The client can load them at any time but must manipulate the Date fields to have the ‘Entry Date’ at the exact time and date that the movie starts, then the ‘Expiration Date’ a minute after (to make sure the show listing disappears after the start of the movie).

The calendar can then be used almost standard out of the box and a little trickery is needed for the ‘Coming Soon’ section as shown.

{if '{entry_date format="%U"}' >= '{current_time format="%U"}'} {!-- This gets future entries only --}

The client can handle it simply and it leaves them the ability to handpick show times and repeats etc.

If you need any more info feel free to DM me. The site isn’t live yet (as we are now going back and forth on designs).

hey Adam,
can you please post some code from the table with programme - Movie title and the {realted show entries}
thanks a   lot