Error database Yoast Seo

Resolved cerisenuances
(@cerisenuances)

4 years, 7 months ago

Hello

I have some issues with my website since a few days, it seems to be coming from Yoast Seo.

“[02-Nov-2021 06:31:09 UTC] Erreur de la base de données WordPress : Unknown column 'estimated_reading_time_minutes' in 'field list' pour la requête UPDATEmod746_yoast_indexableSETobject_id= '4226',object_type= 'post',object_sub_type= 'product',permalink= 'https://nuances.paris/?post_type=product&p=4226',primary_focus_keyword_score= NULL,readability_score= '90',is_cornerstone= '0',is_robots_noindex= NULL,is_robots_nofollow= '0',is_robots_noimageindex= NULL,is_robots_noarchive= NULL,is_robots_nosnippet= NULL,open_graph_image= 'https://nuances.paris/wp-content/uploads/2020/06/ugbu_totem_ours_c-1000x1000.jpg',open_graph_image_id= NULL,open_graph_image_source= 'first-content-image',open_graph_image_meta= NULL,twitter_image= 'https://nuances.paris/wp-content/uploads/2020/06/ugbu_totem_ours_c-1000x1000.jpg',twitter_image_id= NULL,twitter_image_source= 'first-content-image',primary_focus_keyword= NULL,canonical= NULL,title= NULL,description= NULL,breadcrumb_title= 'Tasse cylindre',open_graph_title= NULL,open_graph_description= NULL,twitter_title= NULL,twitter_description= NULL,estimated_reading_time_minutes= NULL,author_id= '1',post_parent= '0',number_of_pages= NULL,post_status= 'trash',is_protected= '0',is_public= '0',has_public_posts= NULL,blog_id= '1',schema_page_type= NULL,schema_article_type= NULL,version= '1',permalink_hash= '47:b167ed85eaba2c60626eb13f28ce21dc',updated_at= '2021-11-02 06:31:09' WHEREid` = ‘1293’ faite par WP_List_Table->display, WP_List_Table->display_tablenav, WP_Posts_List_Table->extra_tablenav, do_action(‘manage_posts_extra_tablenav’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Admin\Admin_Columns_Cache_Integration->maybe_fill_cache, Yoast\WP\SEO\Integrations\Admin\Admin_Columns_Cache_Integration->fill_cache, Yoast\WP\SEO\Repositories\Indexable_Repository->find_by_multiple_ids_and_type, array_map, Yoast\WP\SEO\Repositories\Indexable_Repository->upgrade_indexable, Yoast\WP\SEO\Builders\Indexable_Builder->build, Yoast\WP\SEO\Builders\Indexable_Builder->save_indexable, do_action(‘wpseo_save_indexable’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Watchers\Indexable_Post_Watcher->updated_indexable, Yoast\WP\SEO\Integrations\Watchers\Indexable_Post_Watcher->update_relations, Yoast\WP\SEO\Integrations\Watchers\Indexable_Post_Watcher->get_related_indexables, Yoast\WP\SEO\Repositories\Indexable_Repository->find_by_id_and_type, Yoast\WP\SEO\Repositories\Indexable_Repository->upgrade_indexable, Yoast\WP\SEO\Builders\Indexable_Builder->build, Yoast\WP\SEO\Builders\Indexable_Builder->save_indexable, do_action(‘wpseo_save_indexable’)…

Erreur de la base de données WordPress : [Unknown column ‘nonce_action’ in ‘field list’]
SELECT action_id, name, label, query, status, is_primary, actioned_text, nonce_action, nonce_name FROM mod746_wc_admin_note_actions WHERE note_id = 78`”

Could you please help ?

The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)

Plugin Support Maybellyne
(@maybellyne)

4 years, 7 months ago
Hello Cerisenuances,

We are sorry about the database error you are experiencing. Can you please try resetting the indexables in the database tables by following the steps below?

1. Install & activate the Yoast Test Helper plugin
2. Go to Tools > Yoast Test
3. Locate the Yoast SEO section and click on the ‘Reset indexables tables & migrations’, ‘Reset Prominent words calculation’, and ‘Reset Internal link counter’ buttons. After each click, the page will reload to confirm that each reset was successful. Note: this won’t actually erase your SEO data, which is also stored in WordPress’ default tables. It’ll just reset our index (custom tables) for that data.
4. Go to SEO > Tools, and under SEO data, click the “Start SEO data optimization” button to allow Yoast to rescan your content.

Could you then check if you aren’t experiencing these errors anymore?
- This reply was modified 4 years, 7 months ago by Maybellyne. Reason: added hyperlink
Thread Starter cerisenuances
(@cerisenuances)

4 years, 7 months ago

Hello

Thank you for the quick answer. I did all the first steps but the last one “Start SEO data optimization” gives me an error message and cannot proceed.
“Error message
Error parsing the response to JSON.”

Plugin Support Maybellyne
(@maybellyne)

4 years, 7 months ago

Thanks for following the steps and we are sorry about the error you later encountered.

Could you check if there are any JavaScript errors appearing in your browser’s console when you encounter the ‘oops’ message again when running the SEO data optimization process? And could you share a screenshot with us?

We also recommend trying to complete the SEO data optimization process in troubleshooting mode in the Health Check plugin, with only a default WP theme such as TwentyTwenty, and only Yoast SEO 16.9 as the plugin enabled, just to rule out any plugin or theme conflicts that could be causing an issue.
Thread Starter cerisenuances
(@cerisenuances)

4 years, 7 months ago
here is the error i get
```
JQMIGRATE: Migrate is installed, version 3.3.2
indexation-1750.js:1 POST https://nuances.paris/wp-json/yoast/v1/link-indexing/posts 503
(anonymous) @ indexation-1750.js:1
f @ regenerator-runtime.min.js?ver=0.13.7:1
r._invoke @ regenerator-runtime.min.js?ver=0.13.7:1
(anonymous) @ regenerator-runtime.min.js?ver=0.13.7:1
n @ indexation-1750.js:1
a @ indexation-1750.js:1
(anonymous) @ indexation-1750.js:1
(anonymous) @ indexation-1750.js:1
(anonymous) @ indexation-1750.js:1
(anonymous) @ indexation-1750.js:1
f @ regenerator-runtime.min.js?ver=0.13.7:1
r._invoke @ regenerator-runtime.min.js?ver=0.13.7:1
(anonymous) @ regenerator-runtime.min.js?ver=0.13.7:1
f @ regenerator-runtime.min.js?ver=0.13.7:1
t @ regenerator-runtime.min.js?ver=0.13.7:1
r._invoke @ regenerator-runtime.min.js?ver=0.13.7:1
(anonymous) @ regenerator-runtime.min.js?ver=0.13.7:1
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
Promise.then (async)
n @ indexation-1750.js:1
a @ indexation-1750.js:1
indexation-1750.js:1 POST https://nuances.paris/wp-json/yoast/v1/link-indexing/posts 504
```
Plugin Support Maybellyne
(@maybellyne)

4 years, 7 months ago

Thanks for the feedback. I can see this error from the console:

POST https://nuances.paris/wp-json/yoast/v1/link-indexing/posts 504

The SEO data optimization feature uses the WordPress REST API to scan posts/pages for the right internal links to show. Your server returns that error when accessing the REST API.

Please contact your web host to check the mod_security settings that prevent our plugin from accessing the REST API. If there are no ‘mod_security’ settings preventing access at the server, you may have a custom .htaccess rule or security plugin that limits access to the WordPress REST API. Please review any security restrictions and whitelist the Yoast plugin for accessing the feature.

If you have a Web Application Firewall (WAF)s, like Comodo, please verify that it is not set up to strip the parameter from the Yoast REST API requests. Some users have reported that some WAF setups are too strict in the prevention of Blind SQL injection attacks. Your web host or server admin can help you if you’re not familiar with WAF settings on your site.

Are there any settings in your server/firewall that would explain this behavior? If you don’t know how to check this, please reach out to your server administrator. They’ll be able to check this for you.

Thread Starter cerisenuances
(@cerisenuances)

4 years, 7 months ago

Hello.
Thank you so much for your complete answer. I just checked with my hosting company and they say everything is ok on the servor. Do you have another option ?

Plugin Support Michael Tiña
(@mikes41720)

4 years, 7 months ago

Hi @cerisenuances

We would recommend that you reset all of the data using the Yoast Test Helper plugin, and then enable troubleshooting mode in the Health Check plugin and enable a default WP theme (such as TwentyTwenty) and only Yoast SEO v17.5 as the plugin enabled. Please then go to your SEO > Tools section and try to run and complete the SEO data optimization process. Does it successfully complete then?

Otherwise, you can refer to this article for more information – https://yoast.com/help/we-couldnt-complete-the-optimization-of-your-seo-data/

We may need to check on your setup specifically, but we are unable to do so over these public forums. You may want to consider Yoast SEO Premium so we can try and check on this further.

Thread Starter cerisenuances
(@cerisenuances)

4 years, 7 months ago

Hello.

I still get the error in doing it this way.

“Error message
Error parsing the response to JSON.

Response
<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>
<!– a padding to disable MSIE and Chrome friendly error page –>
<!– a padding to disable MSIE and Chrome friendly error page –>
<!– a padding to disable MSIE and Chrome friendly error page –>
<!– a padding to disable MSIE and Chrome friendly error page –>
<!– a padding to disable MSIE and Chrome friendly error page –>
<!– a padding to disable MSIE and Chrome friendly error page –>”

Plugin Support Michael Tiña
(@mikes41720)

4 years, 7 months ago

Hi,

Are you still getting the same error even with troubleshooting mode enabled in Health Check and with a default WP theme and only Yoast SEO v17.5 as the plugin enabled?

If so, that 504 message indicates it might be an issue with your server as to why the SEO data optimization process didn’t successfully complete. We would need to check on this further, which we are unable to do so on these public forums. You might want to consider Yoast SEO Premium so we can take a closer look at this.

Otherwise, you might need to check this further with your web host and see if there aren’t any rules in place that might block the WordPress REST API – https://yoast.com/help/we-couldnt-complete-the-optimization-of-your-seo-data/

We’ll be leaving this forum thread open for a few days in case anyone else wants to help provide suggestions or advice.

devnihil
(@devnihil)

4 years, 6 months ago

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

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Error database Yoast Seo’ is closed to new replies.

Tags