I now see what I have been doing wrong. I had the Save setting to Save Draft, but when I close the editor, I was clicking on the Publish button in an attempt to publish as a draft post. I now realise that I do not need to select Publish from the editor. The post is saved regularly as a draft post and I can preview and amend as I do now.
So I now need to work on updating my skills to learn this new ‘Block’ editor. I don’t think I’m going to drop Open Live Writer as an editor, but I think I need an additional string to my blogging bow. It’s funny, I originally started using the WordPress editor before moving to Microsoft’s Windows Live Editor which was part of the Windows Essentials software. When this deprecated, I tried using the blog template in Microsoft Word before I found the open source software ‘ Open Live Writer ‘. So in a fashion, I have come full circle.
My thank must go to @themagicrobot who’s response in the WordPress Support Forums showed me the error of my ways.
I’ve heard a bit about Gutenberg, the new WordPress editor so I thought I would give it a go. “Be bold.” I said to myself, “Don’t get in a rut” and a few other motivational phrases that I don’t want to go into.
My first impression was that it had a quite confusing interface, and I found switching from what they call “Block” and “Document” to add a tag or category, very frustrating. I like to add tags as and when they appear in my text. Then there is the text formatting which seems to be missing ‘full justify’ which is how I usually format my words. Embedding an image within a paragraph does not seem to work. There may be a way to do it, but I could not see how. I didn’t seem to be able to post my words as a draft post. Although I selected ‘pending’ as an option the post went live (now deleted). All in all, unless WordPress are prepared to give us a full tutorial, then I’m going to sit in my rut like the cowardly lion and stick to what I know. It’s the same feeling I had when Windows Live Writer was withdrawn (before I found Open Live Writer) and I tried using Microsoft Word to write a post. I would possibly get used to it, but in the end, is it worth the stress of change?
I can quite see, that WordPress might want everyone to eventually use Gutenberg, but until then, I’ll stick to Open Live Writer.
Still testing the Blogpad app on my iPad. A bit of a way to go yet, but I’m starting to get the hang of it. One of the downsides I’ve found, is that you cannot post your missives (is that what I mean?) as a draft in your WordPress blog. Well I’ve not found a way, if there is one. The way it works is that it is stored as a draft in your defined storage area. You can then ‘preview’ your work and see how it looks, before finally publishing it as a live post. Another downside seems to be the ‘autosave’. I can’t find a setting that sets the autosave frequency. I discovered, to my cost when the app crashed, that the crash happened before the ‘autosave’ kicked in, so I lost a good portion of the post. I’ve now decided to click/tap on the Save icon every 20 words or so.
This app is not going to be my main blogging editor, I’m still firm friends with Open Live Writer, but I needed something to work with when I go on holidays. Don’t want to take the laptop with me (K*** would kill me if I did) and as I have mentioned before, I’m not too keen on the WordPress built in editor. At the moment, there are more ‘up-sides’ than ‘down-sides’ to the app, although I’m not liable to have a tantrum, I just hope ‘up-sides’ continue to grow faster than the ‘down-sides’.
I’m still having an issue with the WordPress app on the iPad. When I’m in the ‘stats’ screen and I click on the Notification Bell at the bottom right of the iPad app, the notification list comes up as normal. Now the issue is, that if I tap the Daily Prompt notification, I get a very unhelpful message telling me that there has been an ‘Error Loading The Post’. I hadn’t noticed this before, it’s only since I have been having a go at the Daily Prompt that the iPad app has become more active. Anyway, the good people in support are looking at the issue and I am hopeful they can come up with the solution.