#indieweb #blog #web #known #wordpress
Yes, there are multiple parts. Wordpress (WP), Known, and myself all contribute to this, so I wanted to jot down the steps in the order I took them for anyone going about moving a blog or starting afresh.
Ready? Here goes...
Before deleting/installing/moving anything I:
- made a note of the existing URL structure I had on my existing WP blog (domain/blog/year/month/day/slug) so I can do redirects later on if needed
- made a note of my database details, including login information
- exported all current mySQL databases
- used the export tool within WP to make a copy, so I can import it later if anything goes wrong and I have to reinstall WP (more on that later)
- moved everything I had on my local machine to a separate folder for reference (.htaccess file, custom CSS, etc.)
Feeling fairly secure I had everything I proceeded.
- deleted everything from root using Coda
- deleted old mySQL databases using myPHPadmin control panel
- created new MySQL database using myPHPadmin control panel
- downloaded Known from http://withknown.com (DO NOT DO THIS)
- unzipped and moved files to root using Coda
- browsed to my domain and followed the simple setup instructions
- enabled all the plugins that came with the install
- added Short Profile plugin
- imported Wordpress generated XML file
- edited .htaccess file with redirects for https
While I was waiting to get the email that the import had finished, I started going around and updating social profiles with the new URL. As I use some IndieWeb tools to syndicate my content (pull in Instagram posts, social media comments, etc.), I want to make sure they all pointed to the right place.
So I changed everything from http://davidjohnmead.com/blog to http://davidjohnmead.com. I can now use this domain to log into various IndieWeb services.
- signed into Quill (online tool for posting)
- signed into Aperture (feedreader)
- signed into OwnYourGram (pulls your Instagram posts into your site)
- signed into OwnYourSwarm (pulls your Swarm checkins into your site)
- signed into Teacup (replacement for Foodspotting)
- signed into Brid.gy (pulls comments from various social media into your blog)
When I went to test these I started running into issues.
Aperture creates a
<link> for you to add to the
<head> of your HTML pages.
<link rel="microsub" href="https://aperture.p3k.io/microsub/xxx">
There didn't seem to be a way to add this within the Known settings. I also didn't know which file I could edit to manually add it using FTP.
The Brid.gy login for Instagram wanted my blog's profile URL (https://davidjohnmead.com/profile/davidmead) to be in my Instagram profile, but OwnYourGram was fine with the root being in there.
Teacup would let me login, create a post, but it never showed up on my blog.
OwnYourSwarm captured checkins, but only sent them to my blog if I logged in and imported them again.
I needed a way to send my blog posts and replies to Twitter, so I found the Known plugin on GitHub and installed it, but it broke.
After all this I still didn't receive any notification that the Wordpress XML import had worked.
So at the end of the day I had:
- A new Known blog at my domain root with the last 10 Instagram posts pulled in via OwnYourGram
- No old WP blog
- No old blog content
- No way to syndicate to Twitter
- No way to pull in comments from Instagram
Not terrible, but not where I wanted to be. On to day two.