Problem/Motivation

When trying to test the latest version of Upgrade Status, the slick_media module would not install due to PreExistingConfigException.

0.00 =0s 2020-08-16 22:53:40 (0.00 B/s) - ‘/dev/null’ saved [0]

5f39b881f4c73fdbac582bde# /bin/sh -c cd "${DOCROOT}" && echo 'if (PHP_SAPI === "cli"){ ini_set("memory_limit", "-1"); }' >> sites/default/settings.php

5f39b881f4c73fdbac582bde# /bin/sh -c cd "${DOCROOT}" && echo '$settings["file_private_path"] = "sites/default/files/private";' >> sites/default/settings.php

5f39b881f4c73fdbac582bde# /bin/sh -c drush -r "${DOCROOT}" si standard --account-name=admin --account-pass=admin -y

// You are about to DROP all tables in your 'tugboat' database. Do you want to // continue?: yes.

[notice] Starting Drupal installation. This takes a while.

[success] Installation complete.

5f39b881f4c73fdbac582bde# /bin/sh -c cd "${DOCROOT}" && chmod -R 777 sites/default/files

5f39b881f4c73fdbac582bde# /bin/sh -c drush -r "${DOCROOT}" en upgrade_status -y

[success] Successfully enabled: upgrade_status

5f39b881f4c73fdbac582bde# /bin/sh -c drush -r "${DOCROOT}" en slick_media -y

The following module(s) will be enabled: slick_media, slick, blazy, media, media_entity_image, media_entity, entity, video_embed_media, video_embed_field

// Do you want to continue?: yes.

In PreExistingConfigException.php line 65: Configuration objects (system.action.media_delete_action, system.action.med ia_publish_action, system.action.media_save_action, system.action.media_unp ublish_action, views.view.media) provided by media_entity already exist in active configuration

Steps to reproduce

  1. Choose Upgrade Status 8.x-3.x
  2. Add Slick Media (slick_media) as an additional project
  3. Click Launch sandbox

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

Kristen Pol created an issue. See original summary.

rachel_norfolk’s picture

rachel_norfolk
Primary language English
Location UK
commented
Status: Active » Postponed (maintainer needs more info)

The error here seems so specific with regard to configuration items that I wonder if this is a simply test.me issue or an issue between these two modules.

Can the reporter confirm that installing these two modules in this order does no cause an error in a local Drupal instance?

rachel_norfolk’s picture

rachel_norfolk
Primary language English
Location UK
commented

We have not received an update on this issue in a four week period so we’re going to close it. This lets us focus on the issues that are getting the most engagement.