Provide simple "event" node type.

+1!!!

I see no reason not to include a basic event type. Ideally, it would actually have an (optional) location field, making for a very easy transition from 4.5, and not requiring flexinode.

Jose: we'll test this and give some more feedback.

The module attached was the PHP source (that is, it was a the output of a highlight_file() function). I'm attaching it here as text.

Unless everything with .module turns into the HTML version of the PHP, as did mine. Copy & paste I guess. :P

+1 from me.

I don't see the point in the flexinode-system for simple calendars. There would be either just one node type or too many because there are many different events.

Is there any way to get rid of the "limit view to events of this type" links in events? I could use css to hide them, but text browsers will still show them then.

Here is an updated version of our basicevent module we are shipping with bryght.

The basic premise behind this module, is that it creates an 'event' type that will automatically use the event api, and it includes a location field which is stored using the db schema of the location module. You don't need to have the location module enabled for the location field to work, as it will use the location module only if it is availble.

This is the upgrade script.

    $events = db_query("SELECT * FROM {event} e LEFT JOIN {node} n ON n.nid = e.nid");
    while($event = db_fetch_object($events)) {
      db_query("INSERT INTO {location} (oid, type, name) VALUES (%d, 'node', '%s')", $event->nid, $event->location);
    }

    db_query("ALTER TABLE {event} ADD timezone INT(10) NOT NULL default '0'");
    db_query("ALTER TABLE {event} CHANGE start event_start INTEGER");
    db_query("ALTER TABLE {event} ADD KEY event_start (event_start)");
    db_query("ALTER TABLE {event} ADD event_end INT(10) UNSIGNED NOT NULL default '0'");

    // Assume events end when they begin.
    db_query("UPDATE {event} SET event_end = event_start");

   // maybe automatically enable the module here.

alas. i spoke to soon.

I've made the module use the event classes when outputting the location, so that it looks like part of the event output.

Kieran/Gerhard -- this module has the following benefits:
* very easy to upgrade from event 4.5 to, including location field (that is default with 4.5)
* implements an "event" node type out of the box
* is forward compatible with location module -- users can upgrade from 4.5 which brings in all their bare "location" field items, enable location.module, and get full geolocation fields

Ideally, would like this included with event 4.6/4.7 download.

Here is a version of the basic event module that does not have extra SQL in it.

I think this ought to be included with the event module as standard.

Flexinode uses a lot of memory - and is *not* an option for people limited to 8MB PHP memory by their hosts.

Kind Regards,
Lennart Kiil

Lennart: I'd like to include one of these modules but would appreciate if somebody not involved with any of them could evaluate them.

I think this is vital to have working 'out of the box' and also good to use as a framework for building your custom event definitions.

I'm messing with it a bit, but I have to ask that you either include a 'location.mysql' table definition, or find a way to avoid using the database at all for that field. I went to try out the location module, and it was way too heavyweight for my needs.
But what and where is this alternate 'location' table that this tries to use?
I looked at earlier CVS versions and couldn't find it there either.

So, all is not as easy as it should be. Which was the point, no?

But thumbs up for providing it anyway.

.dan.

As I said: I want to add one of the modules posted, but need to make a decision which I should chose. It would help if somebody could just test them and list the pros and cons of each. I lack the time to do that myself and am happy with te flexinode solution.

Changing back the title...

Gerhard, I tested basicevent variant in comment #9 and it works fine. It has taxonomy built in unlike my original one, and has no need for extra tables.

This one is a good candidate ...

+1 on that.

that one has a rather useless init hook and no locations. I don't care about locations, but some people seem to think they are kind of important. i'd be happy to point those people to the flexinode solution...

Here is a version that removes the init hook, and tidies up things a bit.

The lack of a location is a plus for those who do not need it.

OK, so I was looking at basicEvent from comment 6.
But only evaluating it as a "OK, what am I supposed to do when making my own version" demo way, not as a working product.

I vote for the refinement from there which removes the dependancy on location - which I guess is the most recent working version.

OK, some folk may want location, but this is BASIC bare-bones minimum get-something-running framework. We can patch on features from here by hand or using flexinode.

.dan.

The version that is attached in #16 does not have location. It is just a basic event node.

I hope killes commits it.

I was reading this request and all replies, I did not look at the code, but I guess that my only point would be that as long as we can still use flexinode to create other events :)

You can use the basic one provided, or flexinode, or create your own.

These options are not mutually exclusive.

I am attaching the latest one that I use on a live site. Works very well.

Gerhard, please review and commit.

After discussing this with killes I've committed kbahey version from comment #20 created a 4.6 branch.

*sigh*, one of these days I'll learn to proof read before hitting post.

What I ment to say was: I've committed kbahey's patch from comment #20 and created a branch for 4.6.

...and created a branch for 4.6

Meaning, I can go to the event project page and download the module and I would have this simple event type? Would the tarball have been created already or should I wait for a day or two?

Thanks.

Sorry, just saw this thread:
http://drupal.org/node/37795

Does the latest tarball for 4.6 solve this issue as well?

ramdak5000: To answer the first question, the tarballs are generated at a fixed interval (what that is I'm not sure). I just checked and it hadn't made it in yet. I'd imagine that it should be up before too long so you might just want to try it torrow.

On the second, yes there are now two version of basicevent.module, one for 4.6 and one for HEAD/4.7. If you're comfortable with CVS you can grab a copy right now.