Hey Guys,
I know this probably doesn't belong to this thread but.....
masterchief wrote:
One is to require a field like the infamous title_alias in the content table. Actually, step back a sec.
What would be handy is to have two common fields in all data tables:
name - this is the text using in SEF url's, eg "spacenews"
title - this is the 'real' title, eg "News About Space"
Name would need to be held constant to maintain URL stability but the actual title can change to whatever you like. They could be the same.
Off course, I understand where you are coming from and it makes perfect sense to keep the name field constant. On the other hand, SEO is a process and sometimes it is necessary to change the target keywords. Therefore, I believe it is important to be able to easily change the pathway.
Here is my idea:
Using php, it is no big deal to redirect to new url and return the status code 301 (Permanently moved). This way the new page would inherit the old pagerank, which is off course a major advantage. Following your idea, I would have to create a new item in order to change the pathway. Nothing inherited whatsoever.
I see basically two ways to do this:
1. Option:
- When saving a content / menu item, check if the title_alias / name has been changed
- If so, save the old value in a new table #__redirect, mapping the old url to the new one.
An incoming request would look like this:
- Look up the internal url that corresponds to the current pathway
- If there is none, lookup in table #__redirect, redirect to the new pathway (Status 301)
- If there is none, process Error 404 Document not found
2. Option:
- The pathway is in a separate table and points to an Itemid, there may be more than one pathway to the same Itemid
- Look up the itemid that corresponds to the current pathway and retrieve name / title_alias (Both could be done with one query )
- Compare pathway and title_alias / name
- Redirect (Status 301) if not the same, else load as usual
I am just a newbie to this forum, but this approach seems to be more userfriendly to me and still is a lot more search engine friendly than a static pathway. However it wouldn't interfere too much with the running system (exspecially Option 2) and I am sure it could even be done on a plugin basis (i.e. OpenSef). In a separate table it also appears backward compatible.
Anyway, your doing a great job keep it up.
Cheers
http://www.publicinstinct.co.zahttp://www.swissfin.co.za