Event page allows an unrealistic 10-year duration

[dharmikpatel97]

This avoids assuming the end date is definitely wrong. It focuses on the observable behavior.

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".

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.

Steps to reproduce

• Open the WordPress Credits Contributions event page.

Check the event details panel.
Observe the start and end dates.

Actual result

Start date: 9 Apr 2026
End date: 9 Apr 2036
UI displays: "Ends: in 9 years"

Expected result

Event durations should be validated to prevent unintended multi-year spans, or the UI should clearly indicate that such long-running events are intentional.

[sabernhardt]

It's a good thing you were able to contribute to the Credits program before it ends :)

Anyway, I moved this report to Meta Trac, where (most) tickets about WordPress.org sites belong.
​#meta8280