Does CiviNode makes nodes out of CiviEvents?

Not yet. Mostly, I'm looking for a customer who will fund the work. I don't think it would be too hard, since the CiviCRM APIs for events are probably getting pretty stable round now.

Subscribing since this is something I would also be interested in. Especially if I can expand the node with additional CCK fields when using it in Drupal. I haven't dug into CiviNode yet, but the comments made it sound like that might be possible for contact nodes currently.

But either way, thanks for the work so far.

This would be great. I am also subscribing.

I'm subscribing also - civinode support for civi-events would be a GREAT feature!

Can anyone think of a work-around?

Subscribing. Who can build this?

Provide an estimate, Digital202 will consider funding something reasonable.

Still searching for a way to turn civievent into a custom node type so it can be displayed as a view. Thought perhaps there was a way to use ICal and at least get the title and time.

I was wondering if anyone had either:
1. created an estimate / spec
2. found a workaround
3. secretly built this and will surprise me :)

S.

Subscribing. Has this moved along at all? Seems like a lot of interest.

We now have 6 people interested in this feature - will people pitch in for it? I'm at a non-profit but we could afford a $150 bounty for this. any other takers?

I will have to check with my boss for an exact amount, but I know we can chip in. Assume at least that much, $150 from me.

I've attached a preliminary version of a module to create Drupal Event nodes when CiviEvent events are created. In addition, it provides a single CCK field for including CiviEvent events in your normal Drupal content.

The module works with Drupal 5.x and CiviCRM 2.x

There are still some problems with it:

- Timezones are wonky
- The CiviCRM event hook is broken, so I can't tell whether an event is being created or edited

I made this a separate module because I wasn't sure of the status of the CiviNode module. Is it going to be updated to work for CiviCRM 2.0? I'd love for this to get integrated into CiviNode.

Subscribing (how I wish Civicrm were better integrated into Drupal).

I've gone for the opposite approach to jgerrish: I'm working on a module that creates a CiviEvent when you create a Drupal node of a certain type.
Will post here when it's ready...

Hi jgerrish,

I am having trouble implementing your module, it seems like the attachment civieventnode-5.x-1.x.tar_.gz contains only the file civieventnode-5.x-1.x.tar_.gz which consists of one page of code.

dose this module require the CIVI node module as well?

-Adam

Here's my module.
You make the nodes in Drupal and the Civi event is created for you. It implements a vocabulary for the different event types from Civi.

This module would be a real lifesaver but I'm not able to get it to work.

Keep getting error messages:

Missing require fields ( title, event type id,start date)
3 event matching input params

Have created the above fields in content, live event but still nothing. Have installed date module. Am at a loss. Any help would be much appreciated. Thanks.

Does it give you a line number for that error?

joachim, what versions of Drupal and CiviCRM does your module work with?

Drupal 5.x and the corresponding CiviCRM.

I've run joachim's module through Deadwood, and here are the results. Note that this will NOT work out of the box, as there are several TODOs that need to be fixed first, including a few mistakes by Deadwood that I've commented as TODOs but not fixed yet. I also have no idea whether this will work with CiviCRM 2.1, which is my current version. I'll begin ironing out the kinks over the next few days.

I'm still a little new to CiviCRM, and have never migrated a Drupal module before, so any tips would be much appreciated

OK, here's an updated version. It works for adding and editing events in Drupal 6.8 / CiviCRM 2.1.4, and I tweaked it a bit to avoid overwriting any changes made to the event through the CiviCRM admin interface. Event deletion hasn't been implemented. And you will have to add a CCK Date field to the "Live Event" content type to handle the event start date. If you call this field anything other than field_event_date, you must update the define() call at the top of the module to indicate the correct field name.

Also included is an Event.tpl.php designed to prevent the user from making changes to the event through CiviCRM that wouldn't get propagated to the Drupal Event node. This requires adding the following to your CSS somewhere:

.structural { display: none; }

The file should be placed in {path-to-civicrm-custom-templates}/CRM/Event/Form/ManageEvent