Jason Hsu

That’s like not caused by this plugin. The FAQ markup on that page is inside of this <div> block, which is generated by Elementor’s Text Editor widget.

<div class="elementor-element elementor-element-d51d7b0 elementor-widget elementor-widget-text-editor" data-id="d51d7b0" data-element_type="widget" data-widget_type="text-editor.default">

The said widget is located between the “Water Heater Venting” section and the “Share” section. However, I don’t see it on every page.

Can you please check?

Sorry, no, it’s just there by default. Also, there is still a container even though it doesn’t show anything. So I guess the only application for it would be to use to control the container, for example, its margin,.

Also sorry for the late reply. I’m subscribed to this forum but for some reason I don’t get the notifications.

Hey Mike,

It’s still showing 3 different FAQ markups.

You should only have ONE FAQ widget on a page, so delete one of them. You can add multiple questions and answers to this particular plugin.

Also, Yoast SEO created a markup on the page as well. Whichever plugin you use, you should only have one FAQ markup.

Thanks for the Christmas greeting, Happy New Year to you.

Hi Mike,

It appears you have FOUR FAQ markups on the same page, which suggests that you might be using multiple FAQ widgets. You should only have ONE FAQ markup per page.

Two of the four markups widgets you’re using are producing errors, so I’d either remove them or configure them properly to rid of the errors.

The other two are correct, but like I said you can only have one. So choose one to use and remove the other one.

Hope this helps.

Using this invisible FAQ schema widget allows us to present the answer differently to search engine, without affecting the flow and readability of the article.

Which is why I wrote “to present the answer different,” not to present different answers.

I personally don’t like accordion style FAQ widgets. So what I usually do is to take a snippet from the article, and put it in the schema markup.

Hi Mike,

It’s designed to only output the structured data in source code but not render anything on the front end.

The point of being invisible on page is that schema markup is intended for search engines, not human beings, and you might want to present the information differently.

For example, we have a blog post titled What is Responsive Web Design?. In addition to answering the question in the title, the article also talks about other aspects of responsive web design, plus a bit of advertising at the end.

If you search for “FAQPage” in the source code, you’ll find a FAQ markup that answers what responsive web design is, but it’s kept short in hope that it would get more clicks.

Using this invisible FAQ schema widget allows us to present the answer differently to search engine, without affecting the flow and readability of the article.

Does this answer your question?

Hi Priscilla,

I tried the WP-CLI command on FlyWheel and it didn’t work either.

I’ll just use the Optimize SEO Data button when the site goes live. If there’s an issue then I’ll report back.

Thanks

Hi Jeroen,

I followed your instruction:
– Deactivate and removed Yoast SEO, the plugin.
– Deleted all 6 Yoast tables.
– Removed options that start with yoast and wpseo, left the transient ones alone.
— yoast_migration_free
— wpseo
— wpseo_titles
— wpseo_social
— wpseo_ryte
— wpseo_taxonomy_meta

I then re-installed Yoast SEO. Upon plugin activation, it was able to create related database tables, which it previously could not. So I’d say removing those Yoast options seems to have helped.

The error message regarding inserting NULL ancestor_id seem to have gone away, but I’ll keep monitoring.

That said, I still could not complete the indexing process via the WP-CLI command. The process would get stuck at 100% while indexing posts, then the timer continued to run. Here’s the associated error log.

[04-Dec-2020 17:32:28 UTC] PHP Warning: Error while sending QUERY packet. PID=6244 in /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php on line 2033
[04-Dec-2020 17:32:28 UTC] PHP Stack trace:
[04-Dec-2020 17:32:28 UTC] PHP 1. {main}() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:0
[04-Dec-2020 17:32:28 UTC] PHP 2. include() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:4
[04-Dec-2020 17:32:28 UTC] PHP 3. include() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/php/boot-phar.php:11
[04-Dec-2020 17:32:28 UTC] PHP 4. WP_CLI\bootstrap() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/wp-cli.php:27
[04-Dec-2020 17:32:28 UTC] PHP 5. WP_CLI\Bootstrap\LaunchRunner->process() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/bootstrap.php:74
[04-Dec-2020 17:32:28 UTC] PHP 6. WP_CLI\Runner->start() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:23
[04-Dec-2020 17:32:28 UTC] PHP 7. WP_CLI\Runner->load_wordpress() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1158
[04-Dec-2020 17:32:28 UTC] PHP 8. require() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1237
[04-Dec-2020 17:32:28 UTC] PHP 9. wp_not_installed() /Users/admin/Local Sites/local-site/app/public/wp-settings.php:159
[04-Dec-2020 17:32:28 UTC] PHP 10. is_blog_installed() /Users/admin/Local Sites/local-site/app/public/wp-includes/load.php:664
[04-Dec-2020 17:32:28 UTC] PHP 11. wpdb->get_results() /Users/admin/Local Sites/local-site/app/public/wp-includes/functions.php:1756
[04-Dec-2020 17:32:28 UTC] PHP 12. wpdb->query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2673
[04-Dec-2020 17:32:28 UTC] PHP 13. wpdb->_do_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:1922
[04-Dec-2020 17:32:28 UTC] PHP 14. mysqli_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2033
[04-Dec-2020 17:32:28 UTC] PHP Warning: Error while sending QUERY packet. PID=6239 in /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php on line 2033
[04-Dec-2020 17:32:28 UTC] PHP Stack trace:
[04-Dec-2020 17:32:28 UTC] PHP 1. {main}() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:0
[04-Dec-2020 17:32:28 UTC] PHP 2. include() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:4
[04-Dec-2020 17:32:28 UTC] PHP 3. include() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/php/boot-phar.php:11
[04-Dec-2020 17:32:28 UTC] PHP 4. WP_CLI\bootstrap() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/wp-cli.php:27
[04-Dec-2020 17:32:28 UTC] PHP 5. WP_CLI\Bootstrap\LaunchRunner->process() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/bootstrap.php:74
[04-Dec-2020 17:32:28 UTC] PHP 6. WP_CLI\Runner->start() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:23
[04-Dec-2020 17:32:28 UTC] PHP 7. WP_CLI\Runner->load_wordpress() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1158
[04-Dec-2020 17:32:28 UTC] PHP 8. require() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1237
[04-Dec-2020 17:32:28 UTC] PHP 9. wp_cookie_constants() /Users/admin/Local Sites/local-site/app/public/wp-settings.php:351
[04-Dec-2020 17:32:28 UTC] PHP 10. get_option() /Users/admin/Local Sites/local-site/app/public/wp-includes/default-constants.php:284
[04-Dec-2020 17:32:28 UTC] PHP 11. wpdb->get_row() /Users/admin/Local Sites/local-site/app/public/wp-includes/option.php:145
[04-Dec-2020 17:32:28 UTC] PHP 12. wpdb->query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2593
[04-Dec-2020 17:32:28 UTC] PHP 13. wpdb->_do_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:1922
[04-Dec-2020 17:32:28 UTC] PHP 14. mysqli_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2033
[04-Dec-2020 17:32:28 UTC] PHP Warning: Error while sending QUERY packet. PID=6240 in /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php on line 2033
[04-Dec-2020 17:32:28 UTC] PHP Stack trace:
[04-Dec-2020 17:32:28 UTC] PHP 1. {main}() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:0
[04-Dec-2020 17:32:28 UTC] PHP 2. include() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:4
[04-Dec-2020 17:32:28 UTC] PHP 3. include() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/php/boot-phar.php:11
[04-Dec-2020 17:32:28 UTC] PHP 4. WP_CLI\bootstrap() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/wp-cli.php:27
[04-Dec-2020 17:32:28 UTC] PHP 5. WP_CLI\Bootstrap\LaunchRunner->process() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/bootstrap.php:74
[04-Dec-2020 17:32:28 UTC] PHP 6. WP_CLI\Runner->start() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:23
[04-Dec-2020 17:32:28 UTC] PHP 7. WP_CLI\Runner->load_wordpress() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1158
[04-Dec-2020 17:32:28 UTC] PHP 8. require() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1237
[04-Dec-2020 17:32:28 UTC] PHP 9. wp_cookie_constants() /Users/admin/Local Sites/local-site/app/public/wp-settings.php:351
[04-Dec-2020 17:32:28 UTC] PHP 10. get_option() /Users/admin/Local Sites/local-site/app/public/wp-includes/default-constants.php:284
[04-Dec-2020 17:32:28 UTC] PHP 11. wpdb->get_row() /Users/admin/Local Sites/local-site/app/public/wp-includes/option.php:145
[04-Dec-2020 17:32:28 UTC] PHP 12. wpdb->query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2593
[04-Dec-2020 17:32:28 UTC] PHP 13. wpdb->_do_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:1922
[04-Dec-2020 17:32:28 UTC] PHP 14. mysqli_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2033
[04-Dec-2020 17:32:28 UTC] PHP Warning: Error while sending QUERY packet. PID=6241 in /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php on line 2033
[04-Dec-2020 17:32:28 UTC] PHP Stack trace:
[04-Dec-2020 17:32:28 UTC] PHP 1. {main}() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:0
[04-Dec-2020 17:32:28 UTC] PHP 2. include() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:4
[04-Dec-2020 17:32:28 UTC] PHP 3. include() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/php/boot-phar.php:11
[04-Dec-2020 17:32:28 UTC] PHP 4. WP_CLI\bootstrap() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/wp-cli.php:27
[04-Dec-2020 17:32:28 UTC] PHP 5. WP_CLI\Bootstrap\LaunchRunner->process() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/bootstrap.php:74
[04-Dec-2020 17:32:28 UTC] PHP 6. WP_CLI\Runner->start() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:23
[04-Dec-2020 17:32:28 UTC] PHP 7. WP_CLI\Runner->load_wordpress() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1158
[04-Dec-2020 17:32:28 UTC] PHP 8. require() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1237
[04-Dec-2020 17:32:28 UTC] PHP 9. wp_cookie_constants() /Users/admin/Local Sites/local-site/app/public/wp-settings.php:351
[04-Dec-2020 17:32:28 UTC] PHP 10. get_option() /Users/admin/Local Sites/local-site/app/public/wp-includes/default-constants.php:284
[04-Dec-2020 17:32:28 UTC] PHP 11. wpdb->get_row() /Users/admin/Local Sites/local-site/app/public/wp-includes/option.php:145
[04-Dec-2020 17:32:28 UTC] PHP 12. wpdb->query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2593
[04-Dec-2020 17:32:28 UTC] PHP 13. wpdb->_do_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:1922
[04-Dec-2020 17:32:28 UTC] PHP 14. mysqli_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2033
[04-Dec-2020 17:32:28 UTC] PHP Warning: Error while sending QUERY packet. PID=6242 in /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php on line 2033
[04-Dec-2020 17:32:28 UTC] PHP Stack trace:
[04-Dec-2020 17:32:28 UTC] PHP 1. {main}() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:0
[04-Dec-2020 17:32:28 UTC] PHP 2. include() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:4
[04-Dec-2020 17:32:28 UTC] PHP 3. include() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/php/boot-phar.php:11
[04-Dec-2020 17:32:28 UTC] PHP 4. WP_CLI\bootstrap() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/wp-cli.php:27
[04-Dec-2020 17:32:28 UTC] PHP 5. WP_CLI\Bootstrap\LaunchRunner->process() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/bootstrap.php:74
[04-Dec-2020 17:32:28 UTC] PHP 6. WP_CLI\Runner->start() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:23
[04-Dec-2020 17:32:28 UTC] PHP 7. WP_CLI\Runner->load_wordpress() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1158
[04-Dec-2020 17:32:28 UTC] PHP 8. require() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1237
[04-Dec-2020 17:32:28 UTC] PHP 9. wp_cookie_constants() /Users/admin/Local Sites/local-site/app/public/wp-settings.php:351
[04-Dec-2020 17:32:28 UTC] PHP 10. get_option() /Users/admin/Local Sites/local-site/app/public/wp-includes/default-constants.php:284
[04-Dec-2020 17:32:28 UTC] PHP 11. wpdb->get_row() /Users/admin/Local Sites/local-site/app/public/wp-includes/option.php:145
[04-Dec-2020 17:32:28 UTC] PHP 12. wpdb->query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2593
[04-Dec-2020 17:32:28 UTC] PHP 13. wpdb->_do_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:1922
[04-Dec-2020 17:32:28 UTC] PHP 14. mysqli_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2033
[04-Dec-2020 17:32:28 UTC] PHP Warning: Error while sending QUERY packet. PID=6243 in /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php on line 2033
[04-Dec-2020 17:32:28 UTC] PHP Stack trace:
[04-Dec-2020 17:32:28 UTC] PHP 1. {main}() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:0
[04-Dec-2020 17:32:28 UTC] PHP 2. include() /Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar:4
[04-Dec-2020 17:32:28 UTC] PHP 3. include() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/php/boot-phar.php:11
[04-Dec-2020 17:32:28 UTC] PHP 4. WP_CLI\bootstrap() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/wp-cli.php:27
[04-Dec-2020 17:32:28 UTC] PHP 5. WP_CLI\Bootstrap\LaunchRunner->process() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/bootstrap.php:74
[04-Dec-2020 17:32:28 UTC] PHP 6. WP_CLI\Runner->start() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:23
[04-Dec-2020 17:32:28 UTC] PHP 7. WP_CLI\Runner->load_wordpress() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1158
[04-Dec-2020 17:32:28 UTC] PHP 8. require() phar:///Applications/Local.app/Contents/Resources/extraResources/bin/wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1237
[04-Dec-2020 17:32:28 UTC] PHP 9. wp_cookie_constants() /Users/admin/Local Sites/local-site/app/public/wp-settings.php:351
[04-Dec-2020 17:32:28 UTC] PHP 10. get_option() /Users/admin/Local Sites/local-site/app/public/wp-includes/default-constants.php:284
[04-Dec-2020 17:32:28 UTC] PHP 11. wpdb->get_row() /Users/admin/Local Sites/local-site/app/public/wp-includes/option.php:145
[04-Dec-2020 17:32:28 UTC] PHP 12. wpdb->query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2593
[04-Dec-2020 17:32:28 UTC] PHP 13. wpdb->_do_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:1922
[04-Dec-2020 17:32:28 UTC] PHP 14. mysqli_query() /Users/admin/Local Sites/local-site/app/public/wp-includes/wp-db.php:2033

Hi Prescilla,

Here’s the server spec:

WordPress 5.53
PHP 7.4.13
MySQL 5.7.25
cURL 7.68.0
PHP memory limit 128M (but the same problem persists on a local instance with 256M)

Seems to meet the requirements.

It took about 10 seconds for the progress bar to reach 100%, but it’s been stuck there for the last 15 minutes.

wp yoast index –reindex
This will clear all previously indexed objects. Are you certain you wish to proceed? [y/n] y
Indexing posts 100% [===========================================] 15:41 / 15:03

Hi Priscilla,

I’ve tried removing Yoast, manually dropping Yoast tables, and manually uploading Yoast. However, upon activation, tables could not be created, and the following messages filled the error log.

WordPress database error Table ‘local.wp_u4583mh5it_yoast_indexable’ doesn’t exist for query…

After that, I tried the Yoast Test Helper tool to reset the indexable, which then created all the Yoast tables in the database.

I’ve tried using the Twenty Nineteen theme, disabling all plugins except Yoast SEO and Yoast Test Helper. However, the message regarding NULL ancestor_id still persists.

I’m not able to optimize SEO data because the button is disabled due to it being a non-production site. Is there anyway around that?

Update: I tried indexing using WP-CLI command “wp yoast index”. The progress bar reached 100% but the timer continued to run non-stop and got stuck on indexing posts. There are about 150 posts and 10 pages on the site.

• This reply was modified 3 years, 11 months ago by Jason Hsu.
• This reply was modified 3 years, 11 months ago by Jason Hsu.

It’s currently happening on v15.4.

[03-Dec-2020 17:56:42 UTC] WordPress database error Column ‘ancestor_id’ cannot be null for query INSERT INTO wp_u4583mh5it_yoast_indexable_hierarchy (indexable_id, ancestor_id, depth, blog_id) VALUES (‘1’, NULL, ‘1’, ‘1’) made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/hello-elementor/index.php’), get_header, locate_template, load_template, require_once(‘/themes/hello-elementor/header.php’), wp_head, do_action(‘wp_head’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Front_End_Integration->call_wpseo_head, do_action(‘wpseo_head’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Front_End_Integration->present_head, Yoast\WP\SEO\Presenters\Schema_Presenter->present, Yoast\WP\SEO\Presenters\Schema_Presenter->get, Yoast\WP\SEO\Presentations\Abstract_Presentation->__get, Yoast\WP\SEO\Presentations\Indexable_Presentation->generate_schema, Yoast\WP\SEO\Generators\Schema_Generator->generate, Yoast\WP\SEO\Generators\Schema\Breadcrumb->generate, Yoast\WP\SEO\Presentations\Abstract_Presentation->__get, Yoast\WP\SEO\Presentations\Indexable_Presentation->generate_breadcrumbs, Yoast\WP\SEO\Generators\Breadcrumbs_Generator->generate, Yoast\WP\SEO\Repositories\Indexable_Repository->get_ancestors, Yoast\WP\SEO\Repositories\Indexable_Hierarchy_Repository->find_ancestors, Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build, Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->save_ancestors, Yoast\WP\SEO\Repositories\Indexable_Hierarchy_Repository->add_ancestor, Yoast\WP\Lib\Model->save, Yoast\WP\Lib\ORM->save, Yoast\WP\Lib\ORM::execute

• This reply was modified 3 years, 11 months ago by Jason Hsu.

Hi Michael, thanks for the reply.

I can ask the host to check database permission, but the tables have already been created manually.

The one problem we have right now is Yoast trying to insert a NULL value into the table, and this has nothing to do with database permission:

WordPress database error Column ‘ancestor_id’ cannot be null for query INSERT INTO wp_u4583mh5it_yoast_indexable_hierarchy (indexable_id, ancestor_id, depth, blog_id) VALUES (‘2’, NULL, ‘1’, ‘1’) made by require(‘wp-admin/edit-form-blocks.php’), array_reduce, rest_preload_api_request, rest_do_request, WP_REST_Server->dispatch, WP_REST_Posts_Controller->get_item, WP_REST_Posts_Controller->prepare_item_for_response, WP_REST_Controller->add_additional_fields_to_object, Yoast\WP\SEO\Routes\Yoast_Head_REST_Field->for_post, Yoast\WP\SEO\Actions\Indexables\Indexable_Head_Action->for_post, Yoast\WP\SEO\Surfaces\Values\Meta->get_head, Yoast\WP\SEO\Presenters\Schema_Presenter->present, Yoast\WP\SEO\Presenters\Schema_Presenter->get, Yoast\WP\SEO\Presentations\Abstract_Presentation->__get, Yoast\WP\SEO\Presentations\Indexable_Presentation->generate_schema, Yoast\WP\SEO\Generators\Schema_Generator->generate, Yoast\WP\SEO\Generators\Schema\Breadcrumb->generate, Yoast\WP\SEO\Presentations\Abstract_Presentation->__get, Yoast\WP\SEO\Presentations\Indexable_Presentation->generate_breadcrumbs, Yoast\WP\SEO\Generators\Breadcrumbs_Generator->generate, Yoast\WP\SEO\Repositories\Indexable_Repository->get_ancestors, Yoast\WP\SEO\Repositories\Indexable_Hierarchy_Repository->find_ancestors, Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build, Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->save_ancestors, Yoast\WP\SEO\Repositories\Indexable_Hierarchy_Repository->add_ancestor, Yoast\WP\Lib\Model->save, Yoast\WP\Lib\ORM->save, Yoast\WP\Lib\ORM::execute

Hi Michael,

Yes it’s WP 5.5.3 running PHP 7.4.12 on FlyWheel hosting. We also run many other sites on FlyWheel with Yoast installed.

Everything including the Elementor Hello Theme is up-to-date.

I’ve tried deactivating, deleting Yoast, and dropping all tables that have a Yoast prefix.

Thanks

That’s great to hear! Thanks for the review.