Not sure why but adding a trailing / to the path fixes the issue i.e /health/
I'm seeing the same thing if I point my aws load balancer health check to any other path its fine with the following trusted_hosts_pattern
$settings['trusted_host_patterns'] = [
'^10\.0\.\d{1,3}\.\d{1,3}$', // Allow all 10.0.x.x IP addresses
];
It's just the health path that returns a 400 error
I don't think this fix addresses the issue.
The problem is if you leave the field blank on a tagify select field, it set the value as the first item in the select list when it should stay blank.
marcus.williams@four.agency → created an issue.
marcus.williams@four.agency → created an issue.
marcus.williams@four.agency → created an issue.
I see, thanks that's great
marcus.williams@four.agency → created an issue.
marcus.williams → created an issue.
Try this https://www.drupal.org/project/crop/issues/3293782 🐛 Crop API is not appending a hash when the image styles are converted to WEBP Needs review it solved my issues
I'm seeing the same issue and it using the core webp. I looks like crop_field_data isn't populated for any webp images
Ok thanks for the info, I'll have a look into possible solutions and let you know what I find.
I'm using https://www.drupal.org/project/next → which I'm currently trying to modify to work with node preview, so yes it does use oauth but is setup with it's own user, so won't be the same as the one editing the content. I guessing from your response it will only work if it's the same user.
marcus.williams → created an issue.
Yes that's perfect, many thanks for that
Ah ok I was trying to extend the existing graphql_compose_metatags so now just gone with a module that completely replaces it. For the schema one I just went with the easy option of returning the json for the schema as there's a lot of nesting going on in the schema
I've got a few modules now that may be of interest so I'll put a link to them on here in the next few day they include
Config pages
A version of edges with filtering
A version of Image Style that allowing selecting the styles rather that all variation of styles enabled, and also one for Responsive images
Search api
marcus.williams → created an issue.
This looks amazing, thanks for the quick response and looks like it's exactly what I was after. The only thing I'm unsure on is what it should do if there's only a single entity enabled i.e should it be
teaser {
... on ParagraphTeaser {
id
}
}
or should it just return
teaser {
id
}
Thanks for the update, I'll try and have a look at it as soon as I can. If it's opt in surely that would mean it wouldn't affect anyone who uses it as it currently is unless I'm missing something.
marcus.williams → created an issue.