Enabling ‘private_shortcut’ module eventually causes “plugin not found” configuration errors sitewide; uninstall resolves issue

Problem/Motivation

After enabling the Private shortcut module, the site experiences configuration issues after several days of normal operation. Specifically, errors appear stating that plugins are missing or cannot be found. These configuration problems affect unrelated functionality and site stability. Uninstalling the Private Shortcut module resolves the issues immediately, suggesting a direct relationship between the module's activation and the config errors.

Steps to reproduce

1. Enable the private_shortcut module on a Drupal site.
2. Allow the site to run for a few days. Use the site as normal (including importing/exporting configuration, making admin changes, etc.).
3. Observe configuration warnings/errors such as “Plugin not found,” usually within admin screens or when working with config.
4. Uninstall the private_shortcut module.
5. Verify that configuration/plugin errors disappear after the module is removed.

Proposed resolution

• Consider warning or blocking install if configuration dependencies cannot be satisfied.
• Ensure the module correctly cleans up config entities and plugin references upon uninstall.
• Add automated tests for clean install/uninstall and config sync scenarios.

Remaining tasks

• Replicate the issue on a fresh site with the module enabled for several days.
• Review error logs and gather specific plugin/config error messages.
• Audit the module's plugin registration, config entities, and uninstall logic.
• Update documentation on known issues, if any.
• Propose or develop a patch or workaround pending maintainer feedback.
• Test resolution/fix on actual site.