Error on upgrade to 14.0.2

Please remove all files that shouldn’t be there, or delete the entire folder and reinstall the plugin. That’s what’s causing these errors.

No offense whatsoever, but shouldn’t the update do that? Thanks!!!!

@iamediaworks that is what the update should normally do, which is something WordPress core handles, I don’t understand for one bit how that can not happen. Do you use InfiniteWP? Or something similar?

Nope. Straight WP. And it’s on more than one site.

Plus – I’m not the only one who has mentioned this file or the equivalent.

Sorry you’re going through this!

@aztopdavid ok. But now it works. Ok, we’re looking at how we can prevent that from happening, glad you’re ok now, few others in this thread left. For everybody, delete these two files from your migrations folder if you have them:

20180515101200_WpYoastIndexableMeta.php
20190529075734_WpYoastExpandIndexable.php

@kleatus (the OP) that goes for you too please ??

@iamediaworks What other plugins are you running? Anything security related?

i don’t have either of those files you mention on sites i have updated to 14.0.2 or any still on 14.0.1

@kleatus ok thx for checking. Can you please copy paste the complete error you’re getting? I’m trying to fix the many different problems in this thread ??

@iamediaworks That particular file you you referred to has not been in the plugin for 9 months.

You can see where it was removed here: https://plugins.trac.www.ads-software.com/changeset/2127187/wordpress-seo/trunk/migrations

If you were doing updates via normal WordPress update features, then WordPress deletes the entire plugin directory and recreates it from the ZIP file when you update. No version of the plugin served by www.ads-software.com since 11.8 has had that file in it. I have confirmed this.

So, the question therefore again becomes: how are you updating plugins on that site? Because there has to be something special there. If it was normal, then that file could not exist. www.ads-software.com has not served that file to a site in over 9 months.

@otto42 – some of the sites in question have auto-update turned on for plugins – which I’m guessing would be softaculous. But others didn’t, and still gave me that error.

@iamediaworks Well, I don’t know any way for WordPress to update a plugin and not delete the old plugin files first. There’s a function called “delete_old_plugin” just for that purpose.

Now, if you have something external to WordPress doing the updater work, then it is possible that that program is simply overwriting the old files and not getting rid of any deleted files. That could cause this. I have never used Softaculous and cannot speak to its process.

But no normal built-into-WordPress update will try to do this. If the deleting of the old files fails, then it doesn’t try to put the new plugin in place. It simply fails out with the old plugin still there or partially removed. There must be a third-party update of some kind happening for old files to be left behind.

Softaculous might in fact be a culprit, in part… I know it has been mentioned in this thread. FWIW… Softaculous is a VERY widely used cPanel autoinstaller for apps, including WordPress. Countless hosting companies offer it as part of their packages.

@ipstenu – not in particular. On at least 2, loginizer.

This is the error i get. I get this either when i update via wordpress backend or via infinitewp

Error Details
=============
An error of type E_ERROR was caused in line 81 of the file /wp-content/plugins/wordpress-seo/src/models/indexable.php. Error message: Class ‘Yoast\WP\Lib\Model’ not found

@kleatus Yes, we understand your error message.

The Yoast\WP\Lib\Model class is located in the /lib/model.php file in the plugin. So, this error suggests that you have an incomplete or otherwise broken copy of the plugin, somehow. You should manually update the plugin using the ZIP file from the site in order to see if that fixes the problem.

In other words, you need to make sure that the plugin is “complete” on the sites where you are getting this error message. If it is a problem with the update process in some way, then that’s generally not under the control of the plugin itself.

WordPress updates plugins the same way every time, the plugins themselves don’t have any say in the matter, so finding out if the upgrade is actually incomplete in some manner is important to solving the underlying issue.