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.
would it not make more sense if the permissions to handle tracks and albums were in the feature providing those entities? otherwise wouldnt we have to make pushtape_admin depend on pushtape_discography?
Comments
Comment #1
zirafa CreditAttribution: zirafa commentedThe reasoning here is that configuring permissions only works if you have roles, and configuring roles should definitely be separate from discography (so that discography can be a standalone feature). Pushtape Admin is a convenient place to do all of this as it is unlikely to be installed separately. I suppose it wouldn't hurt to list dependencies, but it's also not a high priority atm.
Comment #2
discipolo CreditAttribution: discipolo commentedi merely thought we might wanna add the relevant permissions to our news and events feature aswell, making sure they depend on pushtape_admin so the correct roles exist. in that case i guess doing the same with discography would be logical.
way it is pushtape_admin depends on discography, if we add events and news related permissions to pushtape_admin in would depend on three features (since the contenttypes we are giving permissions for dont exist?) or is there something i am unaware of that would prevent pushtape_admin from depending on news,events and discography? features_exclude maybe?
Comment #3
zirafa CreditAttribution: zirafa as a volunteer commentedClosing due to inactivity