Joost de Valk
Forum Replies Created
-
@loggins @newgiuseppe are you using a multilingual plugin by any chance?
@phamquangbaoplus that still works, for now, we catch those and write them to both the postmeta table and the indexables table.
Hi @serezh4
Yeah we were aware of this issue and we’re sorry! I wrote this post to explain what happened:
https://developer.yoast.com/blog/yoast-seo-14-0-x/
- This reply was modified 6 years, 1 month ago by Joost de Valk.
@mrkawaii I truly understand where you’re coming from, but this is not a problem that affects even 5% of our users. Over a million sites have updated in the last few days, and while I regret the issues that a group of sites have experienced, overall, lots of sites have updated well and are seeing great improvements. I’d suggest trying 14.0.4 and helping us get to the bottom of any outstanding issues if you have them.
I wrote a post about what has happened so far: https://developer.yoast.com/blog/yoast-seo-14-0-x/
If you’re using polylang, they’re working on an update to be compatible with Yoast SEO 14.0, you can follow along here.
In general: a deprecation error means that they’re using old code that soon might not work anymore, or already doesn’t work anymore. Under no circumstances should you this error on a live site, as it only shows when
WP_DEBUGis enabled and this should never be enabled on a live site.Yeah while I hate shifting the blame, honestly I think the problem here is with AMP for WP, not with us. They need to update their integration with us.
@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 😉
@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 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?
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.
Hmm just wondering @iamediaworks : when you update, do you delete the folder and put it back in? The file mentioned in your error doesn’t actually exist in the plugin anymore… You can see for yourself here: http://svn.wp-plugins.org/wordpress-seo/tags/14.0.2/migrations/
You mention
20180515101200_WpYoastIndexableMeta.phpand it simply isn’t there. So I’m wondering how that file can exist after an update.Ah you just answered that, thanks.
I’m stumped, honestly. Can I ask where these sites are hosted?
What we can see is that InfiniteWP seems to use FTP to update the plugin. This means that any object caches a host has would not be refreshed automatically, which is painful if you’re installing a new auto loader in a plugin like we’re doing in this release…
> Are you saying you think the install failed?
Yes. That’s what I’m thinking.
If you’re both using InfiniteWP it might even have to do with how InfiniteWP deals with this.