Thanks for the module, it is up and running at my website.

Now They have asked me for a repeating-date feature. In example, making a reservation like "every friday from 13 to 14 till October the 29th". ( there is something simillar at http://drupal.org/node/295239 ). They seem to need it badly.

Recurring reservations is a planned feature for 1.3.
How is it like now? If needs more work, maybe I could work myself with the code if someone working on this also helps me.

Thank you a lot, waiting for an answer

Comments

martin107’s picture

martin107 commented
Version: 6.x-1.2 » 8.x-1.x-dev
Assigned: Unassigned » martin107
Issue summary: View changes

So this is a reasonable addition to the project ....

My perception is that Drupal8 core release candidates are coming out between March and June which will signify Drupal 6's "end of life". So I am happy to work on this as a Drupal 8.x-1.x-dev issue. Others may want to backport later

I see two, equally valid approaches.

(1) A Form that creates N separate, initially identical, reservations, which can then be edited/deleted individually as the users wants.

(2) A Form which generate 1 reservations which appears N times throughout the calendar as appropriate. If the user edits the reservation then all references are changed.

Both options will fit the needs of different users. To highlight the issues think about adding a daily reservation every day for the next 10 years and then what do you expect when editing "the reservation". Or what this will do to the database.

Initially I expect to add a patch that implements (1) and depending on feedback I will implement option (2)

ZZman’s picture

ZZman commented

... to simplify this functionality in Simple reservation module :-)

Reservation could be done only in week base :
e.g. I insert new reservation on Tuesday 13:15 - 16:30 and in same form is field (repeat x-time) when I can put number (max. is defined in administration). Modul then will insert into database 1+x reservation on same day of week/same item/same reservation attribute.

There must be check if the item is available on every reserved day/ time.
If not, then reservation are write into database only partially and user is informed that in this and this ... date item isn't available. Then he can tune up unreserved reservation .... or delete bundle and start again with other date/time/item.

Recurring reservation could be bound together with unique recurring_id. In case of editing or deleting user can make decision if he do this only for one reservation or for all reservation with same recurring_id (checkbox in form).
There could be problem if recurring reservations are edited separately and then is request for mass change. It could be fixed when form is validated (if all values of all recurred reservations are same - if not user should confirm this.

BleuBi’s picture

BleuBi commented

what's the current status of recurring reservations? I downloaded the module for drupal 7, but it is not a feature?