mably → created an issue.
Sill being hit by the problem, so it looks like it's not really fixed.
Stage File Proxy is fetching .jpg styled files instead of .jpg.webp...
Any solution?
Sill being hit by the problem, so it looks like it's not really fixed.
Stage File Proxy is fetching .jpg styled files instead of .jpg.webp...
Any solution?
Yep, the MR must be slightly updated to work without jQuery but it shouldn't be too difficult.
Can you try to create a new branch/MR then?
I changed the MR's target to 2.0.x. Looks like a rebase is still needed though.
This issue's MR needs to be rebased against 2.x. Thanks.
Hi @lincoln-batsirayi, could you create a new MR for the 2.0.x branch? That would be great.
Includes fixes for the two related issues.
-
Fix included in the following issue: 📌 Switch to Vanilla JS Active .
Any feedback will be greatly appreciated.
Fix included in the following issue: 📌 Switch to Vanilla JS Active .
Any feedback will be greatly appreciated.
Can't we just use some default value when the new configuration is missing?
Shouldn't the rendering code also be fixed to avoid rendering raw content? 🤔
Working with the following exception pattern :-/\:
Included in release 4.3.0-rc1 → .
The "/" probably requires some specific escaping. Will have a look at it.
The "boundary exceptions" field will now be displayed only when "Match full-word" is activated:
Match full-word is required in fact.
We should make that clearer in the configuration form.
Could you give it another try with "match full-word" activated?
@sirclickalot feel free to give a try to this issue's MR.
Still wondering what kind of character, besides the hyphen possibly, we could remove from the list of word separators.
Ok, we are currently separating words in text using the following regexp when "full-word mode" is activated : "/\b(bit)\b/"
You want to be able to replace it with something like: "/(?<!\w|-)bit(?!\w|-)/" that removes hyphen from word separators.
Does I understand it correctly?
Not sure to understand how it should work... 😉
I have added a few comments to the MR.
Could someone open a MR on 2.0.x please?
It's merged!
That's not a Drupal 11 feature.
Do not reopen this issue but rather create another issue if you have a specific documentation request to make.
4.x branch created, MR's target changed to 4.x.
@albert-volkman could you fix the Gitlab CI warnings so I can merge your MR?
It's a Drupal standard feature that has been added to the 3.x version of the module.
The cache busting parameter should be added automatically.
As you can see there: https://www.bordeaux.fr
Have you tried removing those ?v=blJXMRWeAF parameters from your icons urls?
They should not be there.
A repeatable scenario allowing to reproduce the bug on a fresh Drupal 11 instance for example.
More than one thousand sites are using the 3.x version without any problem.
You must provide more information to enable further investigation.
Thanks a lot @albert-volkman, that's a really nice upgrade!
Should we create a new 4.x development branch for this update?
Let's wait a few days before merging.
Added the links on the module Front Page.
I'm not sure those modules are really similar in fact.
Our module is not trying to render anything, letting that to the site's theme, but just add some extra data for improved accessibility.
We really need this feature, can someone review it, please?
We'll be happy to proactively answer any questions.
FYI it has been successfully deployed on a high traffic website (bordeaux.fr) for several weeks.