Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Not sure how best to title this issue but the patch provided addresses an issue where one is using Facet API Pretty Paths AND have patched Facet API to constrain a facet to only allow one active item (See patch in issue: #1393928: Add a per-facet setting that allows only one item to be active at a time).
This is quick and dirty so hoping anyone who is using the above patch and also wants to use pretty paths can test.
Comment | File | Size | Author |
---|---|---|---|
facetapi_pretty_paths-fix-for-facetapi-issue-1393928.patch | 1.26 KB | jaydub |
Comments
Comment #1
dasjohi, thanks for your contribution! the patch looks clean to me.
i will wait until the until the facet api patch goes in.
Comment #2
dasjoComment #3
fagoPatch works fine for me.
Comment #4
Sumi CreditAttribution: Sumi commentedPatch works fine for me to.
Comment #5
khiminrm CreditAttribution: khiminrm commentedPatch works fine for me
Comment #6
jaydub CreditAttribution: jaydub commentedComment #7
dasjoThanks everyone for your feedback. Let's make sure, #1393928: Add a per-facet setting that allows only one item to be active at a time gets in and I will be happy to commit this one.
Comment #8
philipz CreditAttribution: philipz commentedLooks like it has been committed :)
Comment #9
radimklaska#1393928: Add a per-facet setting that allows only one item to be active at a time was commited and is now included in recommended release. I also tested the patch from this issue and it works. Thanks!
Comment #11
dasjocommitted to 7.x-1.x, thanks!
Comment #13
ShaneOnABike CreditAttribution: ShaneOnABike commentedSorry to nag but could we release a new version. This bug pretty much halts any proper use of FacetAPI after they repaired it to allow for hidden values. I had _no clue_ that this module was blocking htat from working (~2 hours later) :/
Pretty pleaaaze!