Home :: PigPog Moving On Up

Mind the Step. Assuming you’re reading this, we’ve successfully moved PigPog’s blog from ‘http://pigpog.com/blog/’ to ‘http://pigpog.com‘. If you’re not reading this, maybe you should be.

Anyway, this means that the front page of the site is now the blog, and everything else will be arranged from there – probably including moving the articles from the wiki into the Pages on the right hand side of the blog.

You Broke All My Bookmarks?

No, we didn’t. It should all still work as before – if you visit a page on PigPog with ‘/blog/’ if it, our web server will know what to do. For the more technically minded, we’ve set a redirect so that anything under /blog/ gets redirected up a level. The result is that Apache ends up giving the browser exactly what it asked for anyway, and the browser knows it’s moved.

RSS Feeds?

No change. Should always have been pointing to ‘http://pigpog.com/rss’ – this has always been a redirect, and it actually redirects off-site to FeedBurner, anyway. They should find out about all this as soon as they request the next update and get redirected. If not, I’ll update them manually.

How Easy Was It?

(Ignore this bit if you don’t care)

Very easy, actually. Just moved all the WordPress folders up a level (well, copied them, actually, I like to be paranoid), changed the addresses in the two lines under ‘Options’ in WordPress Admin, then added the redirect to httpd.conf. The only tiny problem was that pages started getting redirected to the nasty-looking real URLs instead of the nice ‘pretend directories’ that WordPress does so well. I just opened the ‘Presentation’ page in Admin, and saved it without changing anything – all started working nicely again.

Found out that if WordPress has been set to serve a page where a real page exists – we had an ‘/about/’ folder, and a WordPress Page called About, for example – WordPress doesn’t grab the URL. The original real file gets served. If you don’t want that, rename one of the two, or just delete the real file. Seems like the most sensible way to work, though it’s probably an upshot of how the imaginary folders work. I think WordPress becomes the handler for all 404 errors, then just redirects back to the original 404 page if it can’t handle the request either.

If you’re still reading at this point, you’re probably very bored. We’ll start doing some tests of moving articles over next.