events

I maintain the signup.module. This module has long struggled with the problem of how to flexibly define what fields are requested and/or required when a user signs up for something. I might have a slick solution, but I'm not sure if CCK can accomplish what I have in mind.

With 5.x CCK, you can assign any fields you want in whatever groups you need to any node type. My module could allow site admins to define the signup/reply form for any given node type as a specific group of arbitrary CCK fields. This field group would not show up on the node edit form. It would be displayed on the node view page itself, so each user could fill-in, submit, and optionally edit their own signup/reply. All fields would automatically be treated as "multiples" in terms of storage, 1 set of each field's values per user who replies, but displayed as single values for any given user viewing the node. When a user replies, the values of any fields in their reply would have to be associated with their identity (uid for auth users, email for anon).

Hi

Could anybody, please, tell if workflow module can be used for doing/checking things periodically and making a state transition basing on the check results?

I really want to make use of the workflow module just released for 5.x but must have the capability of triggering a state change based on some simple field matching criteria.

On Cron Run:
* foreach (condition) { if (condition.true) { execute state change; break; } }

I noticed a small _cron() method that is already doing state transitions based on pure schedule. I guess my main question here is what is the best way to approach this? Is someone working on something similar that I could help out with? Should I just code it up and submit it to the group for review?

I write to suggest a Drupal Dojo lesson on setting up Calendar. It is a useful module and a common need, but isn't an intuitive setup "out of the box."

Hello DC, I am posting this on behalf of my associate Roz. This is a pretty amazing project, and what seems to me to be a pretty solid networking/sales opportunity. I intend to participate, and would love it if you would consider the same.

From Roz:

If you'll be in DC Friday, March 9 and can offer a few hours to help 3 organizations transform their use of technology for organizing, please sign up to be an NOI " guest consultant":

http://flingk.com/ofde8md

The Atlanta Drupal Users Group is heating up! It looks like there will be a sizable crowd in attendance at our first official meeting. The skill sets run the gamut from new users, graphic designers, drupal site publishers, to PHP programmers, so it should lead to a lively and dynamic meeting.

If you plan on attending (or if you can't) please post a comment on this thread so we'll know what to expect.

The meeting is Thursday Feb 22, 2007, from 7:30pm til 9pm, at 5 Seasons North.

In taking a look at the contributed Event module, I noticed that its latest release is 4.7.x-1.x-dev. I also noticed that g.d.o's About page does not list the Event module.

What does g.d.o use for its members to post events? If it does use the Event module, how is that possible since g.d.o runs on 5.x and the Event module is still 4.7.x?

Thanks,
Walt

Hi Guys,

I've been talking to team Lullabot about the possibility of running an Asian Drupal Conference here in Australia, and have received some positive feedback from their team. As a developer here in Australia, I have been keen for myself and the rest of my team to attend the famous Lullabot seminars, but due to distance, costs and Visa restriction post 911 have found the prospect of traveling to America not viable.

After listening to the Podcasts from the last Drupal Conference in Brussels, and the hearing about the number of other Drupal developers in Asia the idea of staging an Asia Drupal Con came to mind.

Here's the low-down on the upcoming.org integration module:

Per the developers description: The upcoming.org module enables you to import events and venues from upcoming.org and display them in a calendar using the event module. Upcoming.org is a website that helps you share and keep track of your events. Synchronizing (using upcoming.org as the master repository) is also supported. Additionally, this module exposes the upcoming.org REST API, making clients written to use it interoperable with Drupal. This makes it possible to build a whole network of websites sharing their events, all using a defined API.