After looking at the event code for 4.6, and also the upgrade path, I want to discuss the idea of perhaps creating a simple event node type. I reallize that long term flexinode-like concepts will go into core, but flexinode is not an ideal solution for *simple* event needs -- it's not simple to theme, the upgrade path is horribly complicated, and it (unnecessarily) places a requirement of using flexinode if you want an event that doesn't "use up" a core node type. So, my suggestion is as follows: * create an event.module that is the *real* 4.6 version and duplicates the functionality of the 4.5 events module (i.e. a location field) but ties into the new event code * move Aaron's event API stuff to a module called eventapi.module An alternative would also be to make event + eventapi a bundle: this would mean a single download enables a basic event node type. -- Boris Mann http://www.bryght.com Vancouver 778-896-2747 / San Francisco 415-367-3595 IM boris_mann@jabber.org / SKYPE borismann