Warn or prevent disabling "overrides" when Rabbit Hole values already exist in the database

Issue created by @Matroskeen
Open in Jenkins → Open on Drupal.org →
Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
last update almost 2 years ago
21 pass, 2 fail
@matroskeen opened merge request.
Open in Jenkins → Open on Drupal.org →
Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
last update almost 2 years ago
21 pass, 2 fail
Open in Jenkins → Open on Drupal.org →
Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
last update almost 2 years ago
22 pass
Open in Jenkins → Open on Drupal.org →
Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
last update almost 2 years ago
20 pass
Open in Jenkins → Open on Drupal.org →
Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
last update almost 2 years ago
20 pass
Comment almost 2 years ago →
System Message

Matroskeen → committed 4e8e0974 on 2.0.x
Issue #3368673 by Matroskeen: Warn or prevent disabling "overrides" when...
Status changed to Fixed almost 2 years ago11:25am 23 June 2023
Comment almost 2 years ago →
🇺🇦Ukraine Matroskeen 🇺🇦 Ukraine, Lutsk
Done! There are 2 levels of protection:

1) On the general Rabbit Hole settings page, it won't be possible to disable an entity type if at least one of the entities has Rabbit Hole overrides in the database:

2) On entity type settings page, it'll require additional submit to confirm the removal:

Hopefully, it'll be enough for the first iterations.
Marking as Fixed.
Comment almost 2 years ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

Warn or prevent disabling "overrides" when Rabbit Hole values already exist in the database

Problem/Motivation

Comments & Activities