ECA Form module conflicts with Entity Browser selection in Inline Entity Form

This sounds like being related to 🐛 ECA Form breaks complex IEF widget Active . Can you provide any more details from the logs please?

Logs are not present, the console is clean. I'm using the simple ief widget and the same behaviour is present if using the complex widget.

Logs are not present

There must be something somewhere. Either in Drupal's watchdog or in the PHP logs. It's hard to watch the video and getting an idea what's going on. If you really can't find any logs anywhere, we then need step by step instructions on how to reproduce this behaviour on a fresh Drupal installation.

@jurgenhaas I will come back with more information in the next couple of days, thanks.

I'm experiencing similar issue with Entity Browser display.

In my case, I have some custom ECA workflow created for one content type. Custom ECA workflow is utilizing multiple FORM: ADD AJAX HANDLER activities.

These AJAX handlers were working fine until I upgraded ECA module to version 2.0.9 after which Entity Browsers within the entry/edit page of given content type stopped working - they don't get displayed any more as pop-up window.

Browser console is giving Ajax (http 500) related error while in Drupal log I'm getting this message :

LogicException: The database connection is not serializable. This probably means you are serializing an object that has an indirect reference to the database connection. Adjust your code so that is not necessary. Alternatively, look at DependencySerializationTrait as a temporary solution. in Drupal\Core\Database\Connection->__sleep() (line 1920 of C:\xampp\htdocs\project\core\lib\Drupal\Core\Database\Connection.php).

By downgrading ECA module to version 2.0.8 OR by deleting/removing mentioned FORM: ADD AJAX HANDLER activities from the ECA workflow Entity Browsers appear to work again as expected.

Hope this info helps for patching the ECA module.

Thanks @gripphon for the extra details. We don't know for sure if it's caused by the same thing, but it could be.

I looked through the code changes between 2.0.8 and 2.0.9 and nothing comes to mind what could be causing this.

So, something that helps us to reproduce the problem on a fresh Drupal installation would be required.