Call to a member function options_validate() on a non-object when adding a field

I have the same issue when saving a new field to a view involving message's.

*EDIT* Actually this occurs because the view was locked, although I never performed any action that indicated I was locking the view. If I unlock the view then it works fine. I think the reason for this is that none of the people mentioning the issue actually did any intentional locking and there is no error handling for this use case.

This got me too. In my case it's when adding a custom integer field as a sort to a EFQ Content View (built using the efq_views module).

I tried wrapping that line in "if (is_object($form_state['handler'])) { }" as a quick hack but that just broke things more. I'll debug ASAP.

In my particular circumstance, this is happening when trying to add a sort to a view that is inheriting sorts from the default display. When it builds the form, the new field is an option on the default display ($this->default_display->get_option('sorts') returns my new sort), but after submitting the form, during validation, this new sort is NOT on the default display of the view. In turn, the handler is never added to $form_state. Digging in deeper now, but as with any Views bug, I'm never sure how deep this rabbit hole goes. :)

Hmm, oddly enough, after a bit of tinkering with this, an old Lock appeared on the view. Breaking the lock fixed the issue. I wonder if this was somehow a stale cache item that didn't get purged properly?