Unable to update plugins as of 4.3 auto update

Please read the last post of this thread, near the bottom: https://www.ads-software.com/support/topic/read-this-first-%E2%80%93-wordpress-43-master-list?replies=4

I DID read that. The problem is NOT just the error message.

The point is the update ITSELF prevents these plugins that were previously not ready, from updating now that they are! The plugins we use all have updates listed to make them compatible with 4.3. It claims 100% compatibility. However, if you click ‘update plugins’ its just spins at you.

This happens when trying to update plugins straight from the wordpress repository and it as far as I’ve always known, a core function (as long as they are IN the wordpress repository, which they are.)

The plugin breaking is expected. The core ability to update those plugins breaking is not, nor is it acceptable for something that auto updates should do that. If it were a possibility someone should have issued a warning to everyone to update the plugins FIRST and do not allow auto update beforehand.

And this file:
wp-includes/functions.php

is a core file, not a plugin file.

Debug is already set to false. And having to ask a shared webhost to turn something off (possibly for everyone) is not reasonable.
It’s one thing to say the plugins are not compatible and either need to be turned off or updated. Its something else to roll out an update that won’t even allow you to run said updates that are available.

By any chance you use SSH2 method to upgrade plugins?

I just use the usual dashboard method. Plugins need updating, check the boxes and hit ‘update’.

If you use SSH2 methods for updating, again, read this post, at the *very* bottom. ??

https://www.ads-software.com/support/topic/read-this-first-%E2%80%93-wordpress-43-master-list?replies=4

Plugin and theme updates using SSH2 may be broken in some cases. There’s a fix there.

If you don’t use SSH2 methods for updating, then that fix won’t apply to you. However, you may be using SSH2 and don’t know it. Look in your wp-config.php file, and see if you have defined constants of FTP_SSH and similar. If they are there, then you’re using SSH2 update methods.

Are you saying wordpress uses that by default? Because I am not familiar with the term SSH2.
The file listed in the patch does not exist in my wordpress.

Are you saying wordpress uses that by default?

No, far from it. It would be something you would have to actually configure in your wp-config.php file.

However, you may have installed WordPress using a third-party system or some kind of auto-installer, which might have configured it for you. We have no way to know how exactly your WordPress is performing updates (there’s actually three different methods). Given the recent problem and your problem sounding very similar, it is reasonable to check for that case.

Because I am not familiar with the term SSH2.

You don’t need to be. Look in your wp-config.php file. Do the letters FTP_SSH appear anywhere at all in there? Or FTP_anything?

The file listed in the patch does not exist in my wordpress.

Yes, it does, because it exists in all installations of WordPress. You can ignore the trunk/src part of the file path, because that’s the path in our development system, not the path that will be in your WordPress installation.

The wordpress is not using SSH2, according to wp-config

It looks like maybe the plugins ARE updating but are stuck in a perpetual twirl and never showing the update as completed.

In addition I’m seeing a whole slew errors referring to javascript and jquery core:

ReferenceError: reference to undefined property j.delegateType
ReferenceError: reference to undefined property a.nodeName
ReferenceError: reference to undefined property a[h]
ReferenceError: reference to undefined property this[c] jquery.js:2:24416
ReferenceError: reference to undefined property e.type jquery.js:5:8853
ReferenceError: reference to undefined property j.opts.start
ReferenceError: reference to undefined property m.event.triggered jquery.js:4:6885
ReferenceError: reference to undefined property m.event.triggered

This: Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()
finally went away after the plugins finally updated. But it never showed it had completed, just kept twirling, until the page was refreshed. I had to double check with wordfence scans (turning plugins off and then on again first) to even be sure.