Patrick Kuijpers
Forum Replies Created
-
Hi Eggeno,
There are a few cases where disabling all other plugins and then using the “Reset indexables & migrations” button has worked. So if you could try that, that would be great.
Alternatively, if you don’t want to disable all your plugins you can use the Health Check plugin, follow steps 1-10 of this article and then click the “Reset indexables & migrations” button.
I hope that makes sense
Forum: Plugins
In reply to: [Yoast SEO] Object 334900 of 32057 processedYou’re welcome and thank you for letting us know.
This thread is now marked as resolved.
Forum: Plugins
In reply to: [Yoast SEO] Object 334900 of 32057 processedI understand that waiting 13 hours is not the most ideal situation. If you are familiar with the WordPress Command Line Interface (WP-CLI) you can follow this guide the re-index. It should only take minutes this way.
Alternatively, you can also do nothing, in this case, the database will “lazy load”: it’ll slowly fill as posts are visited.
Forum: Plugins
In reply to: [Yoast SEO] Object 334900 of 32057 processedHi @dutchintouch & @renescr
I’m sorry to hear that it’s not working for you for both of you. Can you update to Yoast SEO 14.0.4 and try the following:
1. Install & activate the Yoast Test Helper plugin
2. Go to Tools -> Yoast Test
3. Hit the “Reset indexables & migrations” button
4. Try the optimize button againForum: Plugins
In reply to: [Yoast SEO] Version 14.0.4 still giving database errorGlad to hear the issue is resolved! Thank you for letting us know.
This thread is now marked as resolved.
Hi Eggeno,
I’m sorry to see that the indexation is not working as expected.
Can you please try the following steps to see if that solves the issue:
1. Install & activate the Yoast Test Helper plugin
2. Go to Tools -> Yoast Test
3. Hit the “Reset indexables & migrations” button
4. Try the optimize button againPlease let us know if that solved the issue
Forum: Plugins
In reply to: [Yoast SEO] Admin Dashboard So Slow since Yoast updateGlad to hear the issue is resolved! Thank you for letting us know.
This thread is now marked as resolved.
@alriksson Can you please try the following steps:
1. Install & activate the Yoast Test Helper plugin
2. Go to Tools -> Yoast Test
3. Hit the “Reset indexables & migrations” button
4. Try the optimize button againIf that does not help can you please share your error log with us here.
- This reply was modified 4 years, 10 months ago by Patrick Kuijpers. Reason: added link to Yoast test helper
Forum: Plugins
In reply to: [Yoast SEO] Search console errors@mish99 No problem!
I’m marking this topic as resolved.
Forum: Plugins
In reply to: [Yoast SEO] Yoast SEO Breadcrumbs Stopped DisplayingHi @mhwallace1,
I’m sorry to see that you’re breadcrumbs are not working anymore after 14.0. Did you by any chance update to the latest version already (14.0.4)? A lot of breadcrumb issues have been solved in the patch releases after 14.0.
If the issue remains can you please share the full error log with us here.
- This reply was modified 4 years, 10 months ago by Patrick Kuijpers.
Hi @alriksson,
I’m very sorry to hear you’re experiencing this error. Did you by any chance update to 14.0.4 already? If so, did that solve the issue?
If the issue remains can you please open a full bug report to give us more information on how to reproduce this issue. You can do this by following the steps in this article
Forum: Plugins
In reply to: [Yoast SEO] Fatal errors again in version 14.0.2Hi @hanswitteprins,
I’m very sorry to hear you’re experiencing a fatal error. Did you by any chance update to 14.0.4 already? If so, did that solve the issue?
Forum: Plugins
In reply to: [Yoast SEO] Need more info about the bugs on indexHi @pingbara,
If you have already updated to 14.0.4 there is nothing to worry about anymore ??
I also checked your website and everything looks fine and can be indexed.I will mark this thread as resolved.
Forum: Plugins
In reply to: [Yoast SEO] Reply Link on Comments Broken by 14.0.2Hi @ispreview,
We were able the reproduce the issue and currently have an open issue for it. Please keep an eye on our changelog
Hi @jamesahavis,
Happy to hear it’s solved!