Calendar

The same warning occurs one or more times whenever you try to add "Calendar: Start Time" or "Calendar: End Time" to a view's fields; also occurs when trying to add "Event: Start ...." as a filter.

If you add one of those to a view, save it and then try to open that view, you get a lengthy SQL syntax error message.

I am seeing the same thing with the current cvs checkout of the 4.7 branch.

I am doing a complete rewrite of the calendar handling and moving it to a separate module that is not dependent on the event module, since you can put dates of any kind into a calendar. The new module will be at http://www.drupal.org/project/calendar. There is some premilinary code there, but don't use it yet. I have a compete rewrite that will work much better and is much more powerful (you can display a year of mini calendars and a mini calendar block is available, etc etc). I hope to be posting some working code there very soon, and when that is done I will carve this out of event views completely and just use the new module.

I have a mostly functional version of the new calendar module working now at http://drupal.org/project/calendar. It still has a few bugs, so it's not quite ready for a production site, but you can get a pretty good idea of how to use it now.

This is a complete rewrite of the code, so read the readme text for instructions. It's actually much simpler to set up. There's a default view provided that displays node update dates on a calendar.

Currently targeted for Drupal 4.7 I assume?

Yes, but I plan to branch the 4.7 version and update it for 5.0.

I've removed the calendar functions from the latest Event Views modules (both cvs and 4.7). Use the http://www.drupal.org/project/calendar module for those features now, since that module makes them available with no dependency on the Event module. I just created a 4.7 branch for the Calendar module, but it won't be available as a download until the next time the downloads are updated.

KarenS: If you create a 1.0 beta release you can put it out immediately.

cvs tag DRUPAL-4-7--1-0-BETA

Then go and add a release. It should be pretty automatic.

I already did it as a regular release and I'm not sure what happens if I try to change it... I have't really figured out the new release system yet.

From your description, you created a dev release.

You created a release off of DRUPAL-4-7, right? If so, that's the 'dev' release that's updated nightly.

What you then want to do is create an actual release, with a tag.

cvs tag DRUPAL-4-7--1-0-BETA (is what I'd recommend; unless you're comfortable with a 1.0 release).

That tag will be static; you'll never move it, and when people file bugs against that release, you'll always know exactly what code they filed against. When you release again after bug fixes or improvements or what-have-you, you'll then do something like:

cvs tag DRUPAL-4-7--1-1

That'd be for the 1.1 release.

LOL, yes I think I'd still call it BETA. Thanks for the tips. I've added a beta release for 4.7 and I'll work next on trying to get something working in 5.0.