End date value is not respected on Daterange field if using the same date field with _1 appendix on views, shows an hour default interval instead

Created on 7 October 2022, over 1 year ago
Updated 7 April 2023, about 1 year ago

Problem/Motivation

The end date value of events are not used when using field type assign is given another date field that has incorrect field machine name daterange.


This caused by the condition of $end_dates value returning an empty string at src/FullcalendarViewPreprocess.php:160

Steps to reproduce

  1. Create a field with default datetime_range module that comes within core naming
  2. Create two to three nodes with end date assigned
  3. Create a fullcalendar views with start date and end date field pointed to two different fields on views that belongs to same field_date, making field_date and field_date_1 for views field

Proposed resolution

Rewrite condition to check $start_dates if its an array, which will allow the $end_date value assigned.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Closed: won't fix

Version

5.1

Component

Code

Created by

πŸ‡ΉπŸ‡ΌTaiwan g-brodiei

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024