nelsonbase

Hi Frank,

In my opinion, it’s good practice (optimization wise) to minimize outside dependencies like that, because even with big providers like Google you can sometimes encounter slowness or non-responsiveness. Of course, you have made it optional, which is good.

I think the critical issue here (in this case) is that i was unaware of it and the option was off until the client saw a notice in the backend, explored the option, and apparently enabled it. However, when i went in to check, there was a yellow notice box warning that there were no more Shortpixel credits available (or something like that) – so basically the feature was broken in some way and that’s probably why it was really really slow to load (probably timing out or something).

The client had no idea that some relationship (apparently) had to be established with Shortpixel in order to use the feature, and they were not aware that it would break things if they simply checked the option and left it at that. This is definitely not user friendly.

AO has always been impeccable, but i think this hurts its reputation.

Take care,
Shanna

Item no. 1 is not resolved

Item no. 2 is resolved

Item no. 3 is not resolved

I was just trying it again and thought that the preview was hanging, but didn’t close the window and eventually it did work – just took a long time, maybe 10 seconds. I wasn’t expecting it to be so long so wasn’t waiting long enough.

I believe with an earlier version it really was hanging, but not sure i’m seeing evidence of that now. Will let you know if it actually hangs any more.

Here’s how you can reproduce what i’m talking about.

Open up the Sample Page in Gutenberg. Switch to the code editor. Insert blank lines between the paragraphs and blockquotes. I always put space between blocks to make it easier to read when i’m editing.

Now simply click the preview or update button and watch that space get removed.

Hi Marius –

I think the general concept of using a classic editor block as the default is a good one, but the implementation is less than ideal. There would probably be a lot fewer complaints if all the functionality of the classic editor (with some exceptions) remained available when it’s being used in a block – notably the ability to insert images (including in the code editor).

Having GB block wrappers show up in the code editor is not a show stopper, but losing whitespace creates a significant usability problem.

I’m not happy with the current state of Gutenberg because it gets hugely in the way of productivity. What it would take for me to adopt it is for all of the current functionality of the classic editor to remain available and for blocks to be optionally available as extra functionality for quickly creating more complex content – using Gutenberg only as a content templating system and not trying to shoehorn traditional word processing functionality into blocks.

For me the concept of using a block to basically just create an HTML tag is ridiculously dysfunctional. Using blocks for headings, paragraphs, blockquotes, and lists is overkill and inferior to traditional ways of inserting such content.

There may be a good case for using image blocks because it makes possible separate instances of image meta data like captions, but removing word-processor-style image insertion breaks backward compatiility.

I concede however that it may be better functionality to create and manipulate compound tags like tables using blocks.

I’m not using any browser extensions.

I’ve noticed from time to time that “generating preview” hangs like this, but most times it seems to work. Maybe it’s just a timing problem? (not waiting long enough for the save to complete or something…)

Hi Marius,

I tried this again and switching from visual to code editor is no longer causing the notice, however i do still get it when i open post attributes and open the dropdown list to look at it (without selecting anything). Then when i try to leave the page, without having made any changes, i will get the notice popup.

Windows 10 x64 with Firefox 54

@catchlight – Yeh, i didn’t notice the stars feature and wondered about that afterward. How i would rate GB in the big picture really depends on the politics of implementation more than how it functions at the moment, which seems somewhat unpolished but will probably improve. Thinking about this now, although i have complaints about shortcomings i will still give it 5 stars because it’s clear that this is a big challenge and the developers are (let’s presume) trying really hard to find common ground among users.

The only problem that i’ve found is if you’re using the code editor Gutenberg removes some whitespace, making it harder to read. The visual editor seems fine. But this little inconvenience does not in any way destroy your pre-existing content, as long as you don’t convert it to blocks (my experience with that was not very good).

I just posted on this, not seeing the present post. This is definitely a hidden feature, not something that i’d ever have found without being told where to look. I’m wondering what was wrong with where it is in pre-GB WordPress?

Also, for the developers, if you invoke this feature when there’s a message bar at the top of the page that bar partially covers the permalink and completely covers the edit button (desktop, about 1200 px wide).

Also, when i first clicked on the edit (permalink) button, the whole thing disappeared and i had to click the title again. Ah… now i see that it seems to be intended to be hidden as soon as you focus anywhere else, although i didn’t think that i had done that.

And finally – this is quite problematic – when i finally get the permalink to edit it is URL encoded, so i cannot actually edit it but instead have to type or paste in the whole permalink (it may work passably with Roman characters but not in other alphabets like Cyrillic, Chinese, etc.)

More… I just tried putting the code into a custom HTML block and it remains as i put it, without getting changed by the editor. Maybe if the editor is set to the code editor the default block type could be custom HTML instead of Classic? Something to think about.

Something is quirky here though, because after i’ve created some code in a custom HTML block, if i remove the block tags then the block reverts to Classic, and after that my code does not get modified when saving of switching between code and visual. Not very consistent behavior.

I have a similar question, as it appears that the aforementioned backward compatibility actually does not exist. With Gutenberg in a Classic block you can no longer add media the old way but instead have to switch to visual editing, add the image at the end of the text, then switch to code editing and move it where you want. This is not how it happens now (pre-Gutenberg) in the code editor, where all you had to do is click the add media button and insert the image where you want it.

Not trying to hijack this post, just correcting the backward compatibility comment above. It would be nice to have this fixed, so we don’t lose long-standing functionality.

My apologies … looks like the ultimate cause of this is that the WordPress draft privacy page is all smushed together out of the box, unlike the sample or hello world pages. The problem does not seem to be Gutenberg.

Oops… It seems that the problem actually still exists, but if you simply switch to the visual editor then switch back to the code editor then the page is a lot more readable. The smushing together of everything seems to only happen when WP converts a page to Gutenberg, so this is probably not a big deal as long as there’s a way to fix it (although just how to fix it is not obvious).

another example… i went in to edit the hello world page, switched from the code editor to the visual editor, then went to leave the editor page and again got the “this page is asking you…” notice

no changes of any kind were made to the content