Increase Column Size of Content slugs, title, featuredImage, featuredImageURL
Description
Once you get nested down more than 3-4 levels in the hierarchy, it is nearly impossible for the url slugs to match the URL patterns of the parent hierarcy, because the 160 character limit is exceeded by items with longer titles. Suggest bumping the column size up to 500 characters to account for a deeply nested hierarchy.
Another option, would be to have the slug remain as only the slugified title, and add a `filePath` property/column, which could store the full hierarchical path - and would update itself on a hierarchy change. Mura, for example, implements this as `urlTitle` and `fileName` columns.
Activity
Show:
Jon ClausenJuly 27, 2021 at 8:48 PM
The comment below is resolved in PR 488:
Jon ClausenJuly 27, 2021 at 8:02 PM
One note, I just noticed:
The setParent function in BaseContent will prepend to an existing hierarchical slug when you change the parent.
We should probably adjust that to
to ensure that a hierarchy change doesn’t keep pre-pending new hierarchical routes.
Jon ClausenJuly 27, 2021 at 8:00 PM
My thought would be to go to 1000. Other than a bit of extra table storage space, I think that makes sense, when browers allow URLs up to 2K+ characters long.
Luis MajanoJuly 27, 2021 at 7:45 PM
Ok, so to clarify we increase both slug and title from 200 to 500? or 1000?
Also, HTML Description and keywords have to remain at 160 since that is the allowed max as per the HTML Spec.
Jon ClausenJuly 27, 2021 at 7:35 PM
You’re right. My bad. slug and title are 200. HTMLKeywords and HTMLDescription are the ones that are at 160.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Once you get nested down more than 3-4 levels in the hierarchy, it is nearly impossible for the url slugs to match the URL patterns of the parent hierarcy, because the 160 character limit is exceeded by items with longer titles. Suggest bumping the column size up to 500 characters to account for a deeply nested hierarchy.
Another option, would be to have the slug remain as only the slugified title, and add a `filePath` property/column, which could store the full hierarchical path - and would update itself on a hierarchy change. Mura, for example, implements this as `urlTitle` and `fileName` columns.