Hi,

I have a big problem with views of Drupal 8.
I added a new field in the taxonomy A. Then, in a view, i added a contextual filter using this field.
On the local environment, everything works. While, in the test environment and after deployment, it shows me "Broken / Missing Handler" instead of the filter name on the edit view screen.
Do you have an idea about the problem ?
FYI : I share the same configuration between local and test environments
To export the config: I use "drush cex" and to import it, i use "drush cim"

Thx

Comments

bendev’s picture

I have exactly the same issue

It is working locally on OSX and Linux VM (4 different machines)
It is not working on stage ubuntu and prod debian LAMP (2 differents servers)

This must be somehow related with environment settings.

I first thought to php version but now everything is in PHP 5.6

aamouri’s picture

Hi bendev,

Thx for your message.
Can you Found a solution for this problem ?

bendev’s picture

Yes the issue was with case sensitive characters in the name of folders and subbloders...
One folder name used a lower case in the linux environment and this was upper case locally on OSX.
The folders were versioned with git but somehow this was not taken into account.

So try to check your folders paths for capital letters...

aamouri’s picture

I did not understand you very well.
You talk about which folder/subfolder name ?

bendev’s picture

in my case this was a custom module with custom plugin (views filter) So I was referring to the folders and subfolders of my files.

If you don't have a custom module, then this is a different problem. May be try to flush your cache, move the order of the filters or to rebuild the view from your other environment

jespermb’s picture

I am having a similar issue. From what I have found I can see that fields i have created on my local site can't be found in views after they have been imported. I am still trying to find the source of this issue.
It can be recreated by:
* adding a field to a content type.
* add it a a filter in a views.
* Export the content type and view
* Import it on another site
* Revisit the view on the new site.
* It now contains a broken/missing handler and when trying to re-add the field it can't be found in the list of available filters.

vlledo’s picture

Hi @jespermb I have exactly the same issue, except I created the new field (in the new site) loading config files programatically and using EntityDefinitionUpdateManager::applyUpdates().

Have you found a solution?

bkosborne’s picture

Same problem for me, except it wasn't a filter I added, it was just adding the field to the view.

I solved this by deleting the field from the content type then importing config again. I did get an error message when importing the config, but the error was blank, and the view was fixed.

sabda.wiguna’s picture

export key_value table and import - drush cr fixed the problem, but not good solution

TheodorosPloumis’s picture

I had the same issue when I have removed a Views plugin from the system that was used on Views. The issue solved when I cleared the Views caches (admin/structure/views/settings/advanced).

Views Cache clear

TheodorosPloumis.com - Drupal developer @ eworx.gr.

sajiniantony’s picture

Having the same problem.Unable to add taxonomy filters in views--getting broken missing handler option in drupal 8.3.4

sajini

chicodasilva’s picture

Hi,

I am having the same problem with when importing config from Search API Index.

I have to import again "drupal config:import:single " after a clean site install.

Jeroen Dost’s picture

I had the same problem and searched the key_value table for the record responsible for the issue. I finally found that the record with collection=entity.definitions.bundle_field_map and name=node (in my case it was a field for a node) did not have the same value. After inspecting the content with CAST(value as char) it was missing exactly missing that field.

So I copy-pasted it from the development server and it was no longer broken/missing.

kakar’s picture

I had the same problem and one the filed which has a lot of data on it.
the solution

  • dump field tables node__field_test, node__revision_field_test
  • delete the fields from UI
  • run config-import if not using configuration then create the fields
  • run the insert statement 
dustin.gates’s picture

I ran into this issue as well, but I didn't want to manually edit the database or export/import content. I stumbled across this custom Drush command: https://gist.github.com/swichers/d0141a3ab14d93835d09943684480ee0 

I set up a quick module for it, installed it on my site, ran drush rfm, confirmed a pile of fields that weren't available in my views were listed as needing to be added and hit y. 

I saw the Used In values on /admin/reports/fields update to display info for the newly updated fields and am now able to add those fields in views. This also fixed the broken/missing error on views that were previously linked to these fields. No content loss.