Skip to main content

David Mead

Setting up a blog, using Known, part 1

4 min read

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...

Day One

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.

  1. deleted everything from root using Coda
  2. deleted old mySQL databases using myPHPadmin control panel
  3. created new MySQL database using myPHPadmin control panel
  4. downloaded Known from http://withknown.com (DO NOT DO THIS)
  5. unzipped and moved files to root using Coda
  6. browsed to my domain and followed the simple setup instructions
    Apache mod_rewrite only requirement not wholly met (screenshot)
  7. enabled all the plugins that came with the install
  8. added Short Profile plugin
  9. imported Wordpress generated XML file
  10. edited .htaccess file with redirects for https

 WordPress import started confirmation message (screenshot)

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.

  1. signed into Quill (online tool for posting)
  2. signed into Aperture (feedreader)
  3. signed into OwnYourGram (pulls your Instagram posts into your site)
  4. signed into OwnYourSwarm (pulls your Swarm checkins into your site)
  5. signed into Teacup (replacement for Foodspotting)
  6. signed into Brid.gy (pulls comments from various social media into your blog)

When I went to test these I started running into issues.

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.

David Mead

Lost last 2 years blog content!

1 min read

Trying to import back into WordPress and I'm missing last 2 years of entries. Looking at the .XML export file WP generated I see the following...

"<b>Fatal error</b>:  Out of memory (allocated 242221056) (tried to allocate 130968 bytes) in <b>/nfs/c03/h05/mnt/56448/domains/davidjohnmead.com/html/blog/wp-includes/taxonomy.php</b> on line <b>1398</b><br />"

 Would've been great to know that when I ran the export, before wiping out the blog from the server.

Also, it seems none of the media came across or could be imported either.

This is not going well.

David Mead

Moving from WordPress to Known

1 min read

With WordPress moving over to Gutenberg recently (the new editor literally not working for me), and the continual bloat from installing more and more plugins, I thought it might be time to try a different blogging platform.

Known is a "publishing platform for everyone" that been around for a few years now.  I first tried it 4-5 years ago, and it worked pretty well, but it had some development kninks to work out.

The move has not been without it problems, not least being unable to import all of my content from WordPress, so I'm going to do a couple of posts outlining the process, fixes, and issues I've run into.