Little niggles that need fixing

This is the second attempt at this blog post ... first one failed to save :(

So the first little niggle is to fix the holes in Bitweaver that resulted in loosing the first attempt. These are caused by a combination of things all of which are slated as 'improvements', but in many cases they are simply change for changes sake. While some changes are described as fixing security problems, the fixes tend to cause further problems that require further changes. The Firefox would not display my websites at all initially because the browser decided they were a security risk is just crass. OK fixing what it was complaining about was not too difficult, and at least Let's Encrypt avoids costs that in the past reached triple figures, but let US decide if we want to look at a site and I don't need a certificate for sites I am working on in development mode inside my own network.

So why did the previous post fail to save? 'Security Violation', but just what I'm not quite sure. The new post worked fine, so I assume it had something to do with the time I'd been working on the previous one. Something had timed out in the meantime. So lets work in stages and save more often. I know there is a niggle in the initial post code which fails to return the new id following the initial save and one has to update it manually to return to the page. Once created, the edit button works fine ... so I need to update the bug list to flag what needs doing and I'll start a wiki page to document the rants that I'd originally voiced. Just updated them with a number of areas I need to develop, but even more still to document.

Now why was this new post not showing top of the blog list? Something else to investigate ... do I really want to move to other packages to manage this material?