Drupal 6 upgrade

There is no way to do that until Views 2 is released for Drupal 6.

They're releasing an alpha version of Views2. Looking forward to seeing that!

I'd like to help upgrade this module to D6.

I am still making changes for version 2, but it is getting relatively stable (and I think a number of the remaining issues are Views-related and the D5 fixes for those won't work in D6 anyway), so feel free to start submitting patches against HEAD for this. It doesn't have to be done in one big patch, it can be a series of patches, whatever works to get the job done :)

Thanks!

subscribed.

subscribed - and happy to test this out for you on a non-production d6 site alongside date to see how it works and report back glitches, etc...

I'm currently trying to get CCK for D6 working, in particular the Views 2 integration in that code, then will jump back and work on Date and Calendar.

@karens - thank you! i've been testing out date on d6 (the alpha) and reported two bugs on that specific thread as well...

Views 2 is getting pretty complete now and many of the things Calendar will need are available or should be soon, so I hope start work on the D6 port in the next week or so. Patches are welcome, either to get HEAD upgraded for general D5 to D6 changes or Views 1 to Views 2 changes.

subscribing. (Karen, you are amazing! If only we could clone you so that you could work on all your modules in parallel.)

subscribed

subscribing

subscribing - thanks

subscribing

subscribe

subscribing

subscribing

subscribing - thx

subscribe

subscribe

what is the current status of this?

I just committed the very beginnings of this today. The Calendar args now seem to work when added to a regular view and I have the start of a plugin to display the calendar, but there's a fair bit of work to do and it is definitely not ready to use yet. I'm hoping to get a rough calendar implementation working in the next week or so.

*cough* subscribing

Interested to see the results. Hope we can be of some use.

Looking forward to calendar for D6. Thanks for putting in such an effort!

If anyone's interested, there is a very very rough implementation of the Views 2 calendar now in HEAD. It's alpha quality at best, but there is a default view that uses the node.changed date which provides a page and block version of the calendar that you can use to see how it looks.

Almost anything could change since I'm still trying to figure out the best way to set things up (since there are so many ways you can do it in Views 2), so don't expect anything you do with it to continue working the same way :)

Also, you need the latest Views 2 code since there is a fix in it that is required for this to work -- an re-implementation of 'even empty' that allows you to see a calendar even if there are no results found.

There is now a 6.2 beta release of the Calendar module which corresponds to a new 6.2 beta release of the Date module and the latest Views 2 code. There will be plenty of things to iron out, but please create new issues for items as you find them.

I've been able to take advantage of lots of the new features of Views 2 to simplify the code while adding lots of flexibility. There are templates for the year, month, day, and week displays, and for month, week, and day nodes, so you can easily style them differently.

More info about the new version from the PHP docs:

The Calendar argument has an option to select one or more Views date fields to filter on, automatically adds them to the view, and then filters the view by the value of the selected field(s). This argument can be used on any view, not just calendar views.

Unlike previous versions of the Calendar module, there is just a single argument instead of year, month, and day arguments. The argument value will be YYYY-MM-DD for a day, YYYY-MM for a month, YYYY for a year, and YYYY-W99 for a week. There is a default option to set the argument to the current date when the argument is empty.

A calendar display creates calendar navigation and links to multiple displays for the year, month, day, or week views. The actual displays are created by attaching calendar views that use whatever styles are desired for those pages. The calendar display requires the calendar argument to do its work and uses its own style plugin and template.

Calendar views are attachments to create the year, month, day, and week displays. They can be set to use any style, either a calendar style or any other Views style, like teasers or lists. They can each have their own fields and formatting. They must be attached to the main calendar page or to a calendar block.

A calendar block will create a calendar block for the view results. This block requires the calendar argument to do its work, and uses one of the year, month, day, or week calendar view attachments created above.

By the way, there is a default calendar view provided and I strongly suggest you start with that instead of trying to figure out how to build it from scratch :)

Has anyone successfully imported an ical feed? If so how might one go about doing this on the latest version?

The iCal stuff is not working in the latest version yet, I'm focusing on getting the other parts working.

I got this error:

Fatal error: Call to undefined function calendar_info() in /home/ncdponli/public_html/main/sites/all/modules/calendar/calendar.module on line 417

I tried to install the Calendar module on one site of a multi-site installation.

I guess the beta version is broken, I'm going to try the dev version.

KarenS is saying that the function calendar_info() is a deprecated function and shouldn't be called.

http://drupal.org/node/262078

@jerime - The 6.2 version doesn't even have a line 417, it ends at line 341. That line was fixed on May 24, so you don't have the right version. And you're commenting in a fixed issue, so it is just an accident that I even saw it.

6.x-2.0-beta 2008-May-23 does in fact have a line 417 with the undefined function.

http://drupal.org/project/calendar

The dev version is the fixed version, the one in pink. The one in green is broken.

This issue says it is for "6.x-2.x-dev" not "6.x-2.0-beta" 6.2 beta is not the most recent code, the dev code is and that is fixed.