Long slugs going to 404

[edalzell]

Discussed in #4371

^{Originally posted by mrmathewc October 3, 2021}

Issue description

I'm creating blog posts using collections and have added one of the posts that I have hosted on my WordPres website. I noticed that when the slug length was long, the route to the post doesn't respond and instead goes to a 404, however when I create a post with a relatively small slug, it loads the route/page fine.

Steps to reproduce the issue

1. Create 'Blog' as collection
2. Set route to: route: '{parent_uri}/{slug}'
3. Create long blog post with auto-generated slug called: "Big massive title to see if the routing works on the site"
4. Create small blog post with auto-generated slug called: "Test blog"
5. Try and preview both posts, 1 works whereas the other does not (for me, anyway)

What's the expected result?

Expected result is long-slugs should display the route the same as smaller slugs.

What's the actual result?

Longer slugs don't route to template or page and instead show a 404 page.

[duncanmcclean]

@mrmathewc By any chance are the slugs for these entries longer than 256 characters?

Tried to create some entries and that seemed to be the cut-off point between it working and me getting a 'File name too long' error from PHP - which is possibly related to what's going on here.. 🤔

[edalzell]

Create long blog post with auto-generated slug called: "Big massive title to see if the routing works on the site"

@duncanmcclean ^^^

[duncanmcclean]

Always helps if I read the original post 🙈

Just created a new entry with Big massive title to see if the routing works on the site as the title, which has auto-generated the slug. When I go to visit the page, it doesn't seem to 404 me which is odd....

Does your entry have any parent entries? What version of PHP are you using?

[jasonvarga]

@mrmathewc Please create a repo with this problem reproduced. Following the steps you provided, it works just fine for us. I even created posts with much longer URLs and it still worked.