Closed (fixed)
Project:
Optional End Date
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
4 Jul 2024 at 07:41 UTC
Updated:
3 Feb 2026 at 02:17 UTC
Jump to comment: Most recent
Comments
Comment #3
mrshowermanComment #4
birk commentedYes you are absolutely right!
This will break on sites using a core version older than 10.3.x so I'll make a new 2.x version of optional_end_date with these changes.
It's primary administrative work on my part, but I still need to find the time to do this.
Hopefully I'll get around to it soon.
I'm unsure of how the merge request works against a new branch, with credits and all. I'll make an update in this issue if I need you to update the merge request to keep credits, maybe it's all done automatically never tried it don't know.
Comment #5
mrshowermanThanks for the update!
Just let me know if you need help with the MR.
Comment #7
birk commentedThank you for the merge
I've created a new v2 branch, updated the core requirements and merged the request.
I'll try to find the time next week to make a v2 release so this gets out there. Thanks again for your code and patience.
Comment #9
bryanmanalo commentedThe module does allow empty end date.
However, on render for the formatter, even if end date is left empty, it displays both start and end date. It copies the value of the start date, and display that as the value for end date.
Is this expected? Any workaround?
Comment #10
birk commentedWhat version of optional end date and Drupal are you using?
Comment #11
bryanmanalo commentedI am using dev-1.x
Comment #12
bryanmanalo commentedApologies, never mind. There was a custom twig on our end causing this.