Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 2025 Newsletters are not being displayed #3651

Closed
2 tasks
babakamyljanovssw opened this issue Feb 26, 2025 · 0 comments · Fixed by #3652
Closed
2 tasks

🐛 2025 Newsletters are not being displayed #3651

babakamyljanovssw opened this issue Feb 26, 2025 · 0 comments · Fixed by #3652
Assignees
Labels
Type: Bug A problem with existing functionality

Comments

@babakamyljanovssw
Copy link
Member

@wicksipedia @amankumarrr

Describe the bug
2025 Newsletters are not being displayed even there are 2 newsletters in 2025 folder.
https://github.com/SSWConsulting/SSW.Website/tree/main/public/images/newsletter-uploads/2025

To Reproduce

  1. https://www.ssw.com.au/newsletters
  2. Find out 2025 Newsletters are not there

Tasks

  • Investigate
  • Fix

Expected behavior
2025 Newsletters are displayed.

Screenshots/Video
Image

@babakamyljanovssw babakamyljanovssw added the Type: Bug A problem with existing functionality label Feb 26, 2025
@github-project-automation github-project-automation bot moved this to 🤷‍♂️ Needs Triage in SSW.Website Feb 26, 2025
@babakamyljanovssw babakamyljanovssw moved this from 🤷‍♂️ Needs Triage to 🔖 Backlog - Ready in SSW.Website Feb 26, 2025
@babakamyljanovssw babakamyljanovssw self-assigned this Feb 26, 2025
@babakamyljanovssw babakamyljanovssw moved this from 🔖 Backlog - Ready to 🏗 In progress in SSW.Website Feb 26, 2025
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in SSW.Website Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug A problem with existing functionality
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant