[Resolved] Wordsmith theme and yoast plug-in incompatibility.

[jonaldo]

I made a premium payment for the GeneralPress yesterday.
I decided the Wordsmith theme right through the site library.

Then we installed the Yoast plug-in, and found the symptoms of the site being loaded indefinitely.

Server CPU utilization is also very high.

Wordsmith library doesn’t seem compatible with certain plug-ins.

Is there a solution?

—————————————————
wordpress dashboard error massage

오류: [Unknown column ‘target_indexable_id’ in ‘where clause’]
SELECT COUNT(ID) FROM wp_posts WHERE ( ID NOT IN ( SELECT object_id FROM wp_yoast_indexable WHERE link_count IS NOT NULL AND object_type = ‘post’ ) OR ID IN ( SELECT DISTINCT post_id FROM wp_yoast_seo_links WHERE target_indexable_id IS NULL AND type = ‘internal’ AND target_post_id IS NOT NULL AND target_post_id != 0 ) ) AND post_status = ‘publish’ AND post_type IN (‘post’, ‘page’)

워드프레스 데이터베이스 오류: [Unknown column ‘target_indexable_id’ in ‘where clause’]
SELECT COUNT(ID) FROM wp_posts WHERE ( ID NOT IN ( SELECT object_id FROM wp_yoast_indexable WHERE link_count IS NOT NULL AND object_type = ‘post’ ) OR ID IN ( SELECT DISTINCT post_id FROM wp_yoast_seo_links WHERE target_indexable_id IS NULL AND type = ‘internal’ AND target_post_id IS NOT NULL AND target_post_id != 0 ) ) AND post_status = ‘publish’ AND post_type IN (‘post’, ‘page’)

워드프레스 데이터베이스 오류: [Unknown column ‘target_indexable_id’ in ‘where clause’]
SELECT COUNT(ID) FROM wp_posts WHERE ( ID NOT IN ( SELECT object_id FROM wp_yoast_indexable WHERE link_count IS NOT NULL AND object_type = ‘post’ ) OR ID IN ( SELECT DISTINCT post_id FROM wp_yoast_seo_links WHERE target_indexable_id IS NULL AND type = ‘internal’ AND target_post_id IS NOT NULL AND target_post_id != 0 ) ) AND post_status = ‘publish’ AND post_type IN (‘post’, ‘page’)

[David]

Hi there,

Sites from our Site Library are not separate Themes, they are simply a Site import. So the issue is not related to the Site itself. That error is directly related to the Yoast plugin and looks to be how it is querying the database – have you raised a support topic with Yoast?

[jonaldo]

Thank you.
I’ve inquired about Yoast for now.
You have a point.
But I’m sorry.
Why does this error occur only in the library?

[Leo]

All the templates in the site library are built with GeneratePress and GP Premium so it’s definitely not a template/site library-specific issue.

It could be a third-party plugin that’s causing the issue though.

Have you tried disabling all plugins except GP Premium to test?

[jonaldo]

Thank you.
I’ve inquired about Yoast for now.
You have a point.
But I’m sorry.
Why does this error occur only in the library?

[jonaldo]

Thank you.
This is a list of plug-ins currently active in my WordPress.
——————————
GenerateBlocks
GP Premium
Lightweight Social Icons
MC4WP: Mailchimp for WordPress
WP Show Posts
Yoast SEO

And after inquiring about Yoast team, I got the following answer.
Is there any possible cause?
—————————————————————-
Hi,

We apologize for the difficulties the plugin is causing for you. We would like some more information. We understand it may take some to gather but want to be able to rule out or in some things.

1. Can you confirm your server has all the right requirements? If you are not sure, speak to your host provider. They may need to increase the PHP memory. This guide explains more: https://yoast.com/help/plugin-requirements/.

2. Can you confirm you are using the most recent Yoast SEO, v15.2.1? If you update, does the issue resolve?

3. Are all your non-Yoast plugins and themes also updated?

4. If you look in your database for the table: wp_yoast_indexable are you seeing duplicate rows? Do those rows show an incorrect object_ID? If you are not sure your host provider can help,

5. Are the tables using int(11) or are they using bigint(20) for object_id and other fields? If you are not sure your host provider can help.

6. Can you confirm you are using WordPress 5.5.3? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: https://yoast.com/why-we-dont-support-old-wordpress-versions/.

7. Can you estimate how large the site is, in terms of content? 100s? 1000s? Or 10s of thousands?

[Leo]

Why does this error occur only in the library?

It’s definitely not something that’s just happening in the library as there is nothing special about the templates in the site library.

Let’s see what Yoast’s support say first.

You can also test with a twenty series WP theme and see if the issue occurs there.

[jonaldo]

No problem occurs in twenty series.

Occurs only in the Generate Press (Wordsmith) theme.

Hey Leo
Is it possible to conduct an internal test?

[Leo]

Occurs only in the Generate Press (Wordsmith) theme.

There is nothing special about the Wordsmith template – it’s simply a site built with GeneratePress and we just give it a name called Wordsmith – it’s still a GeneratePress site like any other sites in the library.

Does the error occur if you disable all plugins except Yoast in your install?

We are using Yoast on this site as well so the two are definitely compatible.

[jonaldo]

Currently, all plug-ins except Yoast are disabled.
Do you want to visit my website?
https://1il1gi.com/
or
https://1il1gi.com/blog

[Leo]

Those errors are pointing directly to Yoast so can you work with their support team first?

I would also check with your hosting support to see if they can help to identify the issue.

We have lots of users using GP with Yoast and never seen this issue before so I would think it’s something specific to your install.

[jonaldo]

Thank you, Leo.
Yoast team is slow to respond.
I’ll continue to ask questions.

[jonaldo]

I’m so, so, so sorry right now.

There was no problem with the absolute theme.

The cause was database authorization problems.

Only three (CREATE, DROP, CREATE ROUTINE) were specified in the structure of DB privileges.

I’m so sorry. And thank you.

I wish you the everlasting development of your company.

I’ll close the issue.

[jonaldo]

I’m so, so, so sorry right now.

There was no problem with the absolute theme.

The cause was database authorization problems.

Only three (CREATE, DROP, CREATE ROUTINE) were specified in the structure of DB privileges.

I’m so sorry. And thank you.

I wish you the everlasting development of your company.

I’ll close the issue.

[David]

No apologies necessary – really glad to hear you found what the issue was!

[Author]

Posts