dimaip at gmail.com
Sun Aug 17 17:26:48 CEST 2014
Hey all! Decided to bring this one out from IRC for a more detailed discussion.
The problem: URLs in Neos are very fragile: imagine renaming a single parent node in your website, and all of your links become 404.
The requirement: once published, the links should remain eternally available, even if the node gets renamed or moved.
I see the following solutions:
(a) Use GUID for URLs. Not really an option, as it's ugly and not SEO friendly.
(b) Add another shorter unique key to the nodes table, like some sort of uid that was in the old TYPO3. Then prepped that uid to the link, and use only that uid to determine the node from the link. That how the link would look like: http://domain.com/path/to/your/node/seo-friendly-title-123.html. If the page gets moved or renamed, old link would 301 redirect to new link, based solely on uid in the link.
Pros: reliable, easy to migrate URLs in the future.
Cons: ugly appendix to the link. For news articles it's OK, but not for static page nodes!
(c) Like in RealUrl: store rendered URLs, and once they become outdated, turn them into redirects.
(d) Combination of (b) and (c). I would love to use (c) for static pages and (b) for dynamic news articles.
I know there was discussion of this before, what have you decided on this? Any JIRA issues I have missed?
We really must decide on something about this feature, it's a crucial one for large news websites.
This is one of the things I can work with at the Sprint, if we settle on a preferred solution.
More information about the Neos