Event instance title field breaks views

Created on 20 June 2023, over 1 year ago
Updated 30 August 2023, over 1 year ago

Problem/Motivation

View breaks entirely when the event instance title is added.

Steps to reproduce

Create a new view of event instances, default settings, unformatted list.
Add the instance title field.

The view breaks and you can't add/configure the field. Refreshing the page displays a server error.

πŸ› Bug report
Status

Closed: duplicate

Version

2.0

Component

Recurring Events Views (Submodule)

Created by

πŸ‡ΊπŸ‡ΈUnited States mortona2k Seattle

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mortona2k
  • πŸ‡ΊπŸ‡ΈUnited States mortona2k Seattle

    This is on Drupal 10.1 RC. This may be an issue with field inheritance?

  • πŸ‡ΊπŸ‡¦Ukraine podarok Ukraine
  • Status changed to Postponed: needs info over 1 year ago
  • πŸ‡ΊπŸ‡¦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.

  • πŸ‡ΊπŸ‡¦Ukraine podarok Ukraine
  • Status changed to Needs review over 1 year ago
  • πŸ‡ΊπŸ‡Έ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 over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States owenbush Denver, CO
Production build 0.71.5 2024