Yoast Indexable Keeps Duplicating Rows

Hi @stephan93

Could you provide us with a couple of examples of duplicate rows in the log as well as any Yoast-related errors that appear? Does the issue still occur when all non-Yoast plugins are deactivated?

We would recommend performing a conflict check as well — https://yoast.com/help/how-to-check-for-plugin-conflicts/

You mentioned that you’re having the same problem as in this forum thread. It looks like that user logged an issue on GitHub. He mentioned that wp_yoast_indexable and other tables incorrectly use int(11) instead of bigint(20) for object_id and other fields, but could you also confirm if it sounds similar to what you are experiencing?

Hello,

Sorry if it took some time but i had to bring up a test environment because right now my site crashes with a 504 Gateway Time-out error. Ok, i give you an example: if i run this query:

SELECT * FROM 'mc_yoast_indexable' WHERE permalink_hash = "39:3e0b4c8f8ef7dd65bf10a5b216f75ac4"

i get 63407 total matching rows that are all exactly the same. I can confirm that object_id in table wp_yoast_indexable is indeed using int(11). Conflict check will take some time but i can tell you that i haven’t added any new plugins to my site and that everything was working fine until a week ago.

P.S. i’m indeed using version 15.1.1 of Yoast SEO, my bad.

• This reply was modified 4 years, 4 months ago by stephan93.
• This reply was modified 4 years, 4 months ago by stephan93.

@stephan93 Thanks for your reply and for the additional information. The issue seems to be caused by when the object Ids are outside the value that int(11) can support. Are you able to check and confirm whether that is the case?

Yes, i can confirm that there are a lot of rows with object_id equal to 4294967295 in yoast_indexable table. I read that a guy was able to fix this by using bigint(20) instead of int(11), but by looking at the code that creates this table i can see that it was never meant to be a bigint:

$indexable_table->column(
   'object_id',
   'integer',
   [
      'unsigned' => true,
      'null'     => true,
      'limit'    => 11,
   ]
);

so i’m asking myself if this is a safe thing to do…

Hi @stephan93,

Thanks for explaining the issue. This looks like something that might need a code change or a feature request. Would you mind adding your question as a comment on the GitHub issue?

If we have any other information just relevant to your issue, we’ll get back to you.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.