Chrome on my phone does offer a 'simplified view' for certain pages, but I couldn't find a way to turn on that for desktop.
An Englishman abroad - Been working with the web since the 90's, main focus now is UX/UI. Moved to Cleveland, Ohio in 2001.
1 min read
4 min read
Time to get a WordPress instance back up and running. Piece of cake as I backed up and exported everything, right? That way links don’t stay broken and I can just start using the Known blog (on the root) going forward.
Even though I had removed everything of my existing WP install by FTPing into the server, using Coda, I went in through the Media Temple control panel and removed the WP install there too.
While in the 1-click-apps screen I then added a new version of Wordpress in /blog.
That set up just fine. In my browser I went to http://
I’ve been blogging for a while now, and have imported various other blogs into this one; Blogger, Tumblr, Known, and older WP blogs since 2005. When it finished I was presented by a HUGE page informing me of all the things that didn’t get created or failed!
This was worrying. I did notice the first block were all referencing Post Kinds. Now, this is an IndieWeb plugin that worked well, but I hadn’t reinstalled it. That must be the problem. So I went, installed the plugin and ran the importer again.
This time I no Post Kinds errors, but still a huge page (over 6000 lines) with a lot of 'Failed to import media', 'Post “blah blah” already exists', and...
“Warning: mysqli_real_escape_string() expects parameter 2 to be string, object given in /blah/blah/blah/blah/blah/blah/davidjohnmead.com/html/blog/wp-includes/wp-db.php on line 1102”
Now posts already existing does make sense as this was the second time I’d tried this. The bigger issue was when I went to look at the blog there were no posts after September 2016! Over two years of photos, checkins, and writing gone.
Opening the file on my local machine, and checking the file size, I noticed that it was way smaller than zipped versions of previous exports. Hitting the end of the XML I saw this at line 475098…
<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 />
OMG! When WP ran and built the export it failed and I never saw any notification of that.
So not only am I missing the last two years, none of the 4.5k entries that are there have media that were part of the posts.
Time for ‘Plan B’ - The diligent exports from mySQL I make every so often.
After asking someone who knows (Thanks GWG), I logged into myPHPAdmin and started to import the .sql file into the new WP created database.
And it failed. Too big. This is a nearly 60Mb file, but the upload cap it set to 10Mb.
Now comes the searching for help documentation, the cries for help on IRC, and me gingerly typing things into Terminal that I don’t understand in the hopes I can move 60Mb of SQL to the right database using SSH.
Not my fun idea of a weekend, but looking the bright side I’ve already got 4 spam comments on the WP blog less than a day of putting it back up.
3 min read
So after part 1, we head into day two of setting up the new blog. I currently have:
I had logged into GitHub and filed a couple of issues about plugins and import not working.
Chatting on the IndieWeb IRC channels (a great resource btw) it became apparent that the build on the WithKnown website is out-of-date. Marcus Povey, one of the project contributors, hosts up-to-date builds if you're not familiar with using GitHub.
Also chatted about the Brid.gy profile issue. Thinking was using the new build would clear it up. Barring that, use the profile URL for both OwnYourGram & Brid.gy
Armed with this we try again.
So we’re cutting down on the immediate issues, but still big hurdles.
Consensus is the WP importer still doesn’t work, so I’m going to add my WP blog back on /blog, using the exported .XML to return all my content. That way I’ll have it there at least, links won’t remain broken, and everything new will be on the Known blog going forward.
Day three, here we come.
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...
Before deleting/installing/moving anything I:
Feeling fairly secure I had everything I proceeded.
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.
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://
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.
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:
Not terrible, but not where I wanted to be. On to day two.
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.
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.