Open andybroomfield opened 7 months ago
Patch is being used at BHCC, so will let you know how it goes. Initial testing shows this works.
This is working for us, new drafts and reviews arn't removing the event from the listing.
Just checking: the intention here is to calculate and store the future occurrences of the recur field on both the latest (unpublished) revision and the (published) current revision.
From what I gather yes that is correct, as this is to prevent interference with the existing set up and tests, so that dates are generated for the current revision and the latest (unpublished) revision.
Do we want to move forward with this. Currently if an event goes to a new draft or review it will fall of the list. New events work does also resolve, but that requires the switch to search api which maybe not everyone will go with straight away.
@ekes any more thoughts on this?
This is possibly redundant with the search api work, but if your using the existing view you need the patch else if you make a new revision events do disappear.
Fix #143
Adds the patch from https://www.drupal.org/project/date_recur/issues/3010184#comment-13156851 (comment 6).
This allows events that have been published to be moved to draft or review and still show on the events calendar, as the default (published) revision will retian it's calculated dates used by views.