Hacker News Reader

Comment by kyle6884 | Hacker News Reader

Might be a good idea to put a canonical tag on the old to the new content.

http://archive.wired.com/wired/archive/1.02/crypto.rebels_pr... > http://www.wired.com/1993/02/crypto-rebels/

Thanks for the catch! We're still fine tuning our redirects from archive to the new article locations. We no longer have print pages so we'll need to redirect those to the new posts. At least the actual post (i.e. http://archive.wired.com/wired/archive/1.02/crypto.rebels.ht...) is redirecting correctly at the moment.

Also you can see at the bottom of the actual article on WIRED.com we did add tags to archived magazine content, like the article you mentioned, to group content together a bit. Thanks!

http://www.wired.com/1995/06/xanadu/ is missing the first few paragraphs from http://archive.wired.com/wired/archive//3.06/xanadu_pr.html

That being said, great work!

I'm about to transition an old Drupal site with 10+ years of content to WordPress with new URL patterns. I'm curious, how have you approached the doubtlessly massive number of redirects at Wired?

Once you have a list (which you already have if you've automigrated it) just generate a list of rewrite rules with header set to "Moved Permanently".

But I'm curious, usually platform changes go from Wordpress to Drupal because people need features other than a blog and simple CMS system. What made you go the opposite route?

Because Drupal is a horrible, horrible system with a flawed architecture that promises a lot and never fails to under-deliver.

(Sorry, I worked at an agency that sold a lot of oversold drupal6 projects)

I recently completed a pretty huge D7 app. The biggest challenge was not the code, but pressuring our customer representative to not over-sell...

Aside: What's with all the blank newlines at the top of the source of that first link? (http://archive.wired.com/wired/archive/1.02/crypto.rebels_pr...)

Reply on news.ycombinator.com