Duplicate scheduled year for single day events whose scheduled year is rendered
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 58/100
Research direction
Start with templates/events/includes/time_tag.html, which the issue identifies as containing the offending template logic, and reproduce the case on the main events page with a single-day event in a future or past year. Done means each affected event renders at most one year string, with the current year omitted when it is unambiguous.
Written by the indexing model from the issue text.
Description
Describe the bug
What
For single day events (events that start and end on the same day) that require year string to be displayed [which are]:
- Single day events scheduled for a future year
- Single day events that have passed rendered at the "You just missed..." section of the main events page {pythondotorg url}/events/
The year string is rendered multiple times.
Here are a couple of examples
1. Past event scenario
2. Future event scenario
To Reproduce
- Set up a single day event scheduled to start in the future year or scheduled in the past (e.g. event has just been concluded)
- Navigate to the main events page (http://localhost:8000/events) and observe the year string rendered multiple times.
Expected behavior
- Single day events (regardless of schedule year) should only render a single year string (if necessary) since the event is guaranteed to start and end within the same year.
Addressing "If necessary"
- Future single day event scheduled within the current year does not need to render the current year as there is no date/year ambiguity.
- Past single day events (Events just missed) would need to render the year string dispelling any ambiguity on year event took place.
URL to the issue
No response
Screenshots
No response
Browsers
Firefox, Chrome, Safari, Microsoft Edge, Other
Operating System
Linux
Browser Version
No response
Relevant log output
No response
Additional context
I've traced down the offending template logic:
https://github.com/python/pythondotorg/blob/1bfeace44973dff8310f695ca15b40c277047cc7/templates/events/includes/time_tag.html#L1-L9
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 700
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 14
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/pythondotorg
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
python/pythondotorg#3137 · 2 comments ·
-
app/pages bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
python/pythondotorg#2677 · 3 comments ·
-
backend easy
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
python/pythondotorg#2453 · 8 comments ·
-
bug good-first-issue
Difficulty 4/5 3-5 days Newbie friendliness 30/100
python/pythondotorg#3125 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 74/100
python/pythondotorg#3094 · 5 comments ·
All issues in python/pythondotorg
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
xinnan-tech/xiaozhi-fde-talk#263 ·
-
rules
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
huggingface/Repo2RLEnv#163 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
huggingface/sentence-transformers#4074 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·