FOLLOWER ALERT: Moving to a New Blog

As I mentioned in an earlier post,  WP’s massive move to enforce their block editor, which nobody seems to like and which I hate with a vengeance, made me decide to go “self-hosted” in order to be able to continue using the classic editor without having to remember to select it every time I’m creating or accessing a post (and even that selection switch is clearly a disfavored option on these days, so it’s bound to disappear entirely at some point).

I’ve been building the new blog in the past two months and am now ready to officially make the move there.  The address is:

The blog name — Lioness at Large — is going to remain the same, and It’s still a blog using the WP functionality, so you can continue following me using the WP Reader (or follow me by email, of course; just input your email address into the form at the top of the sidebar to the right).  And this present blog ( is not going to disappear; I’m going to keep it as my archive of my past blogging activity.

I’ve switched to a different template for the new blog, however, not only in order to keep the two blogs’ posts distinguishable, but also because the new template allows me more editing options than the one I’m using for this blog.  Then again, for purposes of recognizability I will continue to use — at least for the time being — this blog’s  header showing the Lioness at Large blog title, and also the lioness images on the front page.

To get things started, I’ve seeded the new blog with my posts relating to another reading (and lifestyle) game that my previous blogging community, BookLikes, has enjoyed playing in November and December for the past several years, and which we’ve continued to play this year in our new (private) home, The 24 Tasks of the Festive Season (or simply Festive Tasks, for short): my Master Update Post with links to all individual posts is HERE.

I have also imported most of my posts, pages, and project pages from this blog to the new one; many of these, however, still require some sprucing up, so please be patient if you should run into something that’s not quite working as it should be yet.

I very much hope I’ll be able to welcome most of you in my new blogging home — thank you again for your friendship in the past and present!  Here’s to many more great exchanges on books and other topics in the future.



18 thoughts on “FOLLOWER ALERT: Moving to a New Blog

    • ThemisAthena says:

      Thanks. I don‘t hope WP implodes, but I hope the block editor will explode on them at some point …

      And I hope someone will be able to sort out my https protocol issue on the new blog, because if it‘s really a systems thing, I won’t be able to fix it alone. 😦

      Liked by 1 person

  1. cathyc says:

    Are you finding it hard setting up at .org? I’d like to do that, but it seems like a lot of work. At the same time, I also am trying to find alternatives to

    Liked by 1 person

    • ThemisAthena says: turned out to be by far the easiest alternative to; chiefly because you can go on using the same functionalities, even if you have to redefine your basic blog settings from scratch. But it‘s easy to import / move your existing content from one blog to the other, even if it may take several goes for the system to grab it all if there‘s a lot of content (and if you‘re using a different template, some of the posts may need some tender love and care to make them look pretty again).

      Also, it‘s worth noting that some of the things that are part of the basic setup in (such as portfolio / project pages / posts) have to be added by way of plugins in (Then again, there are more (free) plugins available as part of than you can possibly ever use … and virtually none of them exists in

      I took a look at Blogger and a bunch of other hosting service before settling on, but none seemed to meet my needs remotely as well, so here we are. WP is far from perfect, but unless they do something monumentally stupid (such as also trying to enforce that d**d block editor in, I think I‘ll be staying here … not least because I‘ve put a considerable amount of time not only into setting up my blog(s), but also into configuring my Reader so that I‘m reasonably sure I‘m seeing all the posts I‘m really interested in. On a related note, many of my friends are on WP, too, so this is by far the most convenient way of staying in touch with them … and actually commenting on their posts (whereas I can only read post on other sites — though of course, at least being able to read those posts, even without an easy comment option, is still vastly better than not being able to follow friends on other platforms at all).


    • ThemisAthena says:

      Good luck with your move whenever the time comes, and thanks for following my new blog. I‘m still in the throes of getting organized, but the new year‘s first couple of posts should hopefully go live soon.

      Liked by 1 person

    • ThemisAthena says:

      For blogging / online reviewing purposes TA, though it no longer matters quite as much these days (not least in light of the fact that the GDPR leaves me little choice but to reveal my ID on my privacy policy anyway — also, if my copyright notations are to have any weight at all, I feel safer in claiming my rights under my own name).

      Themis-Athena was an alias I adopted in the early days of the internet after having been warned, in the nick of time, off a hacker intent on stealing my (and other people‘s) IDs — the hurriedly-adopted screen name gave me just about the time window I needed to change my credit & debit card numbers, etc. I then kept it, in part because back then this sort of thing really was still a fairly effective shield (and I obviously had zero appetite for a repeat performance); and in part because over time it became the closest thing to a recognizable trademark in blogging and reviewer circles that a screen name can possibly be. To my friends and in email etc. I am of course Ulrike, though, so do please feel free to use either — and thank you for asking!!

      As for blogging, I‘m still using the WP system … just on my own site now (the service that hosts my professional website has an option allowing you to manage the domain “as such“ and everything it entails through them, and the creative part (web design, content, etc.) using the WP tools … sans the blasted block editor, which you can disable and replace by the classic editor (guess what was the first thing I did)! 😀 Fingers crossed the move will pay off in the end.

      Liked by 2 people

      • Ola G says:

        Thank you for your kind explanation! 😀 I do love your alias, for what it’s worth – Themis is by far my favorite Greek goddess 😉

        So does this mean I need to follow you again or will the current setup work? I visited your site but see only email subscription option there…

        Liked by 1 person

      • ThemisAthena says:

        I think you should be able to follow the new blog by way of the same WP prompts (on the blog itself or in your Reader) as for a blog. Or just enter the URL in the “sites I want to follow“ bar at the top of your Reader‘s “manage followings / subscriptions“ page … I hope it works, it seems to have done for everybody else!

        Tbh, my screen name was a spur of the moment, knee jerk kind of choice — but having loved Greek mythology since I was a kid, I really didn‘t have far to look. (Other kids‘ first superheroes were Superman, Batman or Wonder Woman … mine were Athena and Odysseus.) So Athena was a given, my day job supplied Themis, and Pallas Athena suggested combining the two. Though there was a secret pun directed at the hacker, too, as she was operating under a fake Greek alias herself. (“You think you can out-Greek me? We‘ll see about that, lady …“) Anyway, I‘m glad you like it! 😃

        Liked by 1 person

      • cathyc says:

        I was wondering re your comment that you can disable block and keep classic as the default by moving to .org: won’t the classic still need to be maintained? Is there any guarantee that it will be?

        And also, if you are with .org, did you get one of WP’s recommendations to host it or find something you preferred?


        Liked by 1 person

      • ThemisAthena says:

        My domain (URL) is hosted by the same company that also hosts the domain of my office website — when researching options before making the switch, I found out that they offer an option (for a mere song) where they host the domain and then let you use tools for editing. So that‘s what I signed up for. (This, inter alia, also lets me go on using the WP Reader.)

        On, most things work via plugins — and one of those permanently disables the block editor and replaces it with the classic editor, which is actually integrated into the „behind the scenes“ editing features of your blog. So the classic editor is the *only* editing tool I‘m using, and for good measure it‘s also downloaded to my computer — i.e., I can restore it even in the event that WP should mess up and try to foist the block editor on me again after all.


    • ThemisAthena says:

      I know. I think that‘s temporary — they‘ll do away with it once the amount of people who have either accepted the block editor or moved to WP-dot-com (i.e., WP’s paying services) has reached critical mass. I didn‘t much feel like frantically scrambling for a workable solution at the very last minute, so I decided to set up anew, self-hosted, while there‘s still time to use the classic editor (even if it‘s already a disfavored option now) to the extent necessary in synching the two blogs‘ existing / transferred content.

      That all being said, thank you for actually *reading* and responding to this post! 😀


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.