My mistake — 8 Comments

  1. Bother! So now I suppose I’ll just have to install the silly thing again just because what’s left of my obsession with all things that are “works in progress” is beating a tattoo on my little brain–or what’s left of it. Probably after I mow the lawn. That is if I actually feel like mowing the lawn. What I really should be doing is backing up my wife’s computer before updating to Mint 19 (and those blasted Window 7 updates on the other partition).

    • Stop moaning and just deactivate it next time.  Just reactivate it when you feel the need to disimprove your mood.

      And delete that Windows 7 partition – that’ll save a few hours a day of updates and virus scanning.

      • And delete that Windows 7 partition – that’ll save a few hours a day of updates and virus scanning.

        And die a horrible death at the hands of my wife? No sirree. I have plans for whatever future I may yet have and it does not include a knife embedded somewhere fatal or worse. Besides, She’ll be forced to give it up once 2020 comes around anyway. By that time it will be well past the time to replace our rather elderly machines.
        You know, I do believe that I left Gutenberg installed but deactivated. The moaning comes from two nights with no sleep to speak of. Makes me grumpy grumpier than usual.

  2. This Gutenberg thing seems to be a big PITA for being just a glorified text editor.  Gone are the days of edlin.

  3. Right. Totally forgot about browser extensions when I compiled a list of known issues. I had to disable quite a few on Chrome. Now I mostly use a clean Firefox Developer edition when editing posts on Gutenberg Times. What was your ‘little browser program” that scared the Gutenberg away?

    • This browser extension is your nightmare!  It’s a yoke called Stylus [a Firefox addon] that allows me to apply my own CSS to external websites [overriding their own CSS].  As you can imagine, any errors it throws up are entirely my own.

      What concerns me more is the Preview screen.  It just sits there politely doing nothing.  That means that I have to go straight from Edit to Live and then proofread from there.  That caused problems as I had some difficulty with a Blockquote which insisted on stripping all paragraphs to NewLines which made reading difficult.  I had to experiment on the published page which I don’t like doing.

      • There are already issues in Github about that… There is some auto-saving going on that can get in the way of itself… And when I run into the preview ‘spinning its wheels’ issue, I go back to the edit screen and click on the “Save Draft” button. Most of the time that finishes the saving part, it otherwise tries to do by its own… and displays a preview. It seems that your set-up is so much different from mine, so this might not work for you. Let em know what happens:-) 

        • I have just run a load of tests.  It appears to be a problem with my theme – Weaver  Xtreme V4.0.5 as the Preview works perfectly under Twenty Fifteen.  This will be a problem for me as I run that theme on a dozen or more sites!  The theme authors however claim that it’s fully Gutenberg compliant.  Looks like I’ll have to do some more poking around………

Hosted by Curratech Blog Hosting