Options for the field to override in date_occur_parent field settings show fields on other node types

Created on 13 March 2024, 4 months ago
Updated 14 March 2024, 4 months ago

Problem/Motivation

I don't know if this is by design or not, but it seems weird.

If I have two event node types, each with their own Recurring dates field, and I add a date_occur_parent field type A, then in the "Recurring date field to override" dropdown I see BOTH fields from types A and B.

It seems to me that only the field on the same node type would make sense?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Active

Component

User interface

Created by

πŸ‡¬πŸ‡§United Kingdom joachim

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

Comments & Activities

  • Issue created by @joachim
  • πŸ‡³πŸ‡±Netherlands ekes

    In the beginning, but not implemented, was the idea to also allow having augmenter entities. Rather than close, overrride and replacing in the index as is implemented, these would another entity type that just has the fields to add/replace data on the original. So the possibility is still there in the original architecture, but wasn't something that was needed for the project the module was originally written for.

Production build 0.69.0 2024