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.
We currently list all the test packages, whereas these were designed to only be used during testing. We should respect 'hidden = TRUE' in .info files, and not record these in our package management.
Comments
Comment #1
ergonlogicCommit 8d17191 in dev/site-packages fixes this.
Comment #2
anarcat CreditAttribution: anarcat commentedShouldn't this policy be decided in the frontend (and thefore be more overridable)? Can it be?
Comment #3
ergonlogicI really think we should just respect the 'hidden' flag. Are you suggesting that we should pass such an option down to Provision, or that we should gather everything, and start tracking which packages are hidden, so we can filter them from Views, etc.?
Comment #4
anarcat CreditAttribution: anarcat commentedI was asking whether or not this flag was actually propagated to the frontend, or whether it should be.
If it's not right now, i'm okay with it being blocked in the backend for now.
Comment #5
ergonlogicThe hidden flag is not currently passed to the front-end.
This currently filters out hidden packages when they're .info files are initially parsed.
So, is this RTBC, then?
Comment #6
anarcat CreditAttribution: anarcat commentedyes, except i haven't tested anything anywhere today. :)
Comment #7
ergonlogicMerged into hosting and provision from dev/site-packages.