Cannot resolve missing field handler errors from Defaults display

NB: I've looked through the queue and can't find a report of this as a UI bug; only particular instances caused by missing or unregistered plugins, etc.

When a field handler goes missing (in my case because I removed a CCK field) the Defaults display outputs a message like "Error: handler for node_data_field_profile_full_name > field_profile_full_name_value doesn't exist!" in place of a link to configure the field.

To resolve the error you can use another display to access the configure field screen for the missing field and delete it. Alternatively, you can add a new field and this will remove the error message and replace it with a link like "Broken/missing handler Full name" to the usual field configuration screen. This is a minor but annoying UI flaw.

I would expect that the error message would be, or be accompanied by, a link to the configure field screen allowing you to remove the field with the missing handler.

To reproduce:

1. Add a content type with a text field "woo".
2. Create a view and add the field "woo" to the view and save.
4. Edit the content type and delete the field "woo".
5. Open the view and note the error message and that there is no apparent way to resolve the error.