Can't use fields after updating

I confirm this and reverted to 3.7 too.

Hello,
We can confirm the same issue, after upgrading Views from 7.x-3.7 to 7.x-3.8, most of our views stopped working because they got broken handler message. Out of about 30 views, about 20 were affected.
The only way to tell if they are broken is to either check the page they are generating or edit the view and click on one of the fields in the view - that will cause all fields in the view to be re-checked and broken handler message will appear.

Reverting module back to 3.7 and refreshing modules page did solve the problems.

Here are some additional details in case that will help:
- user fields broken (username, email etc.)
- author fields broken (when using Content: Author relationship)
- body field broken when pulling from different content types
- most Ubercart views/fields broken except Title
- CiviCRM fields are OK

This is a major problem because existing views stop working silently, no error is produced during upgrade. The issue affects most fields.

Did anyone managed to reproduce that problem with a clean drupal + views installation? These kind of issues cannot be fixed unless
you can reproduce it, seriously.

@kasiawaka
Could you try to do me some favor?
Can you put in includes/view.inc in function _init_handler() there are the following lines:

if (!$handler->access()) {
  unset($handlers[$id]);
}

can you please change them to:

if (!$handler->access()) {
  unset($handlers[$id]);
  debug('access denied: ' . $key . ':' . $id);
}

Then go to the admin page and have a look whether you see some debug messages...

I believe this is the same issue coming up here https://drupal.org/node/1860380. For me, turning off Views Data Caching in the Advanced tab of Views Settings: /admin/structure/views/settings/advanced brought all of my fields back to my views.

I believe this is the same issue coming up here https://drupal.org/node/1860380. For me, turning off Views Data Caching in the Advanced tab of Views Settings: /admin/structure/views/settings/advanced brought all of my fields back to my views.

We've tested about 15 sites that were upgraded to Views 7.x-3.8 and we could not re-create the problem.

On the one site that was affected, clearing site cache did solve the problem.

That site that had an issue was reporting errors:
Notice: Undefined index: created in views_handler_filter->accept_exposed_input() (line 1273 of /var/www/vhosts/sitedomain/httpdocs/sites/all/modules/contrib/views/handlers/views_handler_filter.inc).

We will do some more testing to see if we can re-create the problem.

Downgrading the issue to Minor because the problem appears to be only affecting some sites, possibly those with heavy caching turned on.

I can see this error only when I set default language to be Slovak (not English). When I English back to default it works as usual.

Error is on the path site.sk/forum/active (Advanced forum module is installed).

I see also this debug message:

Debug:

'Handler views_handler_field_taxonomy tried to add additional_field vocabulary_machine_name but taxonomy_vocabulary could not be added!'

in views_handler_field->add_additional_fields() (line 142 from /data/sites/all/modules/views/handlers/views_handler_field.inc).

Hope this helps to recreate error.

I can confirm this on a Commerce Kickstart base installation. Many of my views were affected, including those provided by Commerce Message.

Reverting to 3.7 magically solves the missing fields/ broken handler issues.

Per comment 5 above, and after reading both, closing this as a dupe of #1860380: "This view has been automatically updated to fix missing relationships". Referenced entity relationships removed. .

Seems like the most consistently working solution for a lot of people is what was detailed in comment 6 here.