Category: meta

Themes

Update below, maybe WordPress isn’t so bad after all?

I broke my WordPress self-hosted/managed site earlier simply by installing a theme, the one named ‘Default’.

The hosts’s AI troubleshooter failed miserably to make any form of difference when I started it.

To fix it ‘manually’ I first attempted to follow the help page linked to in the error message – go into myPHP and deactivate all the plugins.

Nope.

So then I searched for help directly related to WordPress themes and found the way to fix it is to delete the offending theme folder and rename an existing folder to the offending one.

Success, and I felt lucky I knew which theme was active.

And even more luckily everything is back up again.

My hosting plan includes only weekly automatic backups so yes, I just started one now.

Painful isn’t it, how something so complex can be broken by something so apparently simple as a site theme change.

Anyway, I just looked for similar issues with it and eventually arrived at the WordPress.org forum. The only response i found to its incompatibility with a previous version of PHP was the original poster replying to their own post to make a technical change within the theme file definition.

Pointless reporting it if there’s nowhere to report it, so I’ve given up and I’m sticking with ‘Simple Grey’.

Update: While attempting to fix my site I was sent an email from WordPress, “@bazbt3 🏡 Your Site is Experiencing a Technical Issue”. I was busy so didn’t notice it. The email described the fault and contained a special link to bypass the dashboard I couldn’t access – to enter a “special recovery mode”. Maybe now I know this is a thing, the next time the site breaks I’ll be more patient?

Micro.blog initial issues

I’ve had a few fairly fundamental issues since setting up my custom domain on Micro.blog. Though my username is discoverable on Mastodon (Appdot.net) and the blog works at bt3.com with all links looking good, quite a few are concerning me.

I’ve asked for help via help@micro.blog, when they can spare the time, and I’ve posted this here not to whinge about it but so I remember how things started before I start messing about with CSS, styling my blog. 😱

Ok, the list:

  • Posts no longer automatically appear in my Micro.blog timeline.
  • Neither blog posts nor RSS feeds automatically crosspost to Mastodon, I have either to crosspost from ‘Pages’ or refresh feeds manually on the ‘Sources/Feeds’ page.
  • The comments box under posts is completely absent.
  • None of the comments made by me and others on Micro.blog or Mastodon before or after I set up the domain are visibly linked below the posts. They’re in the timeline though.
  • My custom 404 page does not display when I test by creating a non-existent URL. It’s the same for both the 404.html and the page at layouts/404.html – in a custom theme based under ‘Marfa’ or others, and edited wholly from the ‘Design’ page. Here’s the design I’ve used on both: https://bt3.com/404.html/ (a work in progress).

I’ve checked through the Help pages too, and this isn’t unusual.

Bluesky

I’m sure it’s just me but I can’t summon up the enthusiasm to continue even to crosspost to the Bluesky site. Why? Well, 2 reasons. My social home is the Mastodon-based appdot.net, and now I’ve tried Micro.blog I cannot decide between my self-hosted WordPress blog and one at Micro.blog.

I’m using Bluesky to pull together a few sports reporters and social accounts recently moved from Twitter/X. And that’s all.

The social aspect of being able to blog at Micro.blog and have replies in-line with the posts is compelling. However I’ve been using WordPress for some years now and I’m comfortable with it, but the official plugin linking it to Mastodon simply didn’t work for me. And if I’ve got this right I can continue with the WordPress blog and have it imported to Micro.blog – magic! I know it’s one-way so if I post to Micro.blog it won’t appear in the WordPress blog, but hey, do I care?

Not really.

So what’s next? A todo list:

  • I’ve turned off crossposting to Bluesky.
  • I need to unfollow the ‘Bridgy Fed’ bot to terminate the link between appdot.net and Bluesky.
  • I’ll probably add text in my Bluesky bio to mark it ‘read-only’.
  • I’m definitely going to experiment with retaining a link between my WordPress blog and the Micro.blog site for the duration of the free trial. At least hoping it’s automatic.
  • I’m unlikely to link my domain with Micro.blog within the trial period, even though it’s recommended to do it.

I’m so glad I’ve chosen to think about this over the weekend, it’s bordering on an obsession this trying to find out how things work.

Social sharing

Here’s the first automatic blog post to Mastodon with, I hope, restricted commenting features. (I removed the ability to comment some time ago, so I’m not sure what will happen next. I hope it means comments stay on Mastodon).

Basic security

One of the basic requirements of me using the free ‘IP2Location’ WordPress plugin for my blog is that its authors ask for attribution, which is fair. So here it is:

I just installed and configured the country blocking plugin from https://www.ip2location.com. I found it after a quick web search led me to this page: https://blog.hubspot.com/website/wordpress-plugin-to-block-countries.

The setup procedure is pretty simple: install it from the WordPress dashboard, sign up for a free account at IP2Location to install the database and stuff, and setup the block rules for countries or IP addresses.

An AI-generated monochrome image of a 1980s home computer on fire. Now if one owned such a beast of a computer it's likely one was very serious indeed about computing. I was. One PC had a 'Matrox Millennium' graphics card with an unimaginably vast 4 megabytes of video RAM.

(I didn’t want to pay Wordfence to extend their so-far excellent monitoring and blocking service, at least not yet).

DEVONthink

I’ve moved all of my notes and bookmarks from the Obsidian writing/knowledgebase app into the similar DEVONthink document manager.

Although I’ve known of it for years I’ve resisted DEVONthink mainly because of its cost.

Over those years I’ve spent time with Microsoft OneNote (cross-platform & web), Drafts (iOS & Mac) and Obsidian (cross-platform). But, just as for personal use I’ve previously moved from the Omnifocus task manager to pretty much everything else – and always back again – I have the feeling I should probably have trialled this when I first found it.

One of DEVONthink’s strengths is its ability to simultaneously synchronise with a number of document stores. I’m considering (if my shared web hosting plan allows) attempting to store one copy as WEBDAV, with one in a Dropbox folder.

At least there’s no appreciable lag using iCloud – opening Obsidian could take literal minutes.

And I’m collecting RSS feeds into it instead of using a dedicated reader. RSS, yeah.

Obsidian

[!Info]
This is a test of the Obsidian to WordPress plugin.

I’ve been using a really great notes app called Drafts on my iPhones since 2013, and lately on my Mac.

Someone I know on Mastodon mentioned a couple of days ago that they were taking a fresh look at another notes app/service called Obsidian.

Obsidian doesn’t keep all the notes in one file like Drafts, it instead saves in plain text files – in my case I’ve chosen to save as Markdown – and enables the creation of links between any number of files. Drafts does it too, but it’s an app with less scope and file portability.

Obsidian works on multiple platforms whereas Drafts appears only on Apple hardware. I’m using it in Apple hardware but it can be installed on Androids, Linux and Windows.

Links:

#blog , #write

Migration v2

I'm transferring Markdown blog posts from my GitHub Pages repository (repo) into my WordPress blog, this way:

  • Open MWeb for iOS (a Markdown editor with publishing capability.)
  • Make _posts and _images folders and copy all the posts and images from my local copy of the repo into each.
  • Open each post in MWeb.
  • Check for links to old blogs:
    • If none found then strip the YAML post header, ensure the post date matches the original and publish to WordPress.
    • If links found, hold until later and publish the earlier, link-free posts first.
    • I also attempt to use the original post date but know I've failed on at least a couple of occasions. It's not massively important.

Blog posts to migrate:

Date Remaining
2019-04-06 360
2019-04-10 207
2019-04-12 187
2019-04-15 117
2019-04-22 57
2019-04-27 16

(Table updates at various milestones.)