A client just created a post with a really long slug (90 characters), no special characters (other than hyphens) etc.
Whenever the link to that post was clicked, including the “Preview” or “View this Post” links from the Admin back end, a 404 was generated.
Once we manually trimmed the slug, everything worked as expected. Is this a “feature” or a “bug”?
EDIT: a Note for all those talking about DB limits.
If I were hitting the DB field limit, then the slug itself would be
truncated. Think about it for a second. In the case of most WP
installations, wp_posts.post_name is VARCHAR(200). So, let’s say that
someone types in a title with > 200 chars. What happens? The slug gets
truncated to 200 chars and stored in wp_posts.post_name. It’s not like
someone is going in and typing the full title of the post in the
browser address bar, substituting the spaces with dashes right? The
URL is being generated by WordPress, and it’s getting the URL from the
wp_posts.post_name table and just putting that in the href attribute
of the anchor tag. So there’s not going to be a disparity there. The
whole DB thing is a red herring.
In any case, the slug in question is only 90 chars, so it has nothing to do with DB limits.
Are there any known limitations around rewrite?