- 🇬🇧United Kingdom d.fisher
This issue has had no activity for 6 years. I've just become a maintainer here and I'm spinning lots of plates. Can anyone confirm that this issue is fixed or persists? Many thanks.
- 🇺🇦Ukraine ruslan piskarov Kyiv, Ukraine
Hi @d.fisher, I use the #15 patch on many sites.
- 🇬🇧United Kingdom d.fisher
Working on updating the patch in #15 in a branch so pipelines can be run.
- 🇬🇧United Kingdom d.fisher
So I've created MR!10 which now satisfies all the gitlab pipelines. This will need thoroughly testing by someone who has this issue on a site and can check if MR!10 still resolves the issue for them. The MR will need to applied against the 2.x branch or latest 2.x tagged release (2.0.2) at the time of this comment. If that works we should be able to cherry pick the changes to the 8.x-1.x branch as well for those who are still using Drupal 9 (hopefully nobody at the point)!
If we can get two people to confirm this is working as expected using the new MR then we can mark as RTBC and I'll get it merged and fixed.
In order to apply the MR as a patch simply take the MR URL:
https://git.drupalcode.org/project/file_browser/-/merge_requests/10and add .patch to the end like this and apply it in your composer patches:
https://git.drupalcode.org/project/file_browser/-/merge_requests/10.patchThank you all for you effort and patience on this issue. Let's see if we can get this one over the finish line now!!