Feature #9774
Make permalinks configurable
| Status: | New | Start date: | 2010-09-16 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
This is a follow up from:
http://forge.typo3.org/issues/9071
This issue is for discussing how a permalink should look like and what would be nice to be implemented in t3blog.
Felix Nagel wrote:
Afaik normal FE link and permalink should not be the same as normal links consists on date and title of a blog post -- permalink should be based upon an ID, so its really permanent!
We should discuss again how a permalink should look like -- perhaps its most suitable to make use TS for rendering the link, so its possible to define its for yourself. This should be an own issue, shouldn't it?
Dmitry Dulepov wrote:
Yes, it should be a separate RFC. But beware that you will have duplicate content if permalink and normal links are different.
If you do not use RealURL, you will get links with post ID. Since date does not change, you will get the same link all the time. With RealURl you will get an alias, which will not change unless you force it to change (even if you rename the post, alias will not change). So I do not see aproblem with using the same link.
- * *
I checked BE part again and I will not rewrite it now because it is too complex. It never worked, so I will leave it as is for now. If I come to BE module again, I will rewrite that part. For now I will close this RFC as resolved because FE part works now.
History
Updated by Felix Nagel over 2 years ago
The duplicate content problem could be easily solved by using a cononical tag, which should be easy to be implemented.
http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html
Updated by Felix Nagel over 2 years ago
Im using this snippet for my website:
lib.canonical = TEXT
lib.canonical {
typolink {
parameter = {page:uid}
parameter.insertData = 1
useCacheHash = 1
# add all get parameters from the current URL
addQueryString = 1
addQueryString.method = GET
# remove the page id from the parameters so it is not inserted twice
addQueryString.exclude = id
returnLast = url
}
wrap = <link rel="canonical" href="{$siteURL}|" />
}
page.headerData.20 < lib.canonical
# remove in blog cause of permalinks
[globalVar = TSFE:id = 172] && [globalVar = GP:tx_t3blog_pi1|blogList|showUidPerma > 0]
page.headerData.20 >
[global]
Updated by Dmitry Dulepov about 2 years ago
We cannot set page.headerData inside t3blog because somebody else could use that value (20, 30 or whatever).
The purpose of t3blog is to get up and running fast. It should work out of the box. Therefore forcing user to make a canonical <link> to make the blog SE-friendly does not like a good idea to me.
What exactly is wrong with having a single link to the blog post?
Updated by Felix Nagel about 2 years ago
I agree that t3blog should work out of the box and I agree that using my proposed TS is only a workaround not a solution.
In my opinion the permalink should work even when the date or the title is changed later. This is only the case when its independent from publishing time and blog post title.