KTS915

Thank you for addressing this!

Wow! You are fast!

Thanks, that works perfectly!

Thank you — and thank you for the plugin!

Because normal people who write things don’t do that and don’t want to do that?

Perhaps so. But why, then, would they want to type a slash and a set of letters instead?

@wickywills,

Sorry but I don’t understand the points you raise here. Surely the point of a good editor is to avoid having to hard code your posts, is it not?

It might be. But neither the current/classic editor in visual mode nor Gutenberg achieve anything like 100% accuracy, so @sakyant’s point that “nothing will ever be superior to the control one has when hard coding one’s posts” remains 100% valid.

Savvy Gutenberg supporters point out that you can use a slash and a few letters to pick the next “block”. But how is that superior to (or shorter than) simply writing <p> and </p> to enclose a paragraph? Clearly, it isn’t. And hardcoding the html is guaranteed to produce the right results every time, which neither Gutenberg nor classic in visual mode can claim.

I’d also point out that there are plenty of great rich text editors around for the desktop that don’t require the user to type the html tags, but which insert them automatically with 100% reliability. So the writer can compose content with one of them and then just copy and paste that text into WordPress. But that, of course, is only possible if WordPress provides a mode that is guaranteed not to make a mess of what is already perfect html. Gutenberg provides no such guarantee.

Blocks are movable. Writers often want to move paragraph when editing article. Moving element is a lot easier and precise.

Actually, writers often want to move a chunk when editing, and this is exponentially more difficult in Gutenberg than in the current editor.

A chunk is not necessarily a paragraph. It is a passage of any length or content, defined by the writer for any given chunk. So I might have one chunk with three paragraphs; another with four and an image; another with two and two images, etc. In the current editor I can move such chunks with a simple copy-and-paste.

Now try moving such a chunk with Gutenberg. Clue: you can’t. Instead, you have to move stuff paragraph by paragraph (and also move each image separately because each image has its own block). That’s a nightmare.

Even apart from all Gutenberg’s other shortcomings — and there are many — this alone makes it hopeless for writing anything but a short blog post.

@lonelyvegan,

Just so you know, all those wonderful comments pollute the REST API by adding newlines all over the place. ??

But that’s what happens when you don’t do the thing properly and use JSON instead.

Gutenberg is simply a rich text editor – that’s it.

Actually, that’s not it. It’s barely even close.

The only real difference I can see is in the UI. Nothing more.

Wrong again!

@ziogio98, you really shouldn’t hijack someone else’s thread to say stuff that’s quite wrong. The whole architecture of Gutenberg is different: that’s the point.

@bleazymatt, sorry for trespassing on your thread.

Change line 146 to this:

	  $new_excerpt_more = function($more) {
		  return '...';
	  };

Then change line 150 (now line 152) to this:

	  $new_excerpt_length = function($length) {
		  return $excerpt_length;
	  };

Rick,

You are joking, aren’t you? Or perhaps you haven’t actually looked at the code?

Gutenberg’s architecture is built on HTML comments, for goodness’ sake. There is no way that that is going to give it a good name among devs. It’s like going back to the 1990s.

That architecture is also why so many people report that Gutenberg trashes their sites. It’s pretty much inevitable. What’s under the hood is simply incapable of doing the job being asked of it.

Thank you!

There are also a couple of uses of create_function in a code block beginning on line 47 of s2member-secure-file-browser/s2member-secure-file-browser.php, so that these lines:

	if ( ! version_compare( PHP_VERSION , PSK_S2MSFB_MIN_PHP_VERSION , ">=" ) ) {
		add_action( "all_admin_notices" , create_function( '' , 'echo \'<div class="error fade"><p>You need PHP v\' . PSK_S2MSFB_MIN_PHP_VERSION . \'+ to use \' . PSK_S2MSFB_NAME . \'.</p></div>\';' ) );
	} else if ( ! version_compare( get_bloginfo( "version" ) , PSK_S2MSFB_MIN_WP_VERSION , ">=" ) ) {
		add_action( "all_admin_notices" , create_function( '' , 'echo \'<div class="error fade"><p>You need WordPress? v\' . PSK_S2MSFB_MIN_WP_VERSION . \'+ to use \' . PSK_S2MSFB_NAME . \'.</p></div>\';' ) );
	} else {

should be changed to these:

	if ( ! version_compare( PHP_VERSION , PSK_S2MSFB_MIN_PHP_VERSION , ">=" ) ) {
		add_action( "all_admin_notices" , function() {
			echo '<div class="error fade"><p>You need PHP v' . PSK_S2MSFB_MIN_PHP_VERSION . '+ to use ' . PSK_S2MSFB_NAME . '.</p></div>';
		} );
	} else if ( ! version_compare( get_bloginfo( "version" ) , PSK_S2MSFB_MIN_WP_VERSION , ">=" ) ) {
		add_action( "all_admin_notices" , function() {
			echo '<div class="error fade"><p>You need WordPress? v' . PSK_S2MSFB_MIN_WP_VERSION . '+ to use ' . PSK_S2MSFB_NAME . '.</p></div>';
		} );
	} else {

Are you doing anything to disable the REST API?

Yes, on that site I was. Reactivating the REST API has solved the issue on the General tab. Thanks!

This does, of course, illustrate why a changelog is so helpful. You weren’t using the REST API for that before, so I had no idea what I should be looking for.

Thanks again!

I’ll email [email protected]. This shouldn’t be happening.

You might have a good point there. I have another plugin whose changelog is also not up to date.

I am using WP 4.9.2 on Firefox 58.0.

This issue is widespread, I suspect, because it’s not a transient issue. If you go to the link (shown on https://imgur.com/S59dNWO) that says “View version 7.0.0” the changelog starts with 6.4.8. There is no reference to 7.0.0.

This is particularly problematic because, on the one (test) site I updated despite the lack of changelog, the General tab on the Manage Updates page never loads properly. I just get the animated GIF. The browser Console reports this:

Error: Given action "FETCH_OPTIONS", reducer "options" returned undefined. To ignore an action, you must explicitly return the previous state. If you want this reducer to hold no value, you can return null instead of undefined. admin.js:28:9849