Port to 6.x

Hi,

As I understand it views still isn't stable for Drupal 6 and as timeline is very reliant on views - please don't expect an update here before views is (mostly) done.

- Jeff

subscribing

Views is looking like it's in a pretty stable pre-release state now. Is there any update on the D6 status of timeline module?

Subscribing :)

I've begun porting timeline to Drupal 6 and I'll be committing the code to HEAD as things begin to work again.

subscribing

subscribing

*Love*

Thank you!

Subscribe...

A quick update. I've finally gotten timeline module's basics working in Drupal 6, but the code is pretty rough currently. When it's just slightly cleaner I'll be committing it to CVS.

Thanks Jeff. Please notify here the commit, I can hardly wait this porting! Maybe at that time a first addition to module release page can be useful, I hope some nice patches of 5.x version will be ported (e.g. #121298: Color coding based on taxonomy or content type or #104890: Add configurable icons for timeline events).

Hi All,

I've just committed a first pass at the Drupal 6 upgrade. You'll need to check it our from CVS, and use it with the views rc1. (I just saw the new rc2, so I'll try to get it updated for that very soon). The module is by no means ready for production use.

I would really appreciate some help restoring event and date modules support. Once we have that back I'll close this ticket and we can look at adding new features.

I've tried the new Drupal 6.x CVS version: using "Node: Post date" things work fine, but I've got a problem with a start date coming from date module. On line 278 of timeline.module:

    if (!isset($start_field) && in_array($field_id, $temporals)) {
      $start_field = $field_id;
      if (false) {
        $end_field = $field_id;
      }
    }

Lines 262-268;

  $temporals = array(
    'node_created',
    'node_changed',
    'comment_timestamp',
    'node_counter_timestamp',
    'accesslog_timestamp',
  );

As a test, I change line 278 to "if(TRUE)" solving the issue with a single date field (start date is ok but end date doesn't appear even if I add value2 field), maybe a control for cck date field should be provided.

Edit: "Wed, 31 Dec 1969 23:00:00 GMT" is assigned to all empty date values, these elements shouldn't appears in the view.

As I mention above Date and event module support aren't yet back. Also, I accept patches :)

Also, I looked at the event modules today and I think I'm going to drop event support as there doesn't appear to be views integration for D6.

Hi Jeff, I've tried the new version for Views RC2: this time no elements appear in the timeline (even with Node: Post date) and, most important, Date RC2 cease to works with Views RC2, so Date testing with this version is impossible (and Date HEAD is still unusable).

Views RC1 + previous timeline HEAD version + Date RC2 worked for me, maybe we have to wait Date module adapts to Views RC2.

Note: current HEAD version is incompatible with Views RC1, on timeline.views.inc it seems fixed with:

if(file_exists(drupal_get_path('module', 'views') . '/plugins/views_plugin_style.inc')) {
  require_once(drupal_get_path('module', 'views') .'/plugins/views_plugin_style.inc'); // Not sure this should be here.	
}
else{
  require_once(drupal_get_path('module', 'views') .'/includes/plugins.inc'); // Views <= RC1
}

but since basic functionalities doesn't work there on my installation I cannot say it is right.

Well, updating CCK (6.x-2.0-rc7), Date (6.x-2.0-rc3), Views (6.x-2.0-rc3) and getting the latest timeline HEAD from CVS (2008-09-20), CCK Date integration is nearer.

I have one CCK Date field named "field_release_date" with "From" and "To" values. To get their respective ID, on timeline.module I print out $field_id on function timeline_is_temporal (this function is a good improvement for scalability, thanks).

From value are stored on node_data_field_release_date_field_release_date_value To Value is stored on node_data_field_release_date_field_release_date_value2, so my temporals array became:

  $temporals = array(
    [...],
    'accesslog_timestamp',
    'node_data_field_release_date_field_release_date_value',
    'node_data_field_release_date_field_release_date_value2',
  );

Control statements are designed to get the first date value (checked via timeline_is_temporal) as From, the latter as To. In this way, CCK Date start to work with timeline!

Since the field must be specified by hardcoding timeline.module, this isn't the better solution (just good for testing). Field type or content, instead only name, should be checked on timeline_is_temporal.

Note: on titles, entities are shown instead special character (e.g. ').

@chirale, Thanks for checking this out for me. I'll be looking at refactoring timeline_is_temporal() today to add date module support. I'll post back once that's done.

I've just re-implemented date support. This was the only bit of functionality left before doing a beta. However there is still a bit to do here - mainly testing and documentation.

There should be a tarball on the project page once the packaging scripts run. This ticket here I'm closing :)

last minute subscribing...

Great Jeff, dev version behave exactly as #16, but without hardcoding, like old 5.x. If I found other bugs (or request new features, like backporting 5.x feature patches) I'll open separate issue for 6.x dev.