The Productive Creative


Tag: Wordpress

  • My WordPress Issues List

    Of all the wordpress hosts I’ve tried, I’m happiest with But I’m accumulating speed bumps as I build this website, and I want somewhere to track them. So here it will be.

    I want to succeed and if is great then that helps me. So I’ll list my issues and attempts to resolve them here with a positive intention. It also helps if I can explain the issue without having to write all the detail into support chat.

    So I’m not a complainer and maybe each issue here will end up with a workaround or a fix and it will be an empty post.

    Off we go…

    1. The floating Edit button bar – missing in action

    The floating Edit button bar – missing in action

    I’m on a block theme. In theory, when I’m logged in and looking at the site front end, there should be a little floating toolbar of buttons: Edit Site; Edit; …

    This only appears sometimes. Usually I have to scroll to the bottom of the post or page to make it appear. This is a pain for long postsl

    Sometimes, it never appears, even when I scroll up and down to try to jog it into existence.

    Worse, my other site is on the Business Plan. It’s been confirmed to me by a Happiness Engineer that it will never appear on my site because it has active plugins. Those plugins were installed by when I transferred to the business plan. So the edit bar will never display. What’s worse is that the default theme for 2023, called Twenty Twenty Three, doesn’t display an Edit link on posts and pages as we’re used to seeing. Presumably this was a decision made by the team on the assumption that the edit bar would do this job.

    On the Business Plan site, the happiness engineer helped me install a piece of code that would replace the header bar with the wp-admin one. There I could access the Edit Post button. Actually, this is better than the modern floating Edit bar because it also has an edit button when I’m viewing a tag or category.


  • Bringing My Blog Back To

    Bringing My Blog Back To

    I started with Then I tried self-hosting, and finally returned to

    I started with because it was free to start. I knew I could move onto self-hosted wordpress when I was ready.

    I have a technical background including software development, but not in web development. So it was natural for me to see the opportunities of doing clever things with websites. Because of this, I let myself be tempted into the world of self-hosting, multiple plugins, and the potential to tweak the code.

    The push away from came from the lack of a staging environment. I noticed this when I was trying different themes.

    It’s hard to find out what a change in theme is going to do to your website. The customizer demo gives you a small glimpse of what the changes might look like, and it isn’t accurate. Themes are generally not well documented. Yet they have a huge impact on all the elements of content and also the available features.

    I chose Hostek as my first host for a self-hosted wordpress site. They were cheap and allowed an unlimited number of websites. I could quickly create a clone of my site, apply theme changes, review the whole site, then delete the clone. However, there were concerns with downtime and getting Jetpack Backup to stay connected via FTP.

    I tried Pressable as an opposite to cheap hosting. They use the same infrastructure as, so the downtime should be resolved, and their Jetpack Backup was sure to remain connected. Plus they allow you to create a staging website. However, I got frustrated with the included backup being just a daily backup, and it was expensive given this was a new blog with no visitors.

    So then I had a go with BlueHost. They have a cheap plan, allow for a staging site, and are often recommended in the wordpress world. What a complicated mess! The regular wordpress setup features were all over the place and every new website comes bloated with lots of auto-updating plugins. I killed this plan after 24 hours.

    This is when I realised that I had been pulled into a distraction. I was spending all of this time fixing technology problems when I should really be focused on learning to write a blog. I thought of myself as a techy person rather than identifying as a writer.

    So I killed my self-hosted sites and returned to It’s simpler and I’m taking up the challenge of becoming a writer. When I want to try another theme, I’ll create a free site, export my content into it, and use that as a staging site to test the theme.

    Sometimes I follow a long path to get back to where I started, to take up the real challenge, writing, rather than the comfortable one.