1

All of sudden, cannot add views or save the existing one.

Receiving this error:

The website encountered an unexpected error. Please try again later. Error: Unsupported operand types in Drupal\Core\Config\TypedConfigManager->getDefinitionWithReplacements() (line 186 of core/lib/Drupal/Core/Config/TypedConfigManager.php). Drupal\Core\Config\TypedConfigManager->getDefinitionWithReplacements('label', Array) (Line: 101) Drupal\Core\Config\TypedConfigManager->buildDataDefinition(Array, 'Content', 'label', Object) (Line: 151) Drupal\Core\Config\Schema\ArrayElement->buildDataDefinition(Array, 'Content', 'label') (Line: 26) Drupal\Core\Config\Schema\Mapping->getElementDefinition('label') (Line: 35) Drupal\Core\Config\Schema\ArrayElement->parse() (Line: 83) Drupal\Core\Config\Schema\ArrayElement->getElements() (Line: 57) Drupal\Core\Config\Schema\ArrayElement->get('uuid') (Line: 179) Drupal\Core\Config\StorableConfigBase->castValue('uuid', '48bfba9b-d116-4e8a-935b-7940ec90ed65') (Line: 212) Drupal\Core\Config\Config->save() (Line: 280) Drupal\Core\Config\Entity\ConfigEntityStorage->doSave('content', Object) (Line: 392) Drupal\Core\Entity\EntityStorageBase->save(Object) (Line: 259) Drupal\Core\Config\Entity\ConfigEntityStorage->save(Object) (Line: 364) Drupal\Core\Entity\Entity->save() (Line: 637) Drupal\Core\Config\Entity\ConfigEntityBase->save() (Line: 986) Drupal\views_ui\ViewUI->save() (Line: 321) Drupal\views_ui\ViewEditForm->save(Array, Object) call_user_func_array(Array, Array) (Line: 111) Drupal\Core\Form\FormSubmitter->executeSubmitHandlers(Array, Object) (Line: 51) Drupal\Core\Form\FormSubmitter->doSubmitForm(Array, Object) (Line: 585) Drupal\Core\Form\FormBuilder->processForm('view_edit_form', Array, Object) (Line: 314) Drupal\Core\Form\FormBuilder->buildForm('view_edit_form', Object) (Line: 48) Drupal\Core\Entity\EntityFormBuilder->getForm(Object, 'edit', Array) (Line: 226) Drupal\views_ui\Controller\ViewsUIController->edit(Object, NULL) call_user_func_array(Array, Array) (Line: 123) Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber{closure}() (Line: 574) Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 124) Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97) Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber{closure}() call_user_func_array(Object, Array) (Line: 144) Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 64) Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 57) Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 47) Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 99) Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 78) Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 50) Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 47) Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 50) Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23) Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 656) Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

Anyone could point me to right direction?

closed as too broad by Clive Jun 24 '17 at 14:26

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Please, provide more details, maybe a snippet of your code – Dmitry Kaigorodov Jun 24 '17 at 11:45
  • 1
    Yeah, that's the thing, I haven't change anything else, but I doubt. I will have to uninstall modules one by one to find out if it is the module. – Adarsh Khatri Jun 24 '17 at 11:48
  • Without specifics and a snippet of code, the only answer I can give: uninstall modules one by one and see what causes the unexpected interaction. – Dmitry Kaigorodov Jun 24 '17 at 12:13
  • 1
    We can't debug the site based on a single error message and no context from here I'm afraid, it needs to be done by someone with access to the code and environment. When you have some more information please edit it into the question and flag for reopening – Clive Jun 24 '17 at 14:28
  • Real error: my stupidity. I had renamed one of the views.view.my_view.yml to .yml.to, so that it will not be called (my init thought). This was interfering with the Drupal. I had to completely remove that file from the config/install folder. Hope this will save some time for other drupal learner in future. – Adarsh Khatri Jun 25 '17 at 9:41

Browse other questions tagged or ask your own question.