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.
Now we've had the Facet API integration for some time, I guess we should drop the old, custom Facets module completely before we do a stable release.
Comments
Comment #1
davidseth CreditAttribution: davidseth commentedRather then get rid of it before the RC I would wait. This gives people a chance to upgrade without throwing everything out. Then you could say that the 2nd RC would completely get rid of this old Facet code.
Comment #2
drunken monkeyThat's not what an RC is for. Release candidate means it's what I propose as a stable release. Having still things that will surely be committed before the stable release at this point doesn't make any sense.
Also, if everything's OK, there won't even be an RC 2.
On the other hand, we really didn't have a Beta release since this changed (which is stupid anyways), so it would be hard for people not using the dev.
Therefore, it might be better to remove it in 1.1 …
Comment #3
drunken monkeyOK, we'll do this in 1.1 and note it in the 1.0 release notes.
(Unless there are very good arguments against that.)
Comment #4
davidseth CreditAttribution: davidseth commentedI think that is a sensible approach :)
Thanks.
Comment #5
drunken monkeyFixed in 1.1.
Comment #7
DamienMcKennaWould it be possible to please clear up the project's information regarding what is necessary for facets to work? Right now this issue suggests that Facets API is necessary, the project page says that facets will only work with the Solr storage engine (without saying any other modules are necessary), and the Search API DB issue queue suggests it already supports facets.