Could this please be merged into 1.x? Version 2 is still only in alpha... Many thanks!
Thank you. I think the problem is that I had not entered a value for 'namespace' in the form. When I added what's in my D10 settings.php.file into that field, the errors went away. Changing this issue type from bug report to support request and marking it closed.
I think some improvements to the form could help other users avoid the problem I had. If I have time I will create a new issue.
Thank you for your suggestions.
I believe the settings for my D7 database — at least the ones I have entered — are correct, and that the connection is being made through Lando. If none of that were true the module would not be able to read anything from that database, and that is not the case. For instance, the module displays information it obtained about user roles and text formats when I visit those screens.
Could it be that some of the fields on the database setup screen that are not marked required are, in fact, required for it to work? For instance, your screenshot shows the value "default" in the "target" field. In mine I've entered nothing. It is not immediately obvious to me what should go in all of those fields, as some of it seems to pertain to the D7 database and some to the D10 installation.
dblog entries (just the PHP message and first stack trace item), in the order they're logged:
Warning: Undefined array key "default" in Drupal\Core\Database\Database::openConnection() (line 454 of /app/web/core/lib/Drupal/Core/Database/Database.php)
#0 /app/web/core/includes/bootstrap.inc(166): _drupal_error_handler_real(2, 'Undefined array...', '/app/web/core/l...', 454)
Warning: Trying to access array offset on value of type null in Drupal\Core\Database\Database::openConnection() (line 454 of /app/web/core/lib/Drupal/Core/Database/Database.php)
#0 /app/web/core/includes/bootstrap.inc(166): _drupal_error_handler_real(2, 'Trying to acces...', '/app/web/core/l...', 454)
Drupal\Core\Database\DriverNotSpecifiedException: Driver not specified for this database connection: in Drupal\Core\Database\Database::openConnection() (line 455 of /app/web/core/lib/Drupal/Core/Database/Database.php).
#0 /app/web/core/lib/Drupal/Core/Database/Database.php(191): Drupal\Core\Database\Database::openConnection('', 'default')
jmcintyre → created an issue.
jmcintyre → created an issue.
jmcintyre → created an issue.
Subscribing. This patch almost worked for me. I'm still unable to select items once I've used the exposed filters on the entity browser, though.
I've only seen the issue occur when the entity browser is used on a field (image, in my case) that accepts multiple values. I have single-value image fields, on the same node form even, that work just fine.
I think disabling Big Pipe is going to have to do for now. Thanks for working on this!
#12 solved the issue for me as well, thanks!
jmcintyre → made their first commit to this issue’s fork.
jmcintyre → created an issue.
jmcintyre → created an issue.
The fix in #2 works for me in Drupal 9.5.7.
jmcintyre → created an issue.