stephan93
Forum Replies Created
-
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…
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.
Hello,
I’m having the same problem. Yesterday i followed the above steps but today my hosting provider took my whole site offline because it was generating too much traffic, they pointed out that a lot of queries on tables mc_yoast_indexable and mc_yoast_primary_term were executed and in fact i can confirm that duplicate rows are still being generated.
I’m using WordPress 5.5.1 and Yoast SEO 15.1.2
Any ideas how to fix?
Regards