Problem/Motivation
If I create a brand new, vanilla instance of Drupal 8.3.7, install the Redirect module (8.x-1.0-beta1), and then create a custom View (taking all default options) on the Redirect entity, there is a "Broken/missing handler" error showing in the fields section.
Proposed resolution
Implement a sensible default field when creating a new view for Redirects.
Remaining tasks
- Write a patch
- Review
- Commit
User interface changes
When creating a new view for Redirects, the Fields section shows the 'from' (redirect_source__path) property of a Redirect.
API changes
None.
Data model changes
None.
Comments
Comment #2
karenann commentedI am also seeing this.
I added a screenshot at https://www.drupal.org/files/issues/2018-06-19/Screen%20Shot%202018-06-1...
Comment #3
mrdalesmith commentedI'm using Redirect 8.2 on a Drupal 8.5.6 install, and have seen the issue described at https://www.drupal.org/node/2859493. That issue has been closed with a comment that a custom view can be used to show redirect information: in attempting to create a new view to display redirects, I hit this issue.
I'm not as up on Drupal 8 as I am 7, but I can't see an integration of \Drupal\views\EntityViewsDataInterface or a use of hook_views_data(): is it possible that the views implementation is incomplete?
Comment #4
idebr commentedViews defaults to the 'redirect_source' field that is configured as the redirect label. Since this is a composed field, I suggest we change the default Views field to its 'path' value. When creating a new view for Redirects, the Fields section shows the 'from' (redirect_source__path) property of a Redirect.
Comment #5
laravz commentedAfter applying the patch from #4, I no longer see the broken/missing handler error and I can see that the redirect source field has been set as a default. I'm personally okay with setting the source as a default, however, perhaps it would be a good idea to set the redirect (To) field as well.
Comment #7
berdirworks for me, thanks.