Hello,

I'm getting a WSOD on installing the domain_content module which is part of the domain (Domain Access) module (https://www.drupal.org/project/domain). The error log states:

Standort	https://du6rd.ply.st/admin/modules/list/confirm
Referrer	https://du6rd.ply.st/admin/modules/list/confirm
Message	Drupal\Core\Entity\EntityStorageException: 'view' entity with ID 'affiliated_content' already exists. in Drupal\Core\Entity\EntityStorageBase->doPreSave() (Zeile 425 in /home/du6rd/www/core/lib/Drupal/Core/Entity/EntityStorageBase.php).
Schweregrad	Fehler	

Steps to reproduce (thunder 8.2.10/drupal 8.4.2/domain access 1.0-alpha11):
1. Install thunder and domain module on simplytest.me
2. Activate domain_content module directly without enabling domain_access beforehand.
3. WSOD appears but module seems to be installed properly.

Locally I have thunder 8.2.11 and drupal 8.4.3 installed and get the same error. The error does not show on a plain drupal install, so I assume there is an issue within the Thunder distribution.

Edit
: On every module installation, the error is triggered again.

Comments

anruether created an issue. See original summary.

anruether’s picture

Issue summary: View changes
chr.fritsch’s picture

Status: Active » Postponed (maintainer needs more info)

Hi,

I tried to reproduce the issue, but sadly it was not possible for me.

I installed Thunder 2.12 and did a drush dl domain && drush en domain_access

It worked smoothly for me.

So any idea what I need to do in order to break it?

anruether’s picture

I haven't tried it with drush, but Domain Content is not automatically enabled by Domain Access. So, if it also breaks with drush, this will break it ;)
drush en domain_content

anruether’s picture

Issue summary: View changes

changed module names to machine names to avoid confusion.

chr.fritsch’s picture

Worked fine:

$ drush en domain_content
The following extensions will be enabled: domain_content
Do you really want to continue? (y/n): y
domain_content was enabled successfully.                                                                                                                                 [ok]
domain_content defines the following permissions: access domain content, access domain content editors
anruether’s picture

Issue summary: View changes

I updated the steps to reproduce:

2. Activate domain_content module directly without enabling domain_access beforehand.

If you enable the modules one by one, it works out fine indeed!

chr.fritsch’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

Out of date. Please re-open if there are any further problems.