The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.With the new project browsing by date http://drupal.org/node/33803, we're using the max changed value from the project's releases as the date. But if projects don't have releases, they aren't listed. See http://drupal.org/node/48054#comment-71775.
A simple fix, that would also allow us to simplify the code, would be to update the project node's changed value whenever a release is updated. That way we could simply sort by the project node's changed value (saving some joining and the use of a group by).
Anyone see any disadvantages to/problems with making this change?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | project-date-browsing.patch | 2.2 KB | nedjo |
Comments
Comment #1
nedjoWell, the idea of changing the project date didn't pan out very well. The problem is that we often need to browse by a given release number--so we need to use the particular release's date.
This patch instead says, use the node.changed value if we're not browsing by releases, otherwise use project_releases.changed. This should fix the problem of sites not filtering by release not seeing anything when browsing by date.
Comment #2
drummI haven’t seen any other requests for this. Personally, I think release date should mean exactly that, and only that.
If we did want to revive this, it would probably be a straightforward change in
project_release_apachesolr_index_document_build_node().