Problem/Motivation

When creating or updating a feature, the list of views that can be selected also includes views that are defined in code (both overridden and unaltered).
It is possible to select such a view to be added to the feature and build it. The usual "feature written" success message is shown - but views are not added to the feature. In a case where there are a large number of views defined in code and some overridden (as would likely be found with drupal commerce), this behavior can be very irritating. It took me a while to see the pattern of which views would cause the failure.

Proposed resolution

a) Do not include views in the select list that features is unable to export.
or
b) Display a notification informing the user about the components that were not exported and explain why.

Comments

hefox’s picture

hefox CreditAttribution: hefox commented
Version: 7.x-2.3 » 7.x-2.x-dev

Surprised there is not a patch for this

Patches welcome, a) is likely easiest approach -- don't include default views/components that are not part of existing features.

cjoy’s picture

cjoy CreditAttribution: cjoy commented
Related issues: +#1961734: Add support for exporting admin views in Features

While a view defined in code may not be exportable itself, the "parent" module will be added as a dependency to the feature.
I am personally not sure how useful that really is, but reading #1961734 I understand that this was a desired behavior at one point.
In that case, option a) (hiding the view) might be a regression?