Kommentare

The Future of Serendipity

Kevin am um :

The htaccess could be a bit more seo friendly i believe.

For example...

If I edit a post's title, it will change the url for the post.

domain.com/archives/1-old-title.html domain.com/archives/1-new-title.html

If the post is indexed well, search engines and other sites will still point to the old url. The old url should have a 301 redirect to the new url. This will prevent duplicate content problems since both urls will bring up the same content.

Mario am um :

Am I too late? It's December now..hmm An automatic 301 redirect for renamed posts would be really great.

Garvin am um :

It's still december. ;)

There have been some new features that we wanted to get into 1.4 while there was still room, so there's been a bit delay.

If you want to try it right now, the current snapshots are exactly what will become serendipity 1.4 - and by migrating to a snapshot you will have no problem updating to the final version later, in fact it will be much simpler to update from a snapshot to the final 1.4 release.

Regards, Garvin

Mario am um :

How time flies...

You mean I should switch to 1.4 right now? I just installed 1.3 because I didn't wanted to have trouble ;)

But if you say "go", I guess I'll go...

As I work mainly with TYPO3 (and with the extension RealURL = user friendly URLs) I have the same problems there too.

Garvin am um :

Yes, I can recommend the current s9y 1.4 betas without any problem. I'm using it on my blog as well, and it definitely is more advanced than 1.3. :-)

As for remembering past permalinks: Currently there is no internal concept to track all previous links. It could also easily "spam" the permalinsk database table. Actually, if you use the %id% in your permalink, then the permalink will always work even when the title of the entry might change...