Is it possible to make a monthly schedule?

no, it only does weekly schedules. i'd wanted to do a monthly one but never had the time or paying client.

for your second question i'm guessing you need to grant anonymous users view program permissions.

Where is the configuration to allow anonymous users to view programs node type?

These are the only options I have available under Access Control
Station_Program module
administer program - non checked
edit own program conent - non checked
edit program content - non checked

Station_schedule module
Administer schedule - non checked

Any ideas?

I've gone through the drupal administration over and over again and I still can't figure it out.

I've disabled and re-enabled the program and schedule sub modules without any effect.

node module
access content
checked?

views module
access all views
checked?

Yes, both are now checked.

Incidentally, I initially had access all views unchecked, but having it checked has no effecct

To give you a bit more information, I have a role called DJs, and none of the users in this role can access the program nodes either.

I added the following to the ACL for anonymous, authenticated user, DJs roles.
Station_Program module
administer program - checked
edit program content - checked

After I made these ACL changes, anonymous cannot access existing programs.
A user in DJs roles cannot access existing programs and a user in DJ roles has no options under create content to create a new program.

HOWEVER, if I set the following for anonymous, authenticated users, and DJs

Station_schedule module
Administer schedule - checked

Both anonymous and a user in DJs role is able to view the program nodes. This is obviously not what I want since it allows anonymous users edit the schedule.

Any ideas what is wrong and how to fix this?

the access roles for station need to be:

Node
Access Content for anonymous user
edit own program content for DJs
(you can also enable admin schedule (unless you have a program director)

under create content a DJ should see a form to create a program
yoursite.com/node/add/program
if you don't see a form for a new program
try going to:
yousite.com/admin/content/types/add
(i don't think you need to do this-I believe it's done automatically upon install of the station module).

I think the station module automatically creates the user role DJ; (it's been too long) did you create the user role DJ yourself?

I figured out why the programs could not be viewed by non-admins.

See this patch

http://drupal.org/node/319125

Along the lines of the original question, we have one show that alternates every week. I'm assuming out-of-the-box this isn't supported, but curious how much hacking it would take to make it work. Not a huge issue since it's one show out of about 70. I'm going to create a program that covers both shows for now, but sort of thinking ahead.

that's actually the reason, I'm wanting a monthly schedule as well.

We have a few shows that are only once a month. Like the 2nd Friday of the month from 10-12PM, etc.

Another thing that I can think of that would be a big bonus (and maybe this is already possible) is to clone a schedule so that we don't have to go in an re-create the shows that do stay the same every week... we only have to modify the odd shows that are not weekly.

John Button is Webmaster at kvmr.org ... and we've got over 100 broadcasters sharing the air waves w/ a wide range of schedule rotations.. schedule examples like 2nd & 3rd Thursdays at Noon... Alternate Mondays at 9am... as well as the Every Friday at 2pm.

It appears that the current state of the Station module is unable to handle these sorts of schedules rotations...?
Is this the case and if so ... is there work in progress on these issues?

I've been waiting and watching and hoping for the best ... with the Radio Engage project undertaken by Quiddities Dev, Inc. under a grant by the Knight News Foundation, but from I can gather, their effort may not address this schedule rotation question.

I've got a dear friend and drupal developer that's working on this for kvmr .... a radio schedule module that will handle these types of rotations, associated the program w/ a broadcaster and be able to prepare a schedule into the future. The program schedule database will be able to provide id tags for archived audio that will be made available as an archive for a set period (2-weeks or less due to the DMCA).

A slowly developing project due to limited time and an excess of other work that I'm hoping will become a pretty good way that a radio station can keep track of programs, the broadcast schedule, the audio and so on ... the eventual goal is an overall radio station information management app that we can release to community broadcasters.

I really need this feature and have built my station around Drupal. I'm willing to sponsor development of a more robust scheduling system for the station module as I've spoken to you directly about Drewish.

I already use Centova Cast (http://www.centova.com) on the backend for times when we don't have a live DJ. This is highly recommended and working perfectly. You can schedule jingles, schedule types of music during certain period of times, and randomly rotate songs within a playlist during a certain period of time, etc.

But that has nothing to do with what shows up in my Drupal front end site.

My station will have many live DJs all coming from different geographic locations. However, these DJs are not once a week. Some of them are once a month, or every other month, or the 2nd and 4th Tuesday at Noon like John Button mentions above. Putting up a schedule with the station module is a nightmare in my situation.

I need a show schedule system to display what is playing or what will be playing next, or what will be playing next week.

I can rely on my DJs to play their shows on time, and rely on Centova Cast to fallback to pre-recorded random/scheduled playlists on the backend.

What I need is something for the front-end.

As I said, I'm ready to contribute financially to develop of this. I've already spent so much time building the site around Drupal, that I really need to stick with it rather than building something totally from scratch.