- Issue created by @seanr
- Status changed to Closed: works as designed
9 months ago 2:29am 29 February 2024 - π¦πΊAustralia dpi Perth, Australia
This is simply not an explicit feature of this project.
There are just too many options in the spec, to implement everything.
Typically the way of achieving this is to make your DR field multicardinality. The combined values of the DR fields become your 'inclusions'.
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.3 & MySQL 8last update
9 months ago Waiting for branch to pass - πΊπΈUnited States seanr
@dpi, I respectfully ask you to reconsider. I've created a working MR. The multicardinality option is insufficient - already tried that, but it doesn't set the right values (it actually creates separate calendar items which is incompatible with situations where one or more dates in a sequence is different, i.e. to avoid a holiday). This actually came out of a client request as the functionality actually existed on their old D7 site. This patch/MR should follow the spec and accomplish the goals:
https://git.drupalcode.org/project/date_recur_modular/-/merge_requests/9...
- π¦πΊAustralia dpi Perth, Australia
The project is intended to built upon with custom functionality, you may choose to copy code into your own public/private fork.
The scope of the project will otherwise spiral out of control, just like it did with Date Recur Interactive. Nobody wants/wanted to touch that code after so many years of neglect.
The multicardinality option is something I've personally used, particularly for https://www.drupal.org/project/oh β , it works as expected.
If your calendar or event system doesnt work with this, then I'd suggest tweaking the model.
- π¦πΊAustralia dpi Perth, Australia
Again not to discount your work. I'm sure its viable for your use case. I even maintain private client-specific customisations of these widgets.
But for example, I wouldnt want to overwhelm my clients with additional add data options, when extra field items is the intended approach. Excludes on the other hand, are required since theres no way to take away field items intelligently/sanely.
- πΊπΈUnited States seanr
OK, thanks. Looks like we are going to split it out into our own widget though we're using the patch for now for the sake of expediency (launch imminent!). I plan, perhaps over the weekend to break this out into its own project and release it.