After uninstalling the shield, config should be deleted.

Created on 14 November 2021, about 3 years ago
Updated 25 July 2024, 4 months ago

Problem/Motivation

After uninstalling the shield module user not able to access the site due to shield configuration and schema still present in the Db.

Steps to reproduce

Install the module and check the shield will working fine. Now uninstall it and try to access any of the url like homepage or etc.
it will give you access denied or unauthorized access.

Proposed resolution

Add config delete option to "shield.setting.yml" file.

Remaining tasks

N/A

User interface changes

N/A

API changes

This module does not have an API.

Data model changes

N/A

🐛 Bug report
Status

Active

Version

1.4

Component

Code

Created by

🇮🇳India Manav

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇨🇭Switzerland handkerchief

    I have the exact same problem. Caught the eye in 💬 Undefined constant "Drupal\node\Entity\DRUPAL_OPTIONAL" Active
    https://www.drupal.org/project/shield/issues/3304657#comment-15694393 💬 Undefined constant "Drupal\node\Entity\DRUPAL_OPTIONAL" Active

    Can confirm that there is no shield.setting entry in the config table after uninstalling, but there is still the described error which discards the whole instance and makes it unusable. As soon as the module is reactivated “drush en shield”, the page works again. In the logs it simply says Access denied for each path you have selected, otherwise no error or message.

    Only affects the Shield module, other modules can be installed and uninstalled without any problems. But it only happened to me after I had installed a patch (but not anymore), see link. any ideas?

  • 🇨🇭Switzerland handkerchief

    Strangely enough, importing a DB backup doesn't help either...

  • 🇨🇭Switzerland handkerchief

    Tried with full backup, it's working again now.

    Can anyone tell me if this is specific to Shield or a general phenomenon or what could be the cause? Depending on that, this issue can be treated further or analyzed somewhere else.

Production build 0.71.5 2024