🇺🇸United States @mweixel

Thanks, @megachriz! I'm much more familiar with XML. Your super-clear explanation got me reviewing JSON path syntax so that I was able to build out my mappings pretty quickly.

It would be great, as you say, to trap Ajax/500 errors and to direct the user to review the logs instead, where the real insight into the problem is.

-- Mark

mweixel → created an issue.

Removing the composer.lock file seems to solve the first element in the problem, but the minimum-stability error persists:

% composer -W require 'drupal/term_merge:^2.0@beta'
./composer.json has been updated
Running composer update drupal/term_merge --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/term_merge[2.0.0-beta1, ..., 2.0.0-beta6] require drupal/term_reference_change * -> found drupal/term_reference_change[dev-1.x, dev-2.x, 1.0.0-alpha1, 1.0.0-alpha2, 1.0.0-beta1, 1.x-dev (alias of dev-1.x), 2.0.0-beta2, 2.0.0-beta3, 2.x-dev (alias of dev-2.x)] but it does not match your minimum-stability.
    - Root composer.json requires drupal/term_merge ^2.0@beta -> satisfiable by drupal/term_merge[2.0.0-beta1, ..., 2.0.0-beta6].

Installation failed, reverting ./composer.json to its original content.