WSOD when trying to add certain entity types as parameters

I've pushed a possible fix to the latest 1.0.x branch. If you'd have time for a quick review, I'd appreciate it. Thanks!

that's odd. well at the moment due to the other issues fatal error i am unable to retest in the project i've initially ran into the WSOD. but i've created a new project now and added and created more or less the identical setup. problem is the first two parameter types i dont see in the parameter option list anymore. URL alias item is the only type i still see. but there i can confirm that the WSOD is gone.

ok now i am able to access my initial project again. there the event item still has an error:

The website encountered an unexpected error. Please try again later.

InvalidArgumentException: Field is unknown. in Drupal\Core\Entity\ContentEntityBase->getTranslatedField() (line 587 of core/lib/Drupal/Core/Entity/ContentEntityBase.php).
Drupal\Core\Entity\ContentEntityBase->get('') (Line: 628)
Drupal\Core\Entity\ContentEntityBase->set('', 'en') (Line: 415)
Drupal\parameters\Plugin\Parameter\Content->buildConfigurationForm(Array, Object) (Line: 182)
Drupal\parameters_ui\Form\ParameterForm->buildForm(Array, Object, Object, Object)
call_user_func_array(Array, Array) (Line: 534)
Drupal\Core\Form\FormBuilder->retrieveForm('parameters_parameter', Object) (Line: 281)
Drupal\Core\Form\FormBuilder->buildForm('Drupal\parameters_ui\Form\ParameterForm', Object) (Line: 222)
Drupal\Core\Form\FormBuilder->getForm('Drupal\parameters_ui\Form\ParameterForm', Object, Object) (Line: 239)
Drupal\parameters_ui\Controller\ParametersUiController->parameterAddForm('content:danse_event.danse_event', '', Object, NULL, NULL, NULL)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 581)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 163)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 74)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 680)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

same for the notification item:

<code>The website encountered an unexpected error. Please try again later.

InvalidArgumentException: Field is unknown. in Drupal\Core\Entity\ContentEntityBase->getTranslatedField() (line 587 of core/lib/Drupal/Core/Entity/ContentEntityBase.php).
Drupal\Core\Entity\ContentEntityBase->get('') (Line: 628)
Drupal\Core\Entity\ContentEntityBase->set('', 'en') (Line: 415)
Drupal\parameters\Plugin\Parameter\Content->buildConfigurationForm(Array, Object) (Line: 182)
Drupal\parameters_ui\Form\ParameterForm->buildForm(Array, Object, Object, Object)
call_user_func_array(Array, Array) (Line: 534)
Drupal\Core\Form\FormBuilder->retrieveForm('parameters_parameter', Object) (Line: 281)
Drupal\Core\Form\FormBuilder->buildForm('Drupal\parameters_ui\Form\ParameterForm', Object) (Line: 222)
Drupal\Core\Form\FormBuilder->getForm('Drupal\parameters_ui\Form\ParameterForm', Object, Object) (Line: 239)
Drupal\parameters_ui\Controller\ParametersUiController->parameterAddForm('content:danse_notification.danse_notification', '', Object, NULL, NULL, NULL)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 581)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 163)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 74)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 680)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

the url alias parameter remains fixed

is it possible that the wsod is caused in danse now? so that the initial wsod got fixed and since the two errors from the difference parameters are identical it is an indication that the remaining problem is caused by a problem in danse?

is it possible that the wsod is caused in danse now?

There may be a possibility, however the Parameters module should ideally also be able to deal with that situation. I've pushed another possible fix for the mentioned problem in #6. Maybe it's also now working when using items of danse?

yep it looks like your last change fixed things. i've went through the whole select list and retested all the available options. the two errors linked in #6 are gone now and no new errors turned up. nice!

That's great news, many thanks for re-testing this!

Automatically closed - issue fixed for 2 weeks with no activity.