Changes between Initial Version and Version 1 of Ticket #65405
- Timestamp:
- 06/04/2026 10:39:26 PM (3 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #65405
- Property Keywords needs-testing ux removed
- Property Milestone Awaiting Review
- Property Resolution → reported-upstream
- Property Status new → closed
-
Ticket #65405 – Description
initial v1 1 1 This avoids assuming the end date is definitely wrong. It focuses on the observable behavior. 2 2 3 On the WordPress Credits Contributions event page, the event is displayed with a start date of 9 Apr 2026 and an end date of 9 Apr 2036, resulting in a duration of approximately 10 years and the message "Ends: in 9 years".3 On the [https://translate.wordpress.org/events/2026/wpcredits-contributions/ WordPress Credits Contributions event page], the event is displayed with a start date of 9 Apr 2026 and an end date of 9 Apr 2036, resulting in a duration of approximately 10 years and the message "Ends: in 9 years". 4 4 5 5 It is unclear whether this is an incorrect event configuration or a system issue that allows unrealistic event durations. The application should either prevent such durations through validation or clearly support long-running events if they are intended. … … 7 7 Steps to reproduce 8 8 9 Open the WordPress Credits Contributions event page.9 - Open the WordPress Credits Contributions event page. 10 10 Check the event details panel. 11 11 Observe the start and end dates.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)