-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRAFT Drupal 11 compatibility. #191
base: 8.x-1.x
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, we might just need to do a little testing on the self::MAIN_REQUEST
change in the Url registrar class to ensure its compatible with d9/10.
I did a quick test using Umami for D9.5, D10, D10.1 and D11 and they all seemed fine other than D11 didn't process the webp image on the
|
@steveworley Would you prefer we merge this or park it until later given the UPDATE: Note that page/image looks fine on the Drupal side. |
I think we should try and see if we can resolve the |
Sounds good. Moved this to draft for now. |
Updated D11 test site and tested again and am seeing that this may be a responsive image issue or an Umami profile issue. I see the webp image at some widths and not others. I see webp images in Quant. The markup has:
And Quant has: |
It looks like this is where the Umami profile got the responsive images (webp) added: https://www.drupal.org/project/drupal/issues/3349447#comment-15184905 |
It doesn't seem to be a Quant issue. Once the responsive images are generated in Drupal, they do get seeded. For some reason the |
Okay... used emulator to go more narrow and then tiny showed up and was seeded. So... the main issue is that for some reason the Quant code in |
I think I figured it out. In some cases, the Quant code is pulling in the
I assume this is during the parsing the srcset. I'll see if I can find the regex for that. |
|
||
// Handle responsive images by removing extraneous data like ` 1x`. | ||
// @todo Fix this in the Quant infrastructure. | ||
if ($this->fullPath) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code looks fine, but I'm not sure why were transforming path on disk — do image styles not include the 1x
when resaving?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@steveworley We're not changing the path on disk afaik. In some situations (unknown why, assume a core bug), when you get the "full_path", it shows a space and then 1x
at the end even though that is not correct and should not be there. I assume there is some bug somewhere parsing the srcset value.
Stu said he will handle this at some point on the infra side, but this is just a workaround for now.
Without this workaround, then some of the image styles may not be created if they don't exist already.
We shouldn't merge this yet because some of our dependencies are D11 compatible yet. Moving this to draft for now. https://www.drupal.org/project/purge - not compatible as of 19 Jan 2024 |
Updated the issue with the D11 status of module dependencies. Still waiting on 3 of them. |
We shouldn't merge this yet because some of our dependencies are D11 compatible yet. Moving this to draft for now.
https://www.drupal.org/project/simple_sitemap - not compatible asf 5 Jul 2024 [D11 issue]
https://www.drupal.org/project/tome - not compatible as of 5 Jul 2024 [D11 issue]
https://www.drupal.org/project/webform - not compatible as of 5 Jul 2024 [D11 issue]
https://www.drupal.org/project/token - dev version is compatible as of 18 May 2024
https://www.drupal.org/project/purge - compatible as of 28 Jun 2024
Although we don't need to provide D11 support yet, there are quite a few modules that already do support D11. Someone provided a patch so I decided to test it. It worked with one minor tweak.
See d.o issue: https://www.drupal.org/project/quantcdn/issues/3389070