Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Wrong returned term SEO title. #153

Open
akkis opened this issue Apr 4, 2023 · 0 comments
Open

Wrong returned term SEO title. #153

akkis opened this issue Apr 4, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@akkis
Copy link

akkis commented Apr 4, 2023

I have some terms in 3 levels like:

  1. By Experience (first level)
  2. By Experience -> Adventure (second level)
  3. 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 &#039;ancestor_id&#039; cannot be null]<br /><code>INSERT INTO 'wp_yoast_indexable_hierarchy' ('indexable_id', 'ancestor_id', 'depth', 'blog_id') VALUES (&#039;1&#039;, NULL, &#039;1&#039;, &#039;1&#039;)</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.

@ashhitch ashhitch added the bug Something isn't working label Apr 17, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants