You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By Experience -> Adventure -> By Sea (third level)
However, by running graphql query, seo node of every term (of every parent-child level) returns opengraphTitle with the value of "Adventure Archives < siteTitle etc >". It seems that choose only the "Adventure" term.
Also, if I change the SEO title manually of any term (from WP term edit page), then the query returns this error:
{
"errors": {
"message": "Unexpected token '<', \"<div id=\"e\"... is not valid JSON",
"stack": "SyntaxError: Unexpected token '<', \"<div id=\"e\"... is not valid JSON"
}
}
The full error message start with <div id="error"><p class="wpdberror"><strong>WordPress database error:</strong> [Column 'ancestor_id' cannot be null]<br /><code>INSERT INTO 'wp_yoast_indexable_hierarchy' ('indexable_id', 'ancestor_id', 'depth', 'blog_id') VALUES ('1', NULL, '1', '1')</code></p></div>{"data": ... and that's why it is not a valid JSON, as error message says.
I have some terms in 3 levels like:
However, by running graphql query,
seo
node of every term (of every parent-child level) returnsopengraphTitle
with the value of "Adventure Archives < siteTitle etc >". It seems that choose only the "Adventure" term.Also, if I change the SEO title manually of any term (from WP term edit page), then the query returns this error:
The full error message start with
<div id="error"><p class="wpdberror"><strong>WordPress database error:</strong> [Column 'ancestor_id' cannot be null]<br /><code>INSERT INTO 'wp_yoast_indexable_hierarchy' ('indexable_id', 'ancestor_id', 'depth', 'blog_id') VALUES ('1', NULL, '1', '1')</code></p></div>{"data": ...
and that's why it is not a valid JSON, as error message says.To restore query success, you need to do these steps.
Please, note that I am on dev environment with WPML activated.
The text was updated successfully, but these errors were encountered: