Sounds great! And about versioning, and planning ... it's complicated :) But it does look like most projects are using the 2.x dev branch convention.
Wouldn't it be nice to land this, and get Cypress test support in Automated Testing Kit?
I wanted to totally replace the default Taxonomy term page with a search API, Facets 3 and Facets Pretty Paths based View, and have term links point to my custom View instead.
I first tried to inject a "prefix"-path (the View page path /browse
) in the term link paths in the source with JavaScript, but failed. I eventually ended up redirecting all relevant term links via .htaccess
. Not ideal, but it works.
Term paths are for example /tag/window
or /cat/entrance
, and a .htaccess
rule redirects all URLs beginning with /tag/
or /cat/
to /browse/tag/window
or /browse/cat/entrance
, where the View page path is /browse
, and Facets Pretty Path "Pretty paths coder" is "Taxonomy term name - Use term name, e.g. /tag/blue"
This is a spammer, see https://www.drupal.org/forum/general/general-discussion/2025-07-10/reput... →
Strangely, the account is blocked, but this post remains.
I believe it's because some shells handle wildcards such as * differently, so in order to work, the parameter needs to be quoted https://superuser.com/questions/1722443/in-new-version-of-macos-i-had-to....
Sorry, I should have made it clearer that I am just a regular user of this module, and have no idea if it's possible or not.
But I think it wouldn't harm, if you made more or less the same feature request in the other project as well, and then connected the two issues, so that if it gets made in one, the other issue can be closed.
Your idea is great, and I hope it will become possible, in one of them :)
Thanks for confirming that there is a solution, so I'll connect the related issue.
I saw this, I believe while using Facets 3, and then adding Facets Pretty Paths.
I think it would be really helpful, if someone who knew the details could share the steps to fix this in Drupal 10. Perhaps something along these lines, under a new "Workaround" header?
Workaround for Drupal 10
You can patch Drupal 10 with these steps:
- Download the latest re-roll for Drupal 10.5 from comment #XYZ
- Set the update hook number to (what?)
+1 for the MR, thanks @chrisolof! Your updated code works well with Facets 3 and Better Exposed Filters (BEF) using the "Exposed filter widget" set to "Checkboxes/Radio buttons".
I hope it can get committed before too long. Perhaps you could consider applying to become a co-maintainer, to help move this great improvement along?
Thanks for reporting this @mlncn and improving the Facets eco-system. Perhaps a sentence could be added under "Steps to reproduce" that this is for the "Link" type? Because "Checkboxes/Radio Buttons" work well for me ...
I also noticed that the BEF Reset button ("Include reset button (resets all applied exposed filters)") doesn't work with Facets Pretty Paths ... Perhaps, if you already have a patch, an issue could be created?
I am still on Drupal 10.5.1 with Facets, and as others also get an "1406 Data too long for column 'route_param_key'" error from a string like this:
facets_query=&f0=&f1=&f2=&f3=&f4=&f5=&f6=&f7=&f8=&f9=&f10=&f11=&f12=&f13=&f14=&f15=&f16=&f17=&f18=&f19=&f20=&f21=&f22=&f23=&f24=&f25=&f26=&f27=&f28=&f29=&f30=&f31=&f32=&f33=&f34=&f35=&f36=&f37=&f38=&f39=&view_id=browse_motives_search_api&display_id=motives
.
Is a Drupal 10 backport worth considering, or is the recommendation to upgrade to Drupal 11?
The problem is that only a single value from a multivalue field is being output, like from a taxonomy term Tag field.
How can you output all values?
Thanks @prudloff, this would be a great addition. I wanted to review the patch, but ran into problems, and not sure of the best method to verify a cache hit ... Should I just check to see if these browser headers change?
{
"name": "x-drupal-cache",
"value": "UNCACHEABLE (response policy)"
},
{
"name": "x-drupal-dynamic-cache",
"value": "UNCACHEABLE (poor cacheability)"
},
To get this committed, you probably need to create an issue fork → (the green button), add the changes in there, and then create an MR. Thanks!
Thanks @cgoffin, would a patch for version 3 be possible, if it's relevant? I think I am seeing this error ...
TypeError: Drupal\facets\Plugin\facets\facet_source\SearchApiDisplay::getCount(): Return value must be of type string, none returned in Drupal\facets\Plugin\facets\facet_source\SearchApiDisplay->getCount() (line 460 of modules/contrib/facets/src/Plugin/facets/facet_source/SearchApiDisplay.php).
Thanks for clarifying @drumm, that going forward, GitLab is probably the place to pursue this.
As on drupal.org, GitLab has a priority::high
("Major") option. But my vision with this suggested feature, is that it should work on a personal priority level: An issue can have Priority Normal, if it's not an urgent problem, but many users may see great value in getting it completed -- such as a great .gitignore
out of the box, to onboard beginners. (
✨
Add gitignore(s) to Composer-ready project templates
Needs work
)
Maybe it could be something like a personal-priority::high
flag on GitLab? :)
That sounds good, though I think adding a single sentence with a link could work better, since there is already a documentation page we can link to. Advanced Views RSS Feed → seems like a tried and tested solution, and a good match for this use case, with ~3,800 modern Drupal installations.
We could add a short sentence to the first list item? (added sentence italicized)
1. You must have an RSS feed that contains only content appropriate for Planet Drupal. If you use Drupal, you can build a custom RSS feed → with Advanced Views RSS Feed → .
Since the sentence starts with "If you use Drupal" it's not a requirement, but a friendly tip.
Alternatively, the tip could be inserted in the intro text, right before the "Content that is great for Planet Drupal" header?
Revisiting this post, I still think it's an interesting idea, and you should consider creating feature requests @mvelanka, for example in these two projects below. Please link the issues to each other for full transparency, and share links to them here as well, after you have created them. Thanks:
Thanks for creating the new IP Limiter module and adding it here @idimopoulos, it looks great!
And if you have time at some point, this page could do with a review. Thanks!
There's a new https://www.drupal.org/project/ip_limiter → module which might work?
The IP Limiter module for Drupal allows you to limit the number of requests from a single IP address to specific paths on your site. This can help prevent abuse and reduce server load.
Or if it doesn't have the feature you're looking for, perhaps it could be added?
Oh, and another documentation page I created a while ago, which also needs to be added to the menu:
https://www.drupal.org/docs/administering-a-drupal-site/security-in-drup... →
Thinking some more about this, it would be sad if innovation and new Drupal issue features stopped, after a move to GitLab ...
Because, as a user, I could see this feature as useful, and not really care if it's a Drupal.org or GitLab customization in the backend.
Thanks for the addition @jeetmail, though it looks like the xargs
example got lost:
https://www.drupal.org/node/3340861/revisions/view/14019091/14074603 →
All right. Either way, this is your domain, so you call the shots.
There are already Drupal-centered tips, so your basis for rejecting my constructive improvement seems flawed.
Request to add a feed
You must have an RSS feed that contains only content appropriate for Planet Drupal. If your site uses Drupal, you can create a Drupal Planet taxonomy term and use it to tag any content you want to show on Planet Drupal. Drupal automatically creates an RSS feed for each taxonomy term, and you can submit that term’s feed URL in your Planet Drupal application. If you are not using Drupal, you will need to make sure your site can create a feed just for your Planet Drupal content. [my emphasis]
Request to update a feed
1. You must have an RSS feed that contains only content appropriate for Planet Drupal. If your site uses Drupal, you can create a Drupal Planet taxonomy term and use it to tag any content you want to show on Planet Drupal. Drupal automatically creates an RSS feed for each taxonomy term, and you can submit that term’s feed URL in your Planet Drupal application. Alternatively, you can use the Drupal Planet → module, which uses the Flag and the Views modules to create the feed. If you are not using Drupal, you will need to make sure your site can create a feed just for your Planet Drupal content.
Is it possible to tweak GitLab, and add new features, such as the one suggested in this issue?
You're welcome! I am not maintainer of the module, but judging from the features listed on https://www.drupal.org/project/matomo → , they seem to mainly (or all?) be Drupal-oriented ... so I would think that the approach is to let Matomo itself handle things configurable in Matomo, and Drupal-specific stuff in the Drupal module.
But maybe a maintainer can help clarify?
You can set this in Matomo itself, so perhaps try that? How do I exclude traffic from an IP or a range of IP addresses?
Did you find a solution? If not, the best place to ask is probably in the Commerce issue queue: https://www.drupal.org/project/issues/commerce →
Did you solve this? I would think that if a product was tagged with a term, it should get listed. Maybe you can add a very short use case? https://www.wrike.com/blog/what-is-a-use-case/
That's a Plesk related problem, maybe this can help? https://support.plesk.com/hc/en-us/articles/12377596215703-How-to-run-Co...
Still seeing this in Drupal 10.5.1, so it would be nice if someone else checked, and confirmed if this happens to them, or not.
Add a more important issue in the example.
You're welcome @dydave, I am glad I could assist you in improving Admin Toolbar! And it does seem like a slightly odd and limited dependency. But maybe in the past, they were much closer intertwined, and gradually they drifted apart, until the final break, today?
Your plan with breaking down the changes into bit-size updates for better management and easier roll-back if needed sounds like a great plan, and it's good to hear that this issue unblocks other areas of your plans for improvement. There's nothing worse than stalling, when you have momentum, and things are flowing. If too long time passes with no progress, you may forget the ideas and plans, and if far too long time passes, there's a risk of a complete halt in the process, and it never gets done.
So about helping each other out, I thought about a new feature a while ago, but think I didn't create an issue ... but now I finally did: ✨ Allow flagging erxtra important issues, to fast track completion Active . Feel free to add more suggestions for features, or other improvements if you see any 🙂
Thanks for reviewing this @xjm. Looking at the list again, you have a point and I tend to agree ... Maybe we should only add a new short date without time format?
About an upgrade path for the announcements feed Twig template, you may be right ...
I agree, there should be a prominent link to the Drupal Forum, instead of guiding everyone to a proprietary system, as opposed to drupal.org, where everyone has access, it leaves an eternal source, documenting historical decision and the thoughts behind them, the content gets indexed in search engines, etc.
You also raised this issue in February 2025 in About Slack for Support → (thanks!) and you could leave a comment in Forum link removed in the new drupal.org design: #3475832-109: Feedback on Modern Drupal.org Design → and 📌 Please put link to "Forums" back in the "Community" pulldown menu Active , sharing your support for the Drupal Forum?
I totally understand @bserem, it's important to not spread yourself too thin, by trying to cover too many tasks. So let's see how it turns out with your other application, which I hope you get!
No problem at all @dydave, thanks for keep on working on improving the Admin Toolbar code base and structure, I am very grateful! I have just taken a look at the decoupling issue, and will gladly look at other relevant issues.
So feel free to add them here, and I'll attempt to help with reviewing them, so long as my capabilities allow it 🙂
Great idea to decouple the two sub-modules, and make them independent of each other -- nice job @dydave!
I can confirm that with the MR, the two sub-modules are now operating as totally individual sub-modules, and you can install and use one without the other.
Installing them together or separately, all features still work, such as Search without Tools, and vice versa, all features are still present.
If I try to install just one or the other, only Admin Toolbar is required, as expected:
$ drush install admin_toolbar_search
The following module(s) will be installed: admin_toolbar_search, admin_toolbar
$ drush install admin_toolbar_tools
The following module(s) will be installed: admin_toolbar_tools, admin_toolbar
One thing I forgot to include in my "Add support for multiple Data Source Fields?" suggestion above, is how to select which Data Source Field to use in the Leaflet View. So I'll add it, to keep it all in one place.
Thanks @itamair for an epic explanation, much more than I could have hoped for. And thank you very much for the attention to detail, and even including a custom module example. It works perfectly, and I get the custom ranges, just like requested in the Issue Summary. Mille graze!
Based on your example and walk-through, I and anyone else interested in this, can absolutely now create our own custom Choropleth values and ranges.
About your thoughts of a future plans for a custom Color Scale (defining custom labels for legend values) via long text configuration, that could be a logical expansion to my suggestion in the Issue Summary, and I have extended the feature request with a new "combine value ranges, labels, and color scales" section.
If this "Custom" option is selected, the "Number of Classes" drop-down value should probably be disable (or ignored), since the number of elements are then in effect set. Also, if colors are set, the "Color Scale" drop-down value could also be ignored, I would think.
Add support for multiple Data Source Fields?
Another feature that would be awesome to have, is support for multiple Data Source Field's in a single View, since it looks like only a single Data Source Field is possible per View currently.
It's getting complicated though, and I am not sure what the best method would be ... I can think of two methods right now:
Scenario #1, Set source values in the Custom form
Could something like this work? (in a single form field or multivalue (paragraph-style) which ever is the least complicated to handle):
source: my_data_source_field
50-100|+50|#aa8c02
30-49.9|30-50|#cc4c02
25-29.9|25-30|#fe9929
23-24.9|23-25|#ffffd4
source: data_source_field_number_2
1000-10000|+1000|#aa9c82
100-999.9|100-1000|#cc4c02
1-99.9|1-100|#ffffd4
If this "Custom" option is used, the "Number of Classes" should probably be disable (or ignored), since the number of elements can vary.
Scenario #2, Paragraph-like "Add another"
Another solution could be to offer an "Add another"-button, which creates a complete extra "Choropleth Map Settings" below the current one, allowing an entirely different configuration for each Data Source Field.
Maybe that's better, since it retains the flexibility to use all the great configuration features? Then there would be no need to define a source key, and range, label, and color could be set for each data source, if so desired, and only this is needed:
50-100|+50|#aa8c02
30-49.9|30-50|#cc4c02
25-29.9|25-30|#fe9929
23-24.9|23-25|#ffffd4
Thanks for clearing that up @joelpittet. I do get the benefits of having a consistent and predictable development environment, which you know the ins and outs of -- that's always great to have.
Also, we can only progress by experimenting, and trying new things out, and the insights gained might result in constructive feedback-worthy experiences for the DDEV Drupal Contrib project itself, which may get implemented, so that it may improve, to the benefit of all the other Drupal projects in the end.
Thanks @laylalk for offering to maintain Arabic and @bserem for vetting @layalk, and recommending her. I agree that some parts of Drupal (such as the multilingual part) could do with some more focus.
@bserem: Since you already maintain several projects, and this project is "Seeking co-maintainer(s) -- Maintainers are looking for help reviewing issues." perhaps you could consider applying to become maintainer → ?
Often, a link is veiled SEO, so it's probably best if you remove the link:
https://www.drupal.org/docs/administering-a-drupal-site/troubleshooting-... →
Another approach could be to include all the commands in the CONTRIBUTING.md file, to get the optimal DDEV environment up and running for a project, since I see there are commands to run in CONTRIBUTING.md:
https://git.drupalcode.org/project/calendar/-/blob/8.x-1.x/CONTRIBUTING.md
I wonder which commands are saved by including the .ddev
folder? If it is mainly running ddev config --project-type=drupal
and installing Drush, then it seems to me a bit overkill (and in danger of versions getting outdated) to commit .ddev
, and the commands ddev config [...]
and ddev composer require --dev drush/drush
could instead be included as well, but maybe there are a fair deal more commands, and adjustments?
I had a look at adding a caption, and ended up using a custom module for more flexibility, and created an example in the Token documentation: https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →
I found the problem, a comment by @vladdancer helped me realize it's a Drupal core issue.
Thanks @w01f, though it looks like this issue is closed as duplicate, and work is getting done in #3031919: Bugs if user has blank email address → .
Great news, it just got really easy to install DDEV in Windows:
No problem, thanks @itamair! The credit got registered ("Leaflet Choropleth, 1 issue" is now in my profile) so it's great that it's easier to grant, even after an issue has been closed.
I created an issue about Big Pipe 🌱 [Meta] Big Pipe related issues, causing seemingly random failures Active . Have a great day.
Adding an issue.
Thanks for working on this! The MR works really well and fixes missing Captions settings in PhotoSwipe in Views.
About the current patch and removing settings, I can only partially replicate it. If I set a value like 'Image alt tag', collapse it by disabling 'Use third party setting' checkbox, and save, the setting does remain, like @joachim commented in #31.
But if I instead first set it to "- None -" and then save, it's no longer active, regardless whether I collapse it or not.
I do think it should be totally disabled (set to "-None -") if the setting is collapsed, by unchecking the 'Use third party setting' checkbox.
Since this can be very hard to debug and understand, and options are mysteriously missing from the Views UI in Contrib modules integration without any clue, resulting in a more or less "dead end", could this issue be considered bumped up to "Major"?
Thanks @vlad.dancer! Your tip about Views UI cleared up a Caption issue in PhotoSwipe, where it was missing in Views, and I created an MR to document a workaround in PhotoSwipe, until it gets fixed in Drupal core 🐛 photo filed - caption Needs work .
I added a tip in the documentation → , and created an MR for the README update, please review.
Administrators: Perhaps you can update the project page, adding something like this? Thanks!
In PhotoSwipe 5 the "Photoswipe image caption" option is present on the regular Display page of image fields (on
/admin/structure/types/manage/library/display
), but missing for the same image field in a View. The solution is Drupal core issue 🐛 Formatter third party settings missing from Views UI Needs work , and you can patch Drupal core → until it gets fixed.
Adding a note about Photoswipe image caption not working in Drupal core Views UI.
Good news, everyone! In ✨ [5.x] Make Photoswipe work with any ContentEntity entity type Active @vladdancer shared the cause of the problem, which is in Drupal core 🐛 Formatter third party settings missing from Views UI Needs work . After patching Drupal core (Views UI) with the MR from the issue, the PhotoSwipe Caption is available in Views.
Since it's not a PhotoSwipe bug, but we need to heed it, let's turn this issue into a documentation task, adding tips where relevant, like project page, README and documentation pages.
Thanks @wombatbuddy, I just tried the Media Library Edit module, and it works great: While creating a node with multiple Media images, you can upload them, and immediately add content to their Media fields.
It looks like this option was lost between 3.x and 5.x ... I no longer get custom fields offered in a Media type Display, like an "Author" field containing the photographers name. I tried the custom option with Tokens, but they were empty. I tried Media entities instead of a standard image (as individual nodes) to get the caption working, but failed (see 🐛 photo filed - caption Needs work ), but sadly this method also looks like a dead end ...
By the way, @marcoka I am curious if you have managed to get captions to work in Views in PhotoSwipe 5?
Because many report that the option is missing, see 🐛 photo filed - caption Needs work .
Thanks for adding this feature @kostiantyn. I was wondering just now what the difference is between the View modes "Photoswipe" or "Photoswipe Responsive", so I searched and found your issue.
I am also not sure how to set up "Photoswipe Responsive", so perhaps you could consider add a small description in the README as well, outlining the basic steps to set up? Or if you leave a comment here, I will gladly go through it, and add it in the README via the MR.
On a side note, I also hope captions can be made to work at some point, since that's also pretty much a requirement in modern web sites -- to have attribution of the images, but that's another issue ( 🐛 photo filed - caption Needs work ).
By the way, I would love to have a Leaflet Choropleth credit under my profile → as a badge of honour, so maybe that's possible?
As a side note, it has gotten easier to grant credit, and it can be done at any time now, even after an issue is permanently closed (perhaps after ✨ Grant credit for all closed issues, not just fixed issues Active ?).
So as a maintainer, you can simply check the box and save, and credit is given.
I did a test run together with @grzegorzbartman from Droptica.com in #3521696-13: Embed fonts to comply with EU GDPR → , and it worked well, so I updated the Credit documentation page https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett... → .
It works now, thanks @itamair!
My intention with adding Big Pipe related issues was to connect them, in case others run into something similar, look in the search engines and find this issue, or one of the other ones -- in which case they can visit this, or one of the other issues, and use as inspiration for a solution, depending on what their problem is.
Thanks for a fast reply @itamair, the new module is nothing less than spectacular, since users can now add a Choropleth so easily.
About the bug, thanks for trying to replicate it. It is really strange ... It happens with 1.0.2 and the latest Leaflet Choropleth dev-release in a fresh Drupal 10 installation in DDEV, with no customizations, so no specialized workflows, or anything. I also tried with Olivero and Claro themes as well, and it also happens there.
I found out some more details: It happens for any user with a role. So I added and removed the Content Editor role with the same result. I also looked at the source and noticed that a lot of JavaScript files were only loaded for a user with a role, and scanning the list, one stood out, since I have previously had strange JavaScript problems with that:
Big Pipe.
After uninstalling Big Pipe module, the Choropleth Legend is show in all scenarios.
Maybe you have disabled it, and that's why you don't see this problem?
I have previously used a non-standard Drupal sandbox myself for testing patches (for Admin Toolbar) with customizations, other modules, etc. and realized the value of using a fresh dedicated Drupal instance.
I hope you find a solution, and here's the issue: ✨ Add a setting to bypass the uniquifier if a path alias already exists Needs work .
Sure, that may be a bit outdated to use, and I updated it to web host.
Fantastic news, thanks @itamair! I just tried Leaflet Choropleth → , and it works extremely well. It is easy to configure, and makes adding Choropleth solution in Leaflet maps a breeze -- it used to require a fair deal of configuration, and manual steps. I am eternally grateful for your high level of maintenance of the Geofield/Leaflet-suite of GIS-modules in Drupal, and like here -- with Leaflet Choropleth -- expanding them with this new awesome feature.
This is now possible in Drupal 10, thanks to the new, amazing Leaflet Choropleth → module.
ressa → created an issue. See original summary → .
Thanks to everyone for sharing solutions here! I recently looked at this task, and updated the Drush documentation page, with a lot of inspiration from this Forum post: https://www.drupal.org/docs/develop/development-tools/drush →
I copy-pasted your awesome comment with a step-by-step set up for a symlink solution → , which looks really interesting, so thanks for sharing it @karolus!
Adding "Set PHP version with symbolic links" section from https://www.drupal.org/forum/support/post-installation/2023-01-18/drush-... → .
Add tips about using alias
to set path to PHP version, and allow using simply drush
.
Usually I just reinstall with Drush command drush site:install -y
or does it not work?
If nothing works, perhaps create an issue at https://www.drupal.org/project/drupal_cms → .
See also https://www.drupal.org/forum/support/theme-development/2025-06-25/solved... → referring to a documentation page I created more than two years ago (May 2023) but still not included in the menu.
By the way, I just stumbled over my documentation page I created in May 2023 about this ... so it exists, but has sadly not been added to the menu yet, Override strings in the interface without using full translation system → .
I created a new Guide: https://www.drupal.org/docs/extending-drupal/contributed-modules/field-g... →
Please let me know if I need to create a new issue for getting the documentation pages in my previous comment, and this new one published.
Thanks!
I created Drupal 11 documentation under https://www.drupal.org/docs/extending-drupal/contributed-modules/field-g... → in case someone wants to update and transfer D7 documentation there. See also 📌 Create Drupal 11 documentation pages for Field Group Active .
Some pages were added to the menu, which is great.
However, these are still not added in the menu, so cannot be seen by the users:
- https://www.drupal.org/docs/extending-drupal/contributed-modules/compari... →
- https://www.drupal.org/docs/administering-a-drupal-site/configuration-ma... →
- https://www.drupal.org/docs/administering-a-drupal-site/security-in-drup... →
- https://www.drupal.org/docs/drupal-apis/migrate-api/fixing-errors-due-to... →
To help keep us volunteers motivated to carry on creating documentation, it would be nice if someone could add them to the menu. Thanks.
Thanks for the explanation @xjm, that conclusion in 2014 does make a lot of sense, a sane decision!
And yes, let's discuss some more, though disabling the View method is still a too "round about" method as I see it, instead of a more direct method, of taking the bull by its horns, and dealing with the problem right away.
@mortona2k: About your vision of a quick fix UI, #2575547: Formalize patterns for delete/uninstall of configuration dependencies → may be relevant, but the last comment was more than nine years ago, so it seems stalled ...
In each of your use cases, would it be an acceptable solution to let the user know there is a task to do, before being allowed to proceed? I would think it is easier to code, since it could be streamlined to behave the same way in each case ... Something like this, where we could link to the View in question:
Your View X is using the Y content type fields, please remove it from the View X → before deleting the Y content type
Your View X is using the Y content type as Views filter, please remove it from the View X → before deleting the Y content type
Your View X is using the Y Views Display formatter, please remove it from the View X → before uninstalling the Y module
Thanks @xjm, sounds great! I attempted to add your suggestions to the Issue Summary, feel free to adjust if some things need tweaking.