A 500 error is shown when BibCite keywords are merged using bulk operations

Hi,

Also experiencing this on the views bulk action only. I checked the bibcite_keyword database table and from what I can tell it seems the "keyword" field doesn't exist which is why the query fails when it's looking for the "keyword" field. From looking at the database query it looks like it should point to "id" instead.

It seems like the field_name is passed from the route definition in modules/bibcite_entity/bibcite_entity.routing.yml:

entity.bibcite_keyword.bibcite_merge_multiple_form:
  path: '/admin/content/bibcite/keyword/merge'
  defaults:
    _form: 'Drupal\bibcite_entity\Form\MergeMultipleForm'
    entity_type_id: 'bibcite_keyword'
    field_name: 'keyword'
  requirements:
    _permission: 'administer bibcite_keyword'

Patch attached against 3.0.x branch or this routeSubscriber seems to fix it too:

<?php

namespace Drupal\MODULE\Routing;

use Drupal\Core\Routing\RouteSubscriberBase;
use Symfony\Component\Routing\RouteCollection;

class MODULERouteSubscriber extends RouteSubscriberBase {

  public function alterRoutes(RouteCollection $collection) {
    if ($route = $collection->get('entity.bibcite_keyword.bibcite_merge_multiple_form')) {
      // Change the default 'field_name' to 'id'.
      $route->setDefault('field_name', 'id');
    }
  }

}

Cheers
Tom

Merge request created from the provided patch to confirm automated test coverage.

I can confirm that the error message goes away, but the merge functionality still does not work.

I tested both the `2.x` and `3.x` branches using both approaches suggested in comment #4 (modifying the YAML file and using a `RouteSubscriber`). Neither method resolved the issue.

The interface reports conflicting messages — one indicating success and another stating that the merge failed.

In the logs, we’re seeing the following PHP warning:

Warning: Undefined array key "target_id" in _bibcite_entity_process_field_value() (line 99 of /modules/contrib/bibcite/modules/bibcite_entity/bibcite_entity.batch.inc)

Adding an isset() check on line 99 (and also on line 123) suppresses the warning, but the merge functionality still fails.