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.Problem/Motivation
Currently, feature generation is done via a form where all configuration on the site is assigned to multiple features. This is useful, but limited in terms of customizing. It might be daunting to present an edit interface that allowed an admin to exclude/include/move config items in all detected features at once.
Proposed resolution
Another way to conceptualize the FEatures approach would be as feature suggestions. For example: present a simple page with a list of suggested features, based on analysis of the site (via the generation plugins). Click on a link to bring up the feature in edit mode, with suggested components. Or else enter a custom name + machine name + description to make your own, with a checkbox like "Add suggested components based on the machine name." This would be a bit like the 2-step Views admin UI for creating a view.
Comments
Comment #1
nedjoComment #2
mpotter CreditAttribution: mpotter commentedCool, I think this is exactly where I can get started with Features. Since I want Features to be more of a UI around creating config packages, I think having it fit in and augment or replace the config_packager UI would be a good starting point.
Let me play around with some ideas and then post something for you to look at.
Comment #3
nedjoSounds great. The current UI is really just a placeholder.
Linking to #2405039: Move feature set and profile configuration to settings page. Also opened related issue #2446917: Define Configuration Packager relationship with Features. One possible direction is: we remove the UI from Configuration Packager (except, perhaps, the settings mentioned in #2405039: Move feature set and profile configuration to settings page), and Features becomes a front end.
Comment #4
nedjoComment #5
mpotter CreditAttribution: mpotter commentedHere is the skeleton code for a new features_ui submodule within Features. Will be fleshing this out over the next week or so.
Comment #7
mpotter CreditAttribution: mpotter commentedCommit 9676318 is the initial refactor for moving all the UI into the features_ui submodule.
Comment #10
mpotter CreditAttribution: mpotter commentedCommit 8b0fca2 refactors the main Export form into more of a Features Listing form.
Some of the style and code was taken from the D8 Extension listing page.
Comment #12
candelas CreditAttribution: candelas commentedHello
It sounds very interesting. I hope I have time soon to test it.
As a user, I hope it is the right moment, what for me that I just started with Features, what I would also like to be implemented (I say in case it can help) is:
I hope you understand that I write this with all my best acknowledgment to your great work, trying to be a bit useful :)
Comment #15
mpotter CreditAttribution: mpotter commentedCandelas: Please do not post Feature Requests in this issue. This issue is for developers testing the 3.x build. Please create new issues for feature requests.
Features 8.x is a complete rewrite of Features 7.x so stuff like load time etc is no longer relevant. Only post here if you have installed D8 and are reviewing the code commits that have been posted.
Note that functionality in the dev version is not complete until you see an initial Alpha release.
Comment #20
mpotter CreditAttribution: mpotter commentedMost work lately has been on the Edit form. But the remaining work here for the main UI is adding support for new "action" buttons for importing/exporting individual Features.
Comment #21
mpotter CreditAttribution: mpotter commentedJust going to leave it as-is without any "actions". The two buttons for Download and Write are good.