🇳🇱Netherlands @mhmhartman

Thanks mate :)

No I had it for a while, even after fresh install and cache clears. I cant reproduce the errors anymore either..

Sorry I cant be more helpful, I'll let u know when I discover something.

Thanks Almunnings,

using the following query I get the required results:

metatag {
            ... on MetaTag {
              tag
            }
            ... on MetaTagLink {
              attributes {
                rel
                href
              }
            }
            ... on MetaTagValue {
              attributes {
                name
                content
              }
            }
            ... on MetaTagProperty {
              attributes {
                property
                content
              }
            }
          }
        }

After execution I don't get any errors, so from my side there are no more issues.

The warnings like "Interface field MetaTagInterface.metatag expected but MediaVideo does not provide it." may still cause unexpected problems though.

Thank you for your help.

Hi Almunnings,

At least in my situation the metatags are not automatically added. I have verified that the "GraphQL Compose: Metatags" module is enabled and the content does have metatags entered.

This is my query:

query PageQuery {
  route(path: "/test-page") {
    ... on RouteInternal {
      __typename
      entity {
        ... on NodeArticle {
          id
          title
          path
          changed {
            time
          }
          mediaImage {
            __typename
            ... on MediaContentImage {
              id
              name
              mediaImage {
                variations(styles: HEADER_IMAGE) {
                  url
                }
              }
            }
          }
          
        }
      }
    }
  }
}

And this is the result:

{
  "data": {
    "route": {
      "__typename": "RouteInternal",
      "entity": {
        "id": "4d9a8e9a-6dc0-43c3-813a-0cfebc2952f4",
        "title": "Test page",
        "path": "/test-page",
        "changed": {
          "time": "2023-09-21T14:34:03+02:00"
        },
        "mediaImage": {
          "__typename": "MediaContentImage",
          "id": "5def8848-20e2-456d-a2af-0b0d3c67a547",
          "name": "pyramids-egypt-banner-header_0.jpg",
          "mediaImage": {
            "variations": [
              {
                "url": "http://localhost/sites/default/files/platform/styles/header_image/public/content/2023-09/pyramids-egypt-banner-header_0.jpg?itok=dS2kOMS5"
              }
            ]
          }
        }
      }
    }
  }
}

Used versions:

• Core: 9.5.10
• Metatag module: 2.0.0
• Metatag schema: 3.0.1

mhmhartman → created an issue.

Great work, thank you.

mhmhartman → created an issue.

I ran into the same CURL error "cURL error 3"

Somehow the latest Mailchimp update in mailchimp.install was never executed.

As a quick fix I added the latest update to a custom module, after running this, the CURL error went away.

If you have any problems make sure to check row "mailchimp.settings" in the "Config" table, as @jumpsuitgreen states, "oauth_middleware_url" must be present.

Make sure to run below:

function mailchimp_update_8004(&$sandbox) {
  $config = \Drupal::configFactory()->getEditable('mailchimp.settings');
  $config->set('oauth_middleware_url', 'https://drupal-mailchimp-oauth.uw.r.appspot.com');
  $config->save();
}

We also ran into this issue; the fix in the MR indeed fixes the issue.