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

Some URL routing in Ghost is giving 404 error to posts #22078

Open
1 task done
sergiospagnuolo opened this issue Jan 29, 2025 · 2 comments
Open
1 task done

Some URL routing in Ghost is giving 404 error to posts #22078

sergiospagnuolo opened this issue Jan 29, 2025 · 2 comments
Labels
needs:triage [triage] this needs to be triaged by the Ghost team

Comments

@sergiospagnuolo
Copy link
Contributor

Issue Summary

I updated today to the latest version 5.108.1 and suddenly all my new publications starting to show 404. My homepage was indexing the posts, but when you clicked on them it gives you error 404.

One thing I did: I changed the slug in the editor. I think the CMS might now be routing the URL properly. When I downgraded back to 5.107.2, things came back to normal.

Steps to Reproduce

  1. Updated to v.5.108.1
  2. Created a new post
  3. Changed the URL of this posts
  4. Published the post
  5. Clicked on the link of this post (CMS card, home page, within the post editor)
  6. Received a 404 message

Ghost Version

5.108.1

Node.js Version

18

How did you install Ghost?

ghost CLI

Database type

MySQL 5.7

Browser & OS version

No response

Relevant log / error output

Code of Conduct

  • I agree to be friendly and polite to people in this repository
@github-actions github-actions bot added the needs:triage [triage] this needs to be triaged by the Ghost team label Jan 29, 2025
@sergiospagnuolo sergiospagnuolo changed the title Some URL routing in Ghost prevented pages from being shown Some URL routing in Ghost is giving 404 error to posts Jan 30, 2025
@sagzy
Copy link
Contributor

sagzy commented Jan 30, 2025

Hello @sergiospagnuolo,

I have tried to reproduce the error locally by following the reproduction steps, but I have not been able to. Ghost v5.108.1 has been deprecated for another reason (cf. issue), so curious whether this is somewhat linked.

Do you confirm that downgrading to Ghost v5.107.2 has solved your problem?

@sergiospagnuolo
Copy link
Contributor Author

Hi @sagzy, I will make tests with the newest version of Ghost, and I will try to replicate again.

I can confirm that when I used 5.108.1, this issue happened, but when I downgraded, it went back to normal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:triage [triage] this needs to be triaged by the Ghost team
Projects
None yet
Development

No branches or pull requests

2 participants