Torgut

Always ON, Password,
XML-RPC API ON
Bot protection ON
Authentication log OFF
Signature OFF

Ok, thanks. I edited my original review. By the way… is there any chance that this plugin had messed up with my Jetpack? Because – coincidence, perhaps – the day I installed it, my Jetpack stopped communicating xmlrpc.php. Just asking, who knows…. ??

No I didn’t. Frankly, didn’t even cross my mind that would be necessary. And now that you mention it, really sounds and extra unnecessary step. I mean, if the draft was dragged to a specific day it means we want it published that day. I will try it later, but isn’t there a way to change that default?

Hey Zack, sorry, I thought you were not supporting the plugin anymore, that’s why I didn’t start by leaving a post in the support forums.

The date is correct but the status of the post is still draft:

Status: Draft
Visibility: Public
Schedule for: Dec 29, 2017 @ 14:52

So, it seems that the fact the status is not changed from Draft to Scheduled is blocking the publishing. I guess.

As far as I know I don’t use any other plugin changing post schedules.

Amen

OK… for me it was… actually in some of my installations I didn’t even update.

Nop, definitely now… I did further tests, and it’s not the plugin fault. I installed a clean installation of WP. With the default theme it works OK. When I switch to my theme, the problem starts.

I am having the same issue (the second mentioned bt the OP) in a clean installation of WordPress. The first one with WP 4.6, which rings an alarm bell. What is interesting is that the plugins are actually installed.

OK… this was the issue. Fixed:

https://wordpress.stackexchange.com/questions/48075/settings-in-media-settings-is-ignored-when-inserting-images/48108#48108?newreg=a83e378419564ab9855016ff3e6a32c7

I am afraid I am experiencing a similar issue. Not sure if it’s theme related but no matter what size I try, the images made available for post insertion are no larger than 640px (except if I chose Real Size option).

Did I say you wrote that?

So, besides the need of an extra click to get the link opening in a different tab (for no apparent reason), we are also deprived from the previous easiness to have fast external links suggested at the first keyboard strokes.

By the way, someone up there mentioned, and I guess in a pretty accurate way, that millions of persons use WordPress. Just to be sure I am understanding… your view of the decision making process suggests a discussion simultaneously involving “millions of persons”. Millions of persons discussing if this inline thing should be implemented or not? Most of them with no tech preparation for it (like myself)… is it really the way you idealize the WordPress world?

You don’t like a new feature? Suggest improvements. —> Most of us in this topic already did: cut the need of doubling the number of clicks to do something basic like “open in new tab”. And the choice to decide if the link is DO FOLLOW or not.

Now, apart from this. There is something I still don’t get: isn’t this “feature” supposed to equally act for external links completion? Because in my case doesn’t. At all. Whenever I am inserting an external link I will have to type it all (or paste) as before as soon as I started typing the URL, it would suggest the correct full address.

“You need to get involved during the development process, otherwise the feature will be implemented.”

Oh… and if I and these folks were involved during the development process, there would be no feature, right? Does it works by raising hands?

“And if nothing then I hope you will consider following forum guidelines which suggest you to not hijack over someone else’s thread. “

Right. Than you can start by stopping hijacking a petition for the removal of an unwelcome change pushing it to the support sphere.

“WordPress is an open source project so there are no “developers of WordPress”

Someone makes the decisions. People like to romanticize this “open source project” concept, but still, there is an hierarchy and there are decisions makers.

Someone, very wrongly, decided we have to be punished with this silly inline link thing. So be it, it’s for free, we have to take it. But stop the nonsense like me or John Smith would have a saying if we would had express our repulse for this aberration in a previous stage.

“And millions of people are using the latest version. So if only a dozen of people have complained about this issue, we can’t say that there are so many complaints.”

Demagogy, demagogy. Just look at the ratio of plugins installations vs feedback. People just tend to be quiet about things.