Hi @mydot, could you give a try to this issue's MR please?
Included in 3.2.0-rc1 → release.
Included in 3.2.0-rc1 → release.
Javascript is probably the way to go using some kind of MutationObserver.
Is the header block updated when the view is refreshed using Ajax?
Not sure the problem is related to this module...
@isalmanhaider you replaced the issue summary with your comment.
Thanks @tanguy_mervant!
Ok, I get it, let's merge it as is then.
@michael.acampora how do you get a select in your range filter ? I only have simple min/max input fields.
mably → made their first commit to this issue’s fork.
mably → changed the visibility of the branch 3527046-cvfb-submodule to active.
mably → changed the visibility of the branch 3527046-cvfb-submodule to hidden.
Thank you for your feedback, I'll merge it.
@natts like this?
@natts, something like this?
In our case, we validated the display mode configuration deletion a bit too fast and completely lost the data related to several fields in various entity types. Hopefully we had daily backups.
You should find the code in Drupal generated javascript code.
mably → changed the visibility of the branch 2.0.x to hidden.
Ok, let's close it as "Won't fix" for now.
Feel free to reopen it if needed.
Seems to work fine here. Thanks!
If really needed, this "flatten" feature could be added rather easily I think.
Hi @nicoc, could you have a look at this issue's MR and tell us if it fixes the problem?
mably → made their first commit to this issue’s fork.
The Gitlab CI warnings and the failing tests need to be fixed
@divyansh.gupta did you have a look at your MR changes before setting it to "Needs review"?
Looks like it's rolling back all the recent updates to the dev branch...
Not sure the rebase was done properly.
I tried to implement the Configurable Views Filter Blocks compatibility in a dedicated submodule.
If it works fine, we could merge it as is as it doesn't impact too much the original module.
Add to do significant refactoring of the original JS code though.
mably → made their first commit to this issue’s fork.
Just installed the 2.0.x dev version of the Domain module on a fresh Drupal 11 install without any problem.
Could you give us a repeatable scenario allowing to reproduce the bug from a fresh Drupal 11 install?
Do you have the full stack trace available?
We will rather for the translations to be available on https://localize.drupal.org
It's merged!
Will release 7.0.0 soon.
Hi @nicoc, thanks for the find.
Implemented a slightly different solution in the MR.
Could you give it a try and tell me if it fixes the warning?
mably → made their first commit to this issue’s fork.
We are only querying the values of the filters, so there shouldn't be many.
Unless I miss something.
Just checked, works fine here. We need more details to be able to help.
getActiveDomain shouldn't be looping indefinitely anymore on 2.0.x dev branch. Could you give it a try?
Hi @prosaicpoet, could you create a MR please?
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.