I was successful in setting a View 'calendar-date' for organic groups.

This is what works (month view):

/calendar/ returns all calendar items (filed_date, From) (month view)
/calendar/node/8 returns only node 8's calendars (an organic group)
/calendar/node/4,8 returns node 4's and 8's calendars (organic groups)
/calendar/ical/4,8/2010-08 returns ical for nodes 4 and 8 but only for August 2010
/calendar/ical/4,8 returns ical for node node 4 and 8

What's doesn't work:

* The Add+ link takes one here: /node/add/date?destination=calendar/8/2010-08 which claims to add a date node type for OG 8 but it doesn't have node/8 (OG) checked as an audience. But this node/add/date?gids[]=4 does actually add a calendar event for node/4, but how do I make Add+ do this?

* The ical icon (bottom right) defaults for only the month. How does one add another ical icon next to it that returns the ical for the entire calendar?

* When I click on 2010-08-18 the link takes me here calendar/4/2010-08-12 but that returns Page not found. calendar/2010-08-12 works.


Drupal 6.17
Views 6.x-2.11
Date 6.x-2.4
Organic groups 6.x-2.1

Comments

dawehner’s picture

Project: Views (for Drupal 7) » Calendar
Version: 6.x-2.11 » 6.x-2.x-dev
Issue tags: -calendar, -Organic Groups

When you create a issue in the views issue queue you get the following message

Before submitting an issue to Views, you are responsible for reading and understanding the Views issue submission guidelines. Failure to read and understand this page will result in your issue being marked "won't fix".

So on the guidelines there is the following sentence


Make sure that your issue is a Views issue! Views provides the ability to list data - if your data is provided by a module other than Drupal Core, please enter your issue in that module's issue queue instead. If your problem deals exclusively with fields or filters provided by another module (CCK, Image, VotingAPI are common) please post the issue under the queue for that module first; all modules are responsible for telling Views about their own fields. Issues based on other module's data sent to the Views queue will be punted over to that module's issue queue. It's possible Views IS at fault, but the module maintainers are the best people to make that determination, and they can kick the issue into the Views queue with an explanation of what's wrong if that is the case. If there is a more recent version of Views that is supported, please try that version if at all possible.

So you really think


* The Add+ link takes one here: /node/add/date?destination=calendar/8/2010-08 which claims to add a date node type for OG 8 but it doesn't have node/8 (OG) checked as an audience. But this node/add/date?gids[]=4 does actually add a calendar event for node/4, but how do I make Add+ do this?

is provided by views? I hope not :)

This is often the case that people think it's a view so it's views, but with the same reason you could move every issue to drupal ;)

haisam’s picture

Oops. You are so right. I'll post in the correct area.

dawehner’s picture

No. I already moved the issue.

Todd Zebert’s picture

subscribe

I'm interesting in both display and ical feeds for OG and/or taxonomy. Not sure if it is possible (or even recommended) to mix both these methods for events.

For OG, I'd like to display/feed events for ALL of the user's groups, not just specific ones.

AndyF’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

The D6 branch is no longer supported so we're closing this issue. If you think this issue still exists in D7 you can open a new one, thanks.