Create Recurring Reservations

Not currently. But try experimenting with the Date Repeat module. There is an option in the settings to unlock that field so you can edit it. I haven't tested it out as far as if conflicts are handled correctly. If conflicts work okay one feature you will lose is the status (i.e. checked out, returned, etc.) As that status will apply to all of the reserved dates.

The code assumes only one date value per reservation. So using repeating dates may break a few things.

Please consider this feature for upcoming releases of MERCI. This would be insanely useful. Thank you.

The Date Repeat module worked perfectly for my purposes, but I'm not using the checkout feature at all and any repeating dates are entered before potential conflicts.

I did test to see if conflicts are handled correctly and it seems as if they are not. It allowed a repeating date right over an existing reservation.

The MERCI module could only check for conflicts on the first of a recurring series.

To account for repeating dates and conflicts, I used the Date Repeat Entity module, which breaks each recurring date into its own entity while keeping them linked.

Using Date repeat entity, as suggested in#4: If you try to create a single reservation that conflicts with a previously created repeating reservation, it flags it appropriately. However when you create a new repeating reservation only the first date of the reservation is being checked against existing reservations. This allows for conflicting reservations to be made. ccheezum, are there any settings or other changes you made to make this work for you?

Hello,

I upgraded my MERCI installation to use merci-7.x-2.x-dev, in hopes of fixing the repeating reservation conflict issue I was having. The first time I tried to create a repeating reservation where one event later in the series conflicted with a pre-existing event, the error message displayed appropriately. However, after that one time I was never able to get the error message to display again in that scenario. So I was once again able to create repeating reservations which conflicted with pre-existing reservations. I am using Date Repeat Entity 7.x-2.0.

I'm not seeing any errors in my logs, and I didn't install any new modules or update any settings in the interim. Has anyone else encountered this issue? Or do you have any suggestions for debugging it?

Thank you in advanced for you assistance.

I don't think the Date Repeat Entity module performs form validation for the entities. This is why #5 gets a conflict for a single reservation against reservations created by the Date Repeat module but not conflicts with reservations created by the Date Repeat module. The conflict validation is done on the form level. So the date repeat entity code would need to be modified to load and validate the form for each cloned entity.