Drupal 7 port of Date Repeat Sequence

I will, but I haven't even looked at dates in D7 yet, so I don't know when I'll get to it.

May I second this request?

As an event organiser I really need something like this for a simple booking system that I am trying to put together. I'm fairly new to Drupal and have invested much time in learning D7 and do not want to be bothered with Drupal 6, not least because of incompatibility with Drupal Commerce. If this module was ready for Drupal 7 I would be using it now.

As a sideline, may I ask about Token compatibility? In my use-case there will be some advantage to appending or including the node date into the node title and I expect this will be a fairly common requirement for others. I raise this point because currently there is a Token issue that is holding the Date module back from a stable release for Drupal 7. See http://drupal.org/node/1103032

I got here, trying to find the pieces for a booking system for d7 as well. Is much needed I think

pitxels, you might also want to follow this thread http://drupal.org/node/444544

when will it have a D7 port?

As far as I know the only D7 module providing this functionality is Node Recur. I've tried it and it works quite well, but it lacks the full featured sophistication of the Date Module

See http://drupal.org/project/node_recur

I found that only this module has chain edit in the repeating series. Can this feature implement in other related modules or update this module in D7?

I have test the following modules:

http://drupal.org/project/date_repeat_sequence (D6)

http://drupal.org/project/node_recur (D7)

http://drupal.org/project/date_repeat_instance (D7)

Date Repeat Sequence: Only Date Repeat Sequence has Chain Edit function: "Simply add a date repeat enabled field on any node type, setup the sequencing settings on the widget settings page and you are ready to go. All nodes in the sequence will have the options of saving changes for just that node, all future nodes, or all nodes in the sequence."

However, it has only D6 version and I have tested it in D6, I found if you edit one single event in the sequence with option "just this occurrence", this node will be removed from the sequence. Also, if you edit one event in the sequence with option "all future occurrences", it will create NEW future nodes but will not delete OLD future nodes (which should be deleted, otherwise, many duplications).

Node Recur: It bypass the date repeat API actually. In the content type, you need to enable the "node recur", then you need to use the "Node Recur" setting instead of the "Date Repeat API" to set the recurring dates and nodes with those recurring dates will be created. However, there is no sequence rule related to the Nodes in the recurring dates.

"This module provides no way to bulk/chain edit/delete nodes that are generated in sequences. To do this, it's recommended that you simply use Views bulk operations."

Date Repeat Instance: It uses the Date Repeat API to create "Instance", but not "Nodes". It will create "instances" for each dates under only the Date Repeat API, and you can edit each instance. However, there is no chain edit too.

I have done an initial port of this module to D7, and I believe it is working at least as well as it does in D6. You can get it from a sandbox:

http://drupal.org/project/1922762/git-instructions

Contrary to what the instructions on that page say, you should use the current name for the folder when checking it out, leaving off the "_for_d7", i.e.:

git clone --recursive --branch 7.x-1.x http://git.drupal.org/sandbox/gribnif/1922762.git date_repeat_sequence

If the original maintainer of this module would like to take my work and permanently copy it over to the main repository, he is welcome to do so. If he'd like to add me as a maintainer of the original module, I'd be fine with that, too.

Oh, so great! I will test it later!

Here is a link to Gribnif's sandbox: https://drupal.org/sandbox/gribnif/1922762

Thanx for the sandbox. Heres a fresh tar for those that do not know how to git clone (remove the underscore from the file extension)...

I wouldn't really advise using this unless you're looking to bug fix, it's really not working very well at all.