- Issue created by @mortona2k
- πΊπΈUnited States mortona2k Seattle
This is on Drupal 10.1 RC. This may be an issue with field inheritance?
- Status changed to Postponed: needs info
over 1 year ago 3:13pm 22 June 2023 - πΊπ¦Ukraine podarok Ukraine
Could you provide more details, please?
- Steps to reproduce or test within Merge Request
- screenshots
- log messages - πΊπΈUnited States owenbush Denver, CO
I believe this is an underlying core issue which is called out on the Field Inheritance project page
π Allow adding computed bundle fields in Views Fixed
I've been working hard to try and get it resolved, but as of yet it is not merged into core.
- Status changed to Needs review
over 1 year ago 2:19am 14 August 2023 - πΊπΈUnited States mortona2k Seattle
That was it! The linked issue hit RBTC today. I just used a patch from the 10-backport fork and the error went away.
- πΊπ¦Ukraine podarok Ukraine
nothing to review here, right?
Unless we add a patch to composer.json to have core patched during installattion - πΊπΈUnited States mortona2k Seattle
That's right. If anything, a note on the project page would help people find the patch before it's released.
- πΊπΈUnited States owenbush Denver, CO
I experimented with a patch in the module's composer.json file, but it is really problematic for a number of reasons:
1. You cannot guarantee that a site is using cweagans/composer-patches
2. The patch for core differs depending on what version of core it is for, so we would end up having to have different versions of recurring events for different versions of core, just to support different patches, which is unnecessary - it can be up to consumer sites to use whichever patch they need for whichever version of core they are using.I will update the project page to link to the patch like I have done for the field inheritance module.
- Status changed to Closed: duplicate
about 1 year ago 12:13am 30 August 2023